Software Requirements Specification

for

Prison Management
Version 1.0 approved

Prepared by

Abhay Sharma 08CS000145 Kuldeep Choudhary 08CS000204 Pratish Singh Kurmi 07CS000048 Vickey kumar kapoor 08CS000268 Sir Padampat Singhania University, Udaipur

29th August 2011

Software Requirements Specification for Prison Management Page ii

Table of Contents
Introduction.............................................................................................................................................. 1 1.1 Purpose................................................................................................................................................ 1 Prison Management System provides a user friendly way of managing various records over the internet. The central repository enables to track account- level data, all in-out information and session details. ..................................................................................................................................................... 1 Project Scope............................................................................................................................................ 1 1.2 References........................................................................................................................................... 1

2. Overall Description....................................................................................................................2
2.1 Product Perspective............................................................................................................................. 2.2 Product Features.................................................................................................................................. 2.3 User Classes and Characteristics........................................................................................................ 2.4 Operating Environment....................................................................................................................... 2.5 Design and Implementation Constraints............................................................................................. 2 2 3 3 3

3. System Features......................................................................................................................... 3
3.1 Use Case Diagram............................................................................................................................... 4

..................................................................................................................................................6 3. USE CASE RELEATED TO VIEW REGISTERS:.............................................................. 6 4. External Interface Requirements............................................................................................. 9

4.1 User Interfaces.................................................................................................................................... 9 4.2 Software Interfaces............................................................................................................................. 9 4.3 Communications Interfaces................................................................................................................. 9

5. Other Nonfunctional Requirements.........................................................................................9

5.1 Performance Requirements................................................................................................................. 9 5.2 Safety Requirements......................................................................................................................... 10 5.3 Security Requirements...................................................................................................................... 10 5.4 Software Quality Attributes ............................................................................................................. 10

6. Other Requirements................................................................................................................ 10

Revision History
Name Date Reason For Changes Version

Software Requirements Specification for Prison Management

Page 1

Introduction 1.1 Purpose

Prison Management System provides a user friendly way of managing various records over the internet. The central repository enables to track account- level data, all in-out information and session details.

Project Scope
The prison management system creates different users and assigns different roles with related permissions a subset of the long-term strategic product vision. This Project groups the users together in a single account according to some criteria. It authenticates all user of the system. It Keep track all the visitors their contact details, track all the staff, non-staff and prisoner in out details. Generate a graphical report on fund and other details generated in easily downloadable format. Track the Fund allotment and expenditure details. All activities performed by the system users will be maintained in the form of logs for auditing and maintaining the integrity of the system. Automated Diary Generation based on condition. Maintain a centralized database to provide security to information which can be accessed only by the admin. Customizable Profile feature with predefined skins to choose from.

1.2

References

Object oriented systems development using Unified Modeling Language by Ali Bahrami, publication: McGraw-Hill, International edition 1999 http://java.sun.com/developer/technicalArticles/ http://www.ncbi.nlm.nih.gov/pubmed?term=manage%20prison %20&itool=QuerySuggestion

Software Requirements Specification for Prison Management

Page 2

2.
2.1

Overall Description
Product Perspective

The web pages (XHTML/JSP) are present to provide the user interface on client side. Communication between client and server is provided through HTTP/HTTPS protocols The Client Software is to provide the user interface on system user client side and for this TCP/IP protocols are used. On the server side web server is for EJB and database server is for storing the information

2.2

Product Features

Easy updating: System will allow easy updating of data with the help of few forms only. A user will easily update the data. One click information retrieval: This system will give the information of the prisoner on one click. Report Generation:

Software Requirements Specification for Prison Management

Page 3

The system will generate one click prisoner report. Security: System provides login id and password so that only official person can access the respective data.

2.3

User Classes and Characteristics

This system is stand alone. This system is only designed for the prisons in India. This system can be used by any prison with the few minor modification. It is not designed for normal user it can be only used for official purpose. This system will be used in prison and in offices of the police station and C.B.I department. There will be 2 kinds of user 1 Super user (for jailer and its superior) This user can update the information of the prisoner. 2 Normal user (other official person in prison) This user can generate report and can retrieve the information

2.4

Operating Environment

This system will run on 512 MB RAM and 40 GB hard disk. The system must contain SQL database.

2.5

Design and Implementation Constraints

Security: This system will provide a secure login so that other person cant access the data. And by providing different kind of login system will ensure that wrong use of data will never occur, as only authorized person will be able to change the data.

3.

System Features

The functional requirements for the product by system features, the major services provided by the product and the use case diagram.

Software Requirements Specification for Prison Management

Page 4

3.1

Use Case Diagram

1. FUNCTIONAL REQUIREMENTS: We describe the functional requirements by giving various use cases: 1. USE CASE RELATED TO LOGIN: Primary actor All registered users having valid accounts 1) Jailer (admin) 2) Old Visitor

Software Requirements Specification for Prison Management

Page 5

Precondition 1. Jailer should be logged in to his account Main scenario 1. Retrieved the nominal roll register, case register, parole register Register, in-out register from the data base. 2. Viewing of data. Alternate scenario 1. Data retrieval process failed.

2. USE CASE RELATED TO REGISTRATION: Primary actor Unregistered New Visitor Precondition None Main scenario 1. The visitor accesses the registration page for new ID. 2. He/she fills up the form and submits. 3. The completeness of data is checked on client side. 4. The Database is updated Alternate scenario 1. The data completeness check fails and the user is prompted to provide all details. 2.The database update fails.

Software Requirements Specification for Prison Management

Page 6

3. USE CASE RELEATED TO VIEW REGISTERS: Primary actor: Jailer (admin) Precondition 1. Jailer should be logged in to his account Main scenario 1. Retrieved the nominal roll register, case register, parole Register, in-out register from the data base. 2. Viewing of data. Alternate scenario 1. Data retrieval process failed.

4. USE CASE RELATED TO GENERATE REPORTS: Primary actor Jailer (admin) Precondition 1. Jailer should be logged in to his account Main scenario 1. Retrieval of data prisoner-wise, case-wise or visitor-wise. 2. Form the retrieved data into printable format. 3. Print out the retrieved data. Alternate scenario 1. Retrieval of data failed 2. Printing out of retrieved data failed

Software Requirements Specification for Prison Management

Page 7

5. USE CASE RELATED TO INTERVIEW REQUEST: Primary actor Old visitor

Precondition 1. Old visitor should be logged into his/her account 2. Old visitor should be navigated to interview request page to get Access the interview request form. Main scenario 1. Access Interview request page 2. Provide all details. 3. Data completeness is checked. 4. On success the Database is updated. 5. Success page is shown. Alternate scenario 1. Database Update fails. 2. The data completeness check fails. 6. USE CASE RELATED TO INTERVIEW CONFIRMATION: Primary actor Jailer (admin) Precondition Jailer should be logged in to his account to access this option Main scenario 1. Verification status is checked 2. If OK then it is approved. 3. The database is updated. Alternate scenario

Software Requirements Specification for Prison Management

Page 8

1. The interview request is not approved. 7. USE CASE RELATED TO VIEWING OF RELEASE DIARY: Primary actor All registered users having valid accounts 1) Jailer (admin) 2) Old Visitor Precondition 1. User must be logged in 2. He/she has to be at his home page Main scenario 1. Retrieved the release diary information from the data base. 2. Viewing of data. Alternate scenario 1. Retrieval of data failed. 8. USE CASE RELATED TO CHANGING OF PASSWORD: Primary actor All registered users having valid accounts 1) Jailer (admin) 2) Old Visitor Precondition 1. The users should have registered an account with the system. 2. The users are logged into their account. Main scenario 1. The System asks for the old password. 2. The User provides his/her old password. 3. After successful match the system asks to enter the new password. 4. The Database is updated.

Software Requirements Specification for Prison Management

Page 9

5. The Success page is shown.

Alternate scenario 1. The Old password doesn't match and the error page is shown. 2. The Database Update fails.

4.
4.1

External Interface Requirements

User Interfaces

This user interface will consist of the screen with login window at the start. After system authenticate user then user will enter into another window which will contain various buttons for the forms and report. User can change the background and there are many features will be there. Hardware Interfaces

4.2

Software Interfaces

Operating system can be any system which allows java environment and SQL Database.

4.3

Communications Interfaces

The minimum requirement from the client side are a browser like Internet Explorer 6.0 and above, and Mozilla Firefox, Chrome and a processor at 500 MHz with a RAM of 128 MB and a disk space of 1GB. The server side requirement are Web Sphere Application server v 6.1 and processor of Pentium IV, RAM of 512 MB and a disk space 2 GB. The DB2 V9.1 should be for the database connectivity and implementation

5.
5.1

Other Nonfunctional Requirements

Performance Requirements

This system should be consistent. It should not crash at any time. It must not slow down the computer.

Software Requirements Specification for Prison Management

Page 10

5.2

Safety Requirements

This Project should be Handled by the person who has slightest knowledge of the HTML, Java and Database.

5.3

Security Requirements

This system will provide the secure login of user and provide access to the only authorized user. And dividing user as super user and normal user system will avoid wrong use of data. Data will keep on hard disk so if system gets crashed or in case of critical condition we can retrieve back the data.

5.4

Software Quality Attributes

Reusability :This software can be reusable with minor changes and can be Used in other department of the government. Updation: We can update the software by adding few new features into it and removing the features that we dont want.

6.

Other Requirements

Website should be highly customizable and flexible enough to easily deploy without much effort.

Appendix A: Glossary
Prisoner details: Details of prisoner such as name, id, date of birth, address, fathers name, digital photo and finger prints etc. Staff details: Details of staff associated with the prison. HTML: Hypertext Markup Language is a markup language used to design static webpages. JSP: Java Server Pages. JAVASCRIPT: scripting language used for client side web development.

Software Requirements Specification for Prison Management

Page 11

JQUERY: lightweight JavaScript library that emphasizes interaction between JavaScript and HTML. DB2: DB2 Database is the database management system that delivers a flexible and cost-effective database platform to build robust on demand business applications. WAS: Web sphere application server is an application server that runs business applications and supports the J2EE and web services standards. RAD: Rational application developer is a toolkit which is designed for the creation of more complex projects, providing fully dynamic web application. This consist of EJB tools, CMP, data mapping tools & a universal test client that is designed to aid testing of EJBs. HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between web browser & a Web Server. HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer) to Manage Prisons. 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.