Jail Software Requirement Specification

Code Crackers
Jail-Inmates’ Management System

Software Requirements Specification
Version 1.0
Karan Malhotra
Project Guide
Mrs. Komalavalli C
Revision History
Date Version Description Author

15/09/2008 1.0 Synopsis Code Crackers
15/08/2008 Jail-Inmates’ Management System
Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms and Abbreviations
1.4 References
1.5 Technologies to be used
1.6 Overview
2. Overall Description
2.1 Product Perspective
2.1.1 Software Interface
2.1.2 Hardware Interface
2.1.3 Communication Interface
2.1.4 Product Functions
2.1.5 User Characteristics
2.1.6 Constraints
2.2 Use-Case Model Survey
2.3 Class Diagram
2.4 Sequence Diagram
2.5 Architecture diagram
2.4 ERD
2.5 DataBase Design
2.5.1 Database Diagram
2.5.2 Database Schema
2.6 Assumptions and Dependencies
3. Specific Requirements
3.1 Use-Case Reports
3.2 Data Flow Diagram
3.3 Control Flow Diagram
3.4 Supplementary Requirements
4. Supporting Information
5. Concerns / Queries / Doubts if any:
Page | 2
Software Requirements Specification

1. Introduction
Prisons are conventionally institutions, which form part of the criminal justice system of a
country; and prison system is the organizational arrangement of the provision and operations of
prisons, and depending upon their nature, may invoke a corrections system.
Prisons form an important part of the law and order system of any society or a country at large.
For a country as large as India with so many prisons and so many criminals, there is a requirement
of a very effective and organized system that manages the prisons. Although prisons are as ancient
as the civilization but with the changing times, there is an obvious need of managing them in an
effective way.
Many developed countries have already changed to electronic and computerized prison
management systems that are well organized and controlled. In India also, such need has been felt
and the government is going towards the computerization of the prisons. National Information
Centre (NIC) of India has the responsibility of automating of all the government departments and
likewise.
In their endeavor, they have started automating various prisons like Tihar Jail in Delhi etc. This
will in turn create a centralized or distributed system of prisons all over the country where all the
prisons are connected and synchronized. But the whole process is putting its baby steps and a lot
has to be done. It is just the beginning.
This project “Jail – Inmates’ Management System (JIMS)” is an ambitious work in the same
direction that will help Indian Prison System to reach those heights technologically, that it requires
desperately and which will prove beneficial for the other government departments as well.
1.1 Purpose
This software requirement specification document (referred from IEEE SRS format) explains
details of Jail Management System and includes technical as well as non technical details, use-
cases designs, shortcomings if any and difficulties faced during the overall development cycle.
This document also includes the technologies being used and their purpose. It is a humble effort to
ensure that anybody who reads it gets an insight to the subsystem. The purpose of this software is
to develop an Online Application that will be helpful for management of Prisons across the
country.
1.2 Scope
The Scope of Jail Management System is to organize and manage the information and activities of
the Indian Prison System. This includes the day to day updates and changes in the system as well
as the maintenance of various registers and reports. It helps the users of the system to remain
informed about the status and happenings in the system, which they can see in the form of various
reports and data charts which will be created by the system.
In the broader sense, the system maintains and informs about the current crime state of the country
as it is a country wide integrated system where various units are connected to form a complete
system.
Page | 3
1.3 Definitions, Acronyms and Abbreviations
 HTML - Hypertext Markup Language is to create static web pages.

 HTTP - Hypertext transfer protocol is a transaction oriented client/server protocol
between web browser and a web server.
 HTTPS - Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket
layer).
 TCP/IP - Transmission Control Protocol/Internet Protocol, the suite of communication
protocols used to connect hosts on the Internet. TCP/IP uses several protocols, the
two main ones being TCP and IP.
 J2EE - Java 2 Enterprise Edition is a programming platform and it is the part of the
java platform for developing and running distributed java applications.
 WAS - Web sphere application server is an application server that runs business
applications
and supports the J2EE and web services standards.
 DB2 - Database 2 is the database management system, developed by IBM that
