Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Srs

6,146 views

Published on

Published in: Technology
  • Be the first to comment

Srs

  1. 1. Prison Management System Version 1.0 Software Requirements Specification 30-12-2010 Code champs Code champs PRISON MANAGEMENT SYSTEM Software Requirement Specification Version 1.0Team Guide: Neha Kishore Members: Vipul Sharma Vishal Garg Vivek Thakur College Name: Chitkara University Department: CSOET (Chitkara School Of Engineering And Technology) State: Atal Nagar (Barotiwala).Code champs / Chitkara University 1|Page
  2. 2. Prison Management System Version 1.0 Software Requirements Specification 30-12-2010 Code champs Table of ContentsDescription Page 1. Introduction no. 1.1 Purpose 3 1.2 Scope 4 1.3 Definitions, Acronyms, Abbreviations 4 1.4 References 5 1.5 Technologies to be used 5 2. Overall Description 2.1 Product Perspective 6 2.2 Software Interfaces 6 2.3 Hardware Interfaces 6 2.4 Product Functions 7 2.5 User Characteristics 8 2.6 Constraints 8 2.7 Use case Model Description 8 2.8 Database Design 10 3. Specification Requirements 3.1 Use case Registers 12 3.2 Supplementary Requirements 15Code champs / Chitkara University 2|Page
  3. 3. Prison Management System Version 1.0 Software Requirements Specification 30-12-2010 Code champsSOFTWARE REQUIREMENTSPECIFICATION 1. INTRODUCTION: 1.1 PURPOSE: This project is aimed at developing a prison management system that is a collection of registers and reports for the effective management of prisons. Besides this police and government officials can see crime/criminals reports for their purpose.1. Nominal Roll: The details of the prisoner and his/her demographic details should becaptured. A digital photo comprising different views of the prisoner and the list of articlessurrendered by prisoner during nominal roll are to be recorded.2 Case register: All the details of the cases against the prisoner should be captured.This must include the sentence details, remand/conviction details, etc.3 Automated release diary generator: This report should be display the list ofprisoners to be released on a day, the next day, the next week, the next month, or anygiven duration of time. The system should consider the reduction of sentence lengthdue to various considerations.4 Parole register: This module should track all prisoners on parole and providenecessary reports on this data.5 Duty register: Who was where, why and when.6 Interview requests: All interview requests by the relatives of the prisoners need to berecorded and tracked.7 In-out register: An in-out register will track all prisoners and others who move in andout for various reasons. This should include provisions for recording the prisoners sentto courts for hearing.8 Fund allotted and routine accounting transactions should be captured.Code champs / Chitkara University 3|Page
  4. 4. Prison Management System Version 1.0 Software Requirements Specification 30-12-2010 Code champs1.2 SCOPE:1. The system should have a login.2. System should support for Data Entry module for Nominal Roll, Case register foreach prisoner entering in the prison.3 Police officers should have a read only access to the information of prisoners. 4 Data managers must be able to add or update the data of prisoners.1.3 Definitions, Acronyms and Abbrevations:1.HT ML : Hypertext Markup Language is a markup language used todesign static web pages.2. J2EE: Java 2 Enterprise Edition is a programming platform² part ofthe Java Platform for developing and running distributed multi-tierarchitecture Java applications, based largely on modular softwarecomponents running on an application server.3. GUI: Graphical User interface with the system with mouse control andother easy to use control features like the menus etc.4. SRS:A SRS is basically an organizations understanding (in writing)of a customer or potential clients system requirements anddependencies at a particular point of time (usually) prior to any actualdesign or development work. Its a two-way insurance policy thatassures that both the client and the organization understand each othersrequirements from every perspective at a given point of time.Code champs / Chitkara University 4|Page
  5. 5. Prison Management System Version 1.0 Software Requirements Specification 30-12-2010 Code champs5. Eclipse/NetBeans: Development tool (IDE) for Web applications.6.JSP: Java server page is a standard part of the J2EE .It is used tocreate dynamic web pages.7.Servlets: These are small programs which execute on the server sideand dynamically extend the functionality of the web browser .Itgenerally acts as a control in the server side.8. HTTP: Hypertext Transfer Protocol is a transaction orientedclient/server protocol between web browser & a Web Server.9. HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL(secure socket layer).10. TCP/IP: Transmission Control Protocol/Internet Protocol, the suite ofcommunication protocols used to connect hosts on the Internet. TCP/IPuses several protocols, the two main ones being TCP and IP.1.4 REFERENCES:http://msdn.microsoft.comhttp://java.sun.comhttp://www.asp.net1.5 TECHNOLOGIES TO BE USED: J2EE: (Servlet, JSP, JAXP, Java Beans) Application architecture. JAVA: Application architecture. WASCE: (WebSphere Application Server Community Edition) Web Server DB2: IBM Database. Localization: 3 Languages - Hindi, Kannada, and EnglishCode champs / Chitkara University 5|Page
  6. 6. Prison Management System Version 1.0 Software Requirements Specification 30-12-2010 Code champs 2. Overall Description:Describes the general factors that affect the product and its requirements.2.1. Product Perspective: The web pages (XHTML/JSP) are present to provide the user interfaceon customer client side. Communication between customer and server isprovided through HTTP/HTTPS protocols. The Client Software is to provide the user interface on system userclient side and for this TCP/IP protocols are used. On the server side web server is for EJB and database server is forstoring the information.2.2 Software Interface:Client on Internet: Web Browser,Operating System (any) Web Server: Apache Tomcat,Operating System (any) Data Base Server: MySQL,Operating System (any) Development End: NetBeans (J2EE, Java, Java Bean, Servlets,HTML), Database server (MySQL),OS (Windows XP professional),Apache Tomcat (Web Server)2.3 Hardware interface Client Side: processor ram disk space I.E. 6.0 or above Core2 Duo 2GB 160MB at 2.0Ghz Server Side: 1. Apache Tomcat pentium-3 4GB 500MB Server at 1GHz 2. MySQL 5.1.5 pentium-3 4GB 500MB at 1GHzCode champs / Chitkara University 6|Page
  7. 7. Prison Management System Version 1.0 Software Requirements Specification 30-12-2010 Code champs2.4 Product Function: prison management system should support this following use-caseClass of use Actors involved Use case Description of use case Police officer Login into accountUser account usage Administrator Login <includes> Data manager Invalid id or password <extends>Viewing data Administrator View Register 1.view nominal role 2.view case register Police officer 3.view in-out register 4.view parole register 5.view duty register <extends>Generating reports Administrator Report generation 1.prisoner wise report 2.case wise report 3.visitor wise reportConfirm Administrator Confirm interview All interview requests request by relatives ofInterview request PrisonersView release diary Administrator Viewing release diary Information of release Police officer date of prisonerPassword Administrator Change password Change of password Police OfficerCode champs / Chitkara University 7|Page
  8. 8. Prison Management System Version 1.0 Software Requirements Specification 30-12-2010 Code champs2.5 User Characteristics:Police Officer: should be given read only access to the information of prisoners.Data Manager: should be given the responsibility of adding or updating the existinginformation.Administrator: can be a Jail administrator or government official to handle thetroubleshooting or the managing of the system.2.6 Constraints: • Compatibility – Software should run compatibly (i.e. under the same operating system, database and networking capabilities) with the other subsystems software it works together with. – It should allow an Administrator to enroll new users and give them access rights to read the data. • Reliability and Availability – It should permit 1 hour per day for maintenance and backup activities with minimal disruption to users. – Any failure should cause no more than 10-minute downtime, with the average not exceding 2 minutes. – Backup should spot-tested to ensure they are reliable. – 24X7 availability – Better component design for to get better performance at peak time. – It should allow up to 10 users to logon simultaneously and receive an average response time not exceeding 3 seconds.2.7 Use Case model Description:The use case consists of three users : 1. Police officer: He who is provided with read only access to the information related to the prisoners. After logging in his own account, a police officer will be able to view information of criminals. He can then view nominal role, caseCode champs / Chitkara University 8|Page
  9. 9. Prison Management System Version 1.0 Software Requirements Specification 30-12-2010 Code champs register, in-out register, duty register, release diary and he has to confirm the interview requests by the relatives of criminals. 2. Administrator: can be a Jail Administrator or a government official. Has a right to view data and also generation of various reports. 3. Data Manager: Deals with the addition or updation of the existing data.USE CASE DIAGRAM:Code champs / Chitkara University 9|Page
  10. 10. Prison Management System Version 1.0 Software Requirements Specification 30-12-2010 Code champs2.8 Database Design:Database Specification: 1. Login Table:Serial Number Field name Type of field Remark1 Username Varchar(15) Primary key2 Password Number(10) -- 2. Nominal Roll Register:Serial number Fieldname Type of field Remark1 Prisoner id Number(1000) Primary key2 Case id Number(1000) Foreign key3 Name Varchar(15) No special characters allowed4 Gender Varchar(1) M/F5 Type Varchar(15) Duration specific/ life term6 Duration of Number(100000) No. of days sentence7 Height Number(500) In cms8 Criminal Snaps <img object> --9 Status Number(1) 1.in jail 2.on parole 3.released 4. dead 3. Case Register:Code champs / Chitkara University 10 | P a g e
  11. 11. Prison Management System Version 1.0 Software Requirements Specification 30-12-2010 Code champsSerial number Field name Type of variable Remark1 Case id Number(1000) Primary key2 description varchar(15) Special characters not allowed3 type Number(1) 1.murder 2.theft 3.forgery 4.counterfeiting 4. Parole Register:Serial number Field name Type of variable Remarks1 Prisoner id Number(1000) Primary key2 Address of Varchar(15) Special keys not residence allowed3 Entry date Date --4 Exit date Date --5 Remand frequency Number(1000) Should visit jail for days remand6 Last frequency days Number(1000) T/F7 Last remand visit Varchar(1) -- status8 Last visited on Date --Code champs / Chitkara University 11 | P a g e
  12. 12. Prison Management System Version 1.0 Software Requirements Specification 30-12-2010 Code champs3. Specific Requirements:We describe the functional requirements by giving various use cases:3.1 Use case reports:1. USE CASE RELATED TO LOGIN:Primary actorAll registered users having valid accounts1) Administrator2) Police Officer3) Data ManagerPreconditionINTERNET connection is available and working at its optimal levelMain scenario1) Users Access the login Page2) Provide User ID and Password.3) Login Validity is checked4) The user is shown their respective homepage.Alternate scenario1) The entered User ID or Password is not valid2) The user is shown the error page.2. USE CASE RELATED TO REGISTRATION:Primary actorUnregistered Police OfficersPreconditionnoneMain scenarioCode champs / Chitkara University 12 | P a g e
  13. 13. Prison Management System Version 1.0 Software Requirements Specification 30-12-2010 Code champs1. 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 updatedAlternate scenario1. The data completeness check fails and the user is prompted toprovide all details.2. The database update fails.3. USE CASE RELATED TO VIEW REGISTERS:Primary actorAdministratorPolice OfficerPrecondition 1. Administrator or Police Officer should be logged in to his accountMain scenario1. Retrieved the nominal roll register, case register, paroleregister, in-out register from the data base.2.Viewing of data.Alternate scenario1. Data retrieval process failed.4. USE CASE RELATED TO GENERATE REPORTS:Primary actorAdministratorPrecondition1. Administrator should be logged in to his accountMain scenarioCode champs / Chitkara University 13 | P a g e
  14. 14. Prison Management System Version 1.0 Software Requirements Specification 30-12-2010 Code champs 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 scenario1. Retrieval of data failed2. Printing out of retrieved data failed5. USE CASE RELATED TO INTERVIEW CONFIRMATION:Primary actorAdministratorPreconditionAdministrator should be logged in to his account to access this optionMain scenario1.Verification status is checked2. If OK then it is approved.3. The database is updated.Alternate scenario1. The interview request is not approved.6. USE CASE RELATED TO VIEWING OF RELEASE DIARY:Primary actor1) Administrator2) Police OfficerPrecondition1. User must be logged in2. He/she has to be at his home pageMain scenario1. Retrieved the release diary information from the data base.2.Viewing of data.Code champs / Chitkara University 14 | P a g e
  15. 15. Prison Management System Version 1.0 Software Requirements Specification 30-12-2010 Code champsAlternate scenario1. retrieval of data failed.7. USE CASE RELATED TO CHANGE OF PASSWORD:Primary actor 1. Administrator 2. Police OfficerPrecondition1. The users should have registered an account with the system.2. The users are logged into their account.Main scenario1. 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 .5. The Success page is shown.Alternate scenario1. The Old password doesnt match and the error page is shown.2. The Database Update fails .3.2 Supplementary Requirements:Performance requirement:1.Should run on 500 MHz, 256 MB machine.2.90% of the responses should be within 2 sec.Design Constraints:1. Security: The files in which the information regardingJailer ,Visitor, Prisoner should be secured againstmalicious deformations.Code champs / Chitkara University 15 | P a g e
  16. 16. Prison Management System Version 1.0 Software Requirements Specification 30-12-2010 Code champs2. Fault Tolerance: Data should not become corrupted in caseof system crash or power failure.3. External interface requirements:The external interface is a dynamically generated web page withprofessional graphicsCode champs / Chitkara University 16 | P a g e

×