0% found this document useful (0 votes)
1K views2 pages

Criminal Record Management

The document outlines requirements for a Criminal Record Management System with the objective of implementing the system for jailers, police, and CBI officers. It describes functional requirements for users including registering criminals, searching records, and accessing criminal information. Non-functional requirements include secure access, 24/7 availability, and performance. Optional features, user interface priorities, and technologies to be used are also specified.

Uploaded by

Sourav Roy
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
1K views2 pages

Criminal Record Management

The document outlines requirements for a Criminal Record Management System with the objective of implementing the system for jailers, police, and CBI officers. It describes functional requirements for users including registering criminals, searching records, and accessing criminal information. Non-functional requirements include secure access, 24/7 availability, and performance. Optional features, user interface priorities, and technologies to be used are also specified.

Uploaded by

Sourav Roy
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Name of the project : Objective /Vision User of the system

Criminal Record Management Implement the Criminal Record Management System for Jailers, Police and CBI Officers. 1. 2. 3. 4. 5. Jail Superintendent. Police Officers. CBI Officers. Administrator. Judge

Functional Requirements

Jail Superintendent 1. Register the new Criminal. 2. Record the Crime type and details of the crime. 3. Take the information like photo from 3 different view, blood group, finger print, retina scan and DNA information. 4. Search Criminal with any of the above input. 5. Update the new crime of existing criminal. 6. Maintain the current location of the criminal (i.e. Cell No., Jail Name etc.) 7. Maintain the records of meeting with outsiders. 8. Record the data of health condition if any. 9. Assign works Police Officers 1. Search the criminal by name/blood group/type of crime/Jail No. /DNA/Image/Sketch. 2. Transfer the criminal to another jail. 3. Access full information of criminals. CBI Officers 1. Search the criminal by name/blood group/type of crime/Jail No. /DNA/Image/Sketch. 2. Access full information of criminals. Administrator 1. Maintain the database. 2. Grant/Revoke role to/from other Users. 3. Backup and restore of data. 4. Monitor the Jail Administration. Judge 1. 2. 3. 4. Access information of criminals. Also access information about other Users. Reduce/Increase the level of punishment. Transfer the criminal to other location.

Non-Functional Requirements

i. ii. iii.

Secure access of confidential data (users details). SSL can be used. 24 X 7 availability Better component design to get better performance at peak time

Optional Features User Interface Priorities

iv. Flexible service based architecture will be highly desirable for future extension 1. Enhancements / hooks for integration with other state run welfare schemes and information services. A. Professional look and feel B. Use of AJAX atleast with all registration forms C. Browser testing and support for IE, NN, Mozila, and Firefox. D. Use of Graphical tool like JASPER to show strategic data to admin E. Reports exportable in .XLS, .PDF or any other desirable format 1. Registration confirmations. 2. Statement of security and privacy. 3. Print outs for employment history, funds disbursal, etc. 1. Simplicity of interface. 2. Minimal text (only where needed). 3. Complete separation of access to data based on roles: Consumers, Administrators, Managers and Public Review. 2 4 members UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA ROSE/RSA / WebSphere Modeler Eclipse/ RAD / Lotus Forms Designer / Portlet Factory WebSphere Portal/ WAS/ WAS CE / WPS DB2 Express C or DB2 UDB

Reports

Other Important Issues

Team Size Technologies to be used Tools to be used

Final deliverables must include

Tivoli CDP/TSM / Tivoli Directory Server Linux will be the preferred OS. A. Online or offline help to above said users, Application deployment executive and developer B. Application archive ( .war/.ear ) with source code C. Database backup and DDL Script D. Complete Source code

Documents

You might also like