provides a flexible and efficient database platform to erect strong on demand
business applications.
 RAD – Rational Application Developer is an integrated development environment
(IDE), made by IBM's Rational Software division, for visually designing, constructing,
testing, and deploying Web services, portals, and Java 2 Enterprise Edition (J2EE)
applications.
 WSAD - Web Sphere Studio Application Developer is a designer toolkit which is
designed for develop more complex projects by providing fully dynamic web service.
 JSP - The presentation layer of the application will be developed using Java Server
Pages (JSP) technology. It will separate front end design code from java code so that
we can more concentrate on our work according to our work role
 IEEE - The Institute of Electrical and Electronics Engineers or IEEE (read eye-triple-e)
is an international non-profit, professional organization for the advancement of
technology related to electricity.
 Jail Admin – The Jail Administrator is responsible to plan, organize, implement,
operations and programs in the Correction’s division.
 Govt. Admin – The Government Administrator keeps vigil on the various users of the
System and monitors the functioning of the System.
 J-IMS – Jail – Inmates Management System is a powerful, high-performance, Web-
based system that automates and streamlines the processes associated with
managing inmate data.
 SRS – Software Requirements Specification is a complete description of the behavior
of the system to be developed.
1.2 References
 SRS format adapted from IEEE guide.
 Project Scenario specified by TGMC.
 Information collected by the visit to the Prison Headquarters, Tihar Jail, Delhi through
detailed interaction with the senior administrator.
 Information acquired from World Wide Web.
Page | 4
1.3 Technologies to be used
 J2EE – Java, Java Servlets, Java Scripts, JSP, HTML

 DB2 – Database
 WSAD – Development Tool
 WAS – Websphere Application Server
 Rational – Design Tool
1.4 Overview
 Further, the SRS is divided into two subsections:
o Overall Description – It contains the Customer oriented requirements and the factors
that affect it.
o Specific Requirements – Developer oriented Software requirements are listed in this

section.
2. Overall Description
2.1 Product Perspective
It includes the products that are involved in the making of entire system. The products can be seen
in the diagram.
Page | 5
 Database Server: This is for the maintenance of the entire data which is flowing IN and OUT the system.
 TCP/IP protocols are used to provide the interface on the client by the client software.
 Communication between customer and server is done through HTTP/HTTPS protocol which thereafter
provides the user interface on the client side.
2.1.1 Software Interfaces
 Client on internet/Intranet: Web Browser, Operating System
 Database Server: DB2, Operating System
 Application Server: WebSphere Application Server, Operating System
Page | 6
 Development Side: RAD (J2EE, Java, JSP, Servlet, HTML, Java Script), Operating System, DB2
and WebSphere Application Server.
 Deployment Side: Operating System, WASCE, JDK
2.1.2 Hardware Interfaces
Applications Operating System Processor RAM Hard Disk Space
Client Side Windows/Linux Pentium III 64 MB and 1 GB

500Mhz and Above Above
DB2 Windows/Linux Pentium and Above 256 MB and 350 MB (typical)
Above 100 MB (custom,
compact)
WebSphere Windows/Linux Pentium 500 MHz 512 MB 1 GB
and Above (minimum)
1 GB
(recommended)
(NOT IN CASE OF CLIENT SIDE)
 Additional disk space for storing data size.
 Additional memory may be required
2.1.3 Communication Interfaces
TCP/IP – used by clients on Intranet.

 TCP ensures that data arrive intact and complete.
 IP “network layer” makes TCP/IP a routable protocol.
HTTP – used by clients on Internet.

 It is used to request and transmit files.
2.1.4 Product Functions
 Add/delete System users and assign them permissions according to their roles.
 A complete prisoner Profiling System that will contain the significant details of the inmates
including their demographic details and photographs.
Page | 7
 Keeps track of all the prisoners release details including the probable Date of Release with
the flexibility to accommodate the modifications due to Court orders and other special
reasons.
 Manages the outgoing and incoming of the Funds allocated.
 Manages the login details of various users.
 Maintains the centralized Database with specific access rights for the different users of the
database while ensuring the complete security.
 JMS is flexible enough to accommodate the changes as per the future requirements of the
System.
 It maintains various registers like Duty register, In-Out register for managing movements of
the prisoners, etc
2.1.5 User Characteristics
There are majorly three kinds of users that will use our System.
 Police Officers – There are the officials of various ranks from a constable to the Inspector
General of Police. They have the read only access to the system and can view all the details of
the prisoners and can generate various reports.
They are required to have the general understanding of the System in order to utilize all its
features.
 Data Manager – This kind of users has the responsibility of maintain the Database. All the
entries and updations are done by Data Managers.
They are required to have the proper knowledge of the Prison Database and its design.
 Administrators – Due to the nature and requirement of any such system, someone has to be
there who is responsible for the security and maintenance of the system. This is what the basic
role of System Administrator is.
We have further categorized the administrator in two. One is Jail Admin and another is
Government Admin. They have the rights and responsibility according to their stature and
requirements.
2.1.6 Constraints
 A user cannot log on more than one machine with same user id.
 User can interact with the System only in the English language.
2.2 Use Case Model Survey
Page | 8
 Police Officials
o Login
o View Prisoner Record
o View visitor record
 Data Manager
Page | 9
o Login
o Update Visitor Record
o Update Staff Record
o Update Prisoner record
o Case Register
o In/out register
o Duty register
o Forgot Password
o Maintenance of J-IMS
 Jail admin
o Login
o Update Visitor Record
o Update Staff Record
o Update Prisoner record
o Case Register
o In/out register
o Duty register
o Forgot Password
o Maintenance of J-IMS
o Update Jail records
o Manage Funds
o Reset Password
o Add/Remove User Accounts
o Generate Reports
 Govt Admin
o login
o View Staff Records
Page | 10
o View Jail records
o Manage Funds
o Add/Remove Users
Page | 11
2.3 Class Diagram
Page | 12
2.4 Sequence Diagram

Case 1 – Checking the Flow and sequence of various operations that a Data Manager can do.
Page | 13
Case 2 - Checking the Flow and sequence of various operations that a Govt Admin can do.
Page | 14
Case 3 - Checking the Flow and sequence of various operations that a Police Official can do.
Page | 15
Case 4 - Checking the Flow and sequence of various operations that a Jail Admin can do.
Page | 16
Page | 17
2.5 Architecture Diagram
Page | 18
2.6 E-R Diagram
It is an Entity relationship diagram. It shows the relationship between two or more than two entities.
Page | 19
2.7 Data Base Design
2.7.1 Database Schema
Page | 20
2.7.2 Database Diagram
Page | 21
2.8 Assumptions and Dependencies
 system has been created by administrator already
 roles and tasks of all the users are pre defined
 Database has already been created
 User accounts have been created already assuming some username and password
Page | 22
3. Specific Requirements
3.1 Use-Case Reports
Use Case 1 – Login
Page | 23
Name Login
Description Used by various Users (Police Officer, Data Manager, Jail Admin, Govt Admin) for
Logging in the system.
Pre Conditions  Open the webpage by typing its URL

 Account must be already created
Flow of Events  User types the Username and Password

 Username and password is checked for authentication
 The page is redirected to the User’s main page after its verification
Alternate Flow of Events  Prompt the user with Error message if login is not verified
 If database is not connected and started prompt with an error message
Post Conditions None
Table showing the complete description about the use case 1
Page | 24
Page | 25
Use Case 2 – view Prisoner Record
Page | 26
Name View Prisoner Records
viewing the profiles of the prisoners.
Pre Conditions  The user must be Logged in

 A specific Prisoner ID should be typed by the user or Search criterion has to be
given.
Page | 27
Flow of Events  Click the link of View prisoner record.

 Type the prisoner ID or search for Prisoner.
 The page is redirected to the page containing prisoner’s profile .
Alternate Flow of Events  If the prisoner ID is wrong the user will be prompted by an error message.
 If connection with the database cannot be established then prompt with an error
message.
Page | 28
Use Case 3 – Update Prisoner Record
Page | 29
Page | 30
Name Update Prisoner Records
Description Used by Data Manager and Jail Administrator for updating and viewing the profiles of the
prisoners.
Pre Conditions  The user must be data manager or Jail Administrator
Flow of Events  Click the link of Update prisoner record

 Enter the Jail details of the prisoner along with its Personal details
 Submit for saving the changes to the database
 Details are stored in the database and the profile is created
Alternate Flow of Events  Prompt the user with error message if any of the field is left blank
message
Post Conditions  Data manager and Jail Administrator can view the details entered/profile if he
wants to.
Page | 31
Use Case 4 – Case Register
Page | 32
Name Case Entry
Description This feature is included for maintaining the number of cases on which the prisoner is
found convicted.
Page | 33
Pre Conditions  Data Manager or Admin must be Logged in

 Enter valid Case ID to view the details (if already created).
 Select the prisoner on which case is to be imposed.
Flow of Events  Identify the USER

 If Govt Admin, he can only view the case details
 If Data manager or Jail Admin, select the prisoner
 Enter the case details corresponding to the prisoner selected
 Confirmation message is displayed to the user.
Alternate Flow of  Prompt the (Data Manager/ Jail Admin) with error message if prisoner ID wrong
Events  Prompt the user (Govt Admin) with error message if case ID is not valid
 Prompt the user (Data Manager/ Jail Admin) with error message if any of the
field is left blank
message
Post Conditions  Details are stored in the database and the prisoner’s profile is updated
Page | 34
Page | 35
Use Case 5 – View Visitor Record
Page | 36
Name View Visitor Records
viewing the profiles of the Visitors or the profile of prisoner along with the visitor
details.
Pre Conditions  The user must be Logged in

 A valid Visitor ID must be entered by the user or a search criterion has to be
given.
Flow of Events  Click the link of View Visitor Record.

 Type the visitor ID or Search for visitor.
o The profile of the visitor is showed.
Alternate Flow of Events  If the Visitor ID is wrong the user will be prompted by an error message.
 If connection with the database cannot be established then prompt with an
error message.
Page | 37
Use Case 6 – Update Visitor Record
Page | 38
Page | 39
Name Update Visitor Records
Description Used by Data Manager and Administrator for updating and viewing the profiles of the
Visitors.
Pre Conditions  The user must be Data Manager or Jail Administrator
Flow of Events  Click the link of Update Visitors record

 Enter the Visitor’s details
message
Post Conditions  Data manager and Administrator can view the details entered/profile if he
wants to.
 Visitor ID is generated
Page | 40
Page | 41
Name Update Staff Records
Description Used by Data Manager and Jail Administrator for updating and viewing the profiles of
the Staff.
Flow of Events  Click the link of Update Staff Records

 Enter the Staff’s details
message
wants to.
 Staff ID is generated
Use Case 7– Update Staff Record
Page | 42
Page | 43
Use Case 8 – View Staff Record
Name View Staff Records
Description Used by various Administrators for viewing the profiles of the Staff
Pre Conditions  The user must be Logged in.

 A specific Staff ID should be typed or a search criteria has to be given by the
User
Flow of Events  Click the link of View Staff record

 Type the Staff ID or search for Staff.
o The profiles of the official(s) are showed.
Alternate Flow of Events  If the Staff ID is wrong the user will be prompted by an error message.
message.
Page | 44
Page | 45
Use Case 9 – In out register
Page | 46
Name In out register
Description This feature is included for maintaining the IN-OUT details (Like Parole, Hearing, and
Transferring etc) of various prisoners.
Pre Conditions  User must be Logged in

 Police officials and Government Administrator can only view details while Jail
Administrator and Data Manager can also add new Entries.
 Select the prisoner whose IN-OUT details are to be viewed or entered.
Flow of Events  Identify the USER

 Select the prisoner.
 If Govt Admin or Police Official, only IN-OUT details are shown.
 If Data manager or Jail Admin, enter the IN-OUT details corresponding to the
prisoner selected or view previous details.
 Confirmation message is displayed to the user.
Alternate Flow of Events  Prompt the user with error message if prisoner ID wrong
 Prompt the user (Data Manager/ Jail Admin) with error message if any of the
field is left blank.
message.
Post Conditions  Details are stored in the database and the prisoner’s IN-OUT details are
updated.
Page | 47
Page | 48
Use Case 10 – Search
Name Search
Description Used by all users for the various search operations.
Pre Conditions  User must be logged in.

 User has to choose what to search in the System.
 Search criteria have to be entered.
Flow of Events  Choose the search option.

 Select the entity to be searched.
 Enter the search criterion.
Alternate Flow of Events  Prompt the user with error message if search field is left blank
 Prompt the user if no match is found.
message
Page | 49
Page | 50
Use Case 11– Duty Register
Page | 51
Name Duty Register
Description Used by Data Manager and Jail Administrator for updating and viewing the Duty
Register.
Page | 52
Flow of Events  Click the link of Duty Register

 Enter the Staff ID
message
wants to.
Page | 53
Page | 54
Use Case 12– Update Jail Records
Name Update Jail Records
Description Used by Jail Administrator for updating and viewing Jail details.
Pre Conditions The user can be Jail Administrator only.
Flow of Events  Click the link of Update Jail Records.

 Enter the Jail details.
 Details are stored in the database.
Alternate Flow of Events  Prompt the user with error message if any of the field is left blank.
message
Post Conditions  Administrator can view the details entered.

 Jail ID is generated if new entry is made.
Page | 55
Page | 56
Page | 57
Use Case 13 – View Jail Record
Name View Jail Record
Description Used by various Administrators for viewing the Jail details.
Pre Conditions  The user must be logged in.

 A specific Jail ID should be typed or a search criteria has to be given by the
User
Flow of Events  Click the link of View Jail Records.

 Type the Jail ID or search for Jail.
o The Jail details are showed.
Alternate Flow of Events  If the Jail ID is wrong the user will be prompted by an error message.
error message.
Page | 58
Page | 59
Use Case 14 – Forget Password
Page | 60
Name Forget Password
Description To recover password in case it is forgotten by the user using secret answer of secret
question filled up at the time of subscription.
In case Jail Admin forgets password he/she knows secret answer explicitly as there is
no subscription for admin and password can be reset.
.
Pre Conditions  The user must click the forget password option
 Correct User Id .must is provided.
Flow of Events  User enters the User ID.

 Record for given user is searched in the database.
 Secret question is asked.
 If user provides correct answer than request to reset the password is send to
admin.
 If wrong answer is provided than error message is displayed
Alternate Flow of Events  Prompt the user with error message if user id is wrong as in database.
 Prompt the user with error message if wrong answer to secret question is
provided.
error message
Page | 61
Page | 62
Page | 63
Name Manage Funds
Description Used by Jail Admin and Govt. Admin for the maintenance of funds allocation and
tracking.
Pre Conditions  The user must be Jail Admin or Govt. Admin
Flow of Events  Identify the user.

 Click the link of Manage Funds
 If Govt. Admin then view funds details.
 If Jail Admin then add and update funds records.
 Details are updates and stored in the database.
Alternate Flow of Events  Prompt the user with error message if funds are less the required.
 Prompt the user with error message if any of the field is left blank
message
Post Conditions  Govt. Admin can view the total funds available and funds used for various
causes.
 Jail Admin can view and update the allocation of funds for the various causes
and updates other funds records.
Use Case 15 – Manage Funds
Page | 64
Page | 65
Name Reset Password
Description In case password is forgotten by the user, He/She can send the request to reset
password. In case Jail Admin forgets password he/she knows secret answer explicitly
as there is no subscription for admin and password can be reset.
.
Pre Conditions  The user must be Jail Admin
 Correct User Id .must is provided.
Flow of Events  Jail Admin enters the User ID.

 Record for given user is searched in the database.
 If found than new password is set by Jail Admin.
Alternate Flow of Events  Prompt the user with error message if user id is wrong as in database.
error message
Use Case 16 – Reset Password
Page | 66
Page | 67
Page | 68
Use Case 17 – Add/Remove User Accounts
Page | 69
Name Add/Remove User Accounts
Description Used by Jail Admin and Govt. Admin for adding and removing various user of J-IMS
Pre Conditions  The user must be Jail Admin or Govt. Admin
Flow of Events  Identify the user

 Click the link Add/Remove user
 Click Add New link to add new Enter the User Id, Password and Type
 Click Remove Link and Enter the User ID
 User is Deleted or Added and database is updated
 Prompt the user if User Id already exists(Add user)
 Prompt the user if User Id doesn’t exists(Delete User)
message
Post Conditions  New user can Log on to J-IMS with the User Id
 Existing user cannot Log on to J-IMS
Page | 70
Use Case 19 – Generate Reports
Page | 71
Name Generate Reports
Description Used by Jail Admin for generating various reports of J-IMS
Pre Conditions  The user must be Jail Admin
Flow of Events  Click the link of Reports

 Select the Type and Contents of Reports
 Generate and save the reports.
Page | 72

error message
Page | 73
Page | 74
3.2 Data Flow Diagram
It shows the flow of the system, i.e. how the data is flowing in the system.
Page | 75
3.3 Control Flow Diagram
Page | 76
3.4 Supplementary Requirements
 Since J-IMS is a centralized system with the large user base, the Application Server should be
strong enough to handle the load of the maximum number of clicks at a time.
 Since the System is up 24 hours a day and seven days a week, proper Power backup
arrangements must be there to ensure the un-interrupted running of the system.
The Physical security of the Database at the Server has to be ensured by the concerned authority
deploying the System.
Page | 77

Jail Software Requirement Specification

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Jail Software Requirement Specification

Uploaded by

Copyright:

Available Formats

Code Crackers

Jail-Inmates’ Management System

Date Version Description Author

5. Concerns / Queries / Doubts if any:

Software Requirements Specification

1.3 Definitions, Acronyms and Abbreviations

 HTML - Hypertext Markup Language is to create static web pages.

 SRS format adapted from IEEE guide.

 Project Scenario specified by TGMC.

 Information acquired from World Wide Web.

1.3 Technologies to be used

 J2EE – Java, Java Servlets, Java Scripts, JSP, HTML

 Further, the SRS is divided into two subsections:

o Specific Requirements – Developer oriented Software requirements are listed in this

2.1 Product Perspective

2.1.1 Software Interfaces

 Client on internet/Intranet: Web Browser, Operating System

 Database Server: DB2, Operating System

 Application Server: WebSphere Application Server, Operating System

 Deployment Side: Operating System, WASCE, JDK

2.1.2 Hardware Interfaces

Applications Operating System Processor RAM Hard Disk Space

Client Side Windows/Linux Pentium III 64 MB and 1 GB

(NOT IN CASE OF CLIENT SIDE)

 Additional disk space for storing data size.

 Additional memory may be required

2.1.3 Communication Interfaces

TCP/IP – used by clients on Intranet.

 IP “network layer” makes TCP/IP a routable protocol.

HTTP – used by clients on Internet.

2.1.4 Product Functions

 Manages the outgoing and incoming of the Funds allocated.

 Manages the login details of various users.

2.1.5 User Characteristics

2.2 Use Case Model Survey

o View Prisoner Record

o View visitor record

o Update Visitor Record

o Update Staff Record

o Update Prisoner record

o Update Visitor Record

o Update Staff Record

o Update Prisoner record

o Update Jail records

o Add/Remove User Accounts

o View Staff Records

o View Jail records

2.3 Class Diagram

2.4 Sequence Diagram

2.5 Architecture Diagram

2.6 E-R Diagram

2.7 Data Base Design

2.7.1 Database Schema

2.7.2 Database Diagram

2.8 Assumptions and Dependencies

 system has been created by administrator already

 roles and tasks of all the users are pre defined

 Database has already been created

3.1 Use-Case Reports

Use Case 1 – Login

Pre Conditions  Open the webpage by typing its URL

Flow of Events  User types the Username and Password

Post Conditions None