Crime Records Management System – ASP.NET Project
The proposed system applies to all Police stations across the country and specifically looks into the subject of Crime Records Management. It is well understood that Crime Prevention, Detection and Conviction of criminals depend on a highly responsive backbone of Information Management. The efficiency of the police function and the effectiveness with which it tackles crime depend on what quality of information it can derive from its existing records and how fast it can have access to it.
It is proposed to centralize Information Management in Crime for the purposes of fast and efficient sharing of critical information across all Police Stations across the territory. Initially, the system will be implemented across Cities and Towns and later on, be interlinked so that a Police detective can access information across all records in the state thus helping speedy and successful completion to cases. The System would also be used to generate information for pro-active and preventive measures for fighting crime.
The project has been planned to be having the view of distributed architecture, with centralized storage of the database. The application for the storage of the data has been planned. Using the constructs of SQL server and all the user interfaces have been designed using the DOT Net technologies. The standards of security and data protective mechanism have been given a big choice for proper usage. The application takes care of different modules and their associated reports, which are produced as per the applicable strategies and standards that are put forwarded by the administrative staff.
- 1 Introduction to Project
- 2 Organization Profile
- Analysis Model
- Existing System
- Problem Statement
- Proposed System
Software Requirement Specification
- Product Overview
- Hardware Requirements
- Software Requirements
- Performance Requirements
- Data flow Diagrams
- DOTNET Framework
6.2. C# Introduction and Overview
1.1. Introduction to Project
The entire project has been developed keeping in view of the distributed client server computing technology, in mind. The specifications have been normalized up to 3NF to eliminate all the anomalies that may arise due to the database transaction that are executed by the general users and the organizational administration. The user interfaces are browser specific to give distributed accessibility for the overall system. At all proper levels high care was taken to check that the system manages the data consistency with proper business rules or validations. The authentication and authorization was crosschecked at all the relevant stages. The user level accessibility has been restricted into two zones namely. The administrative zone and the normal user zone.
Why new system?
- The system at any point of time can provide the details of the police station and the employees.
- The system at any point of time can provide the details of victims and the registered FIR’s
- The system at any point of time can provide the details of evidence and their sequence
- The system at any point of time can provide the details of existing charge sheets and their statuses.
2.1. Analysis Model
The model that is basically being followed is the WATER FALL MODEL, which states that the phases are organized in a linear order. First of all the feasibility study is done. Once that part is over the requirement analysis and project planning begins. If system exists one and modification and addition of new module is needed, analysis of present system can be used as basic model.
The design starts after the requirement analysis is complete and the coding begins after the design is complete. Once the programming is completed, the testing is done. In this model the sequence of activities performed in a software development project are: –
- Requirement Analysis
- Project Planning
- System design
- Detail design
- Unit testing
- System integration & testing
Here the linear ordering of these activities is critical. End of the phase and the output of one phase is the input of other phase. The output of each phase is to be consistent with the overall requirement of the system. Some of the qualities of spiral model are also incorporated like after the people concerned with the project review completion of each of the phase the work done.
WATER FALL MODEL was being chosen because all requirements were known beforehand and the objective of our software development is the computerization/automation of an already existing manual working system.
2.2 Existing System
The existing system contains the about all the police stations that are registered as per the jurisdiction of the system. It also gets integrated with the employees who are working in these stations along with their designation.
2.3. Problem Statement
The existing system doesn’t have system security. That means, the user can login in to system any where in the world. But the data in this system is not for public. To avoid this problem, the proposed system is developed as MAC enabled website. That means, the user can access the website in that system only, so that we can avoid the information leakage problem.
2.4. Proposed System
The system after careful analysis has been identified to be presented with the following modules:
- Police stations registration module: This module maintains the information about all the police stations that are registered as per the jurisdiction of the system. It also gets integrated with the employees who are working in these stations along with their designation.
- Victims FIR registration module: This module maintains the information related to the first investigation report of the crime sequences that have taken place. The Fir registers all that a data that is necessary for the investigation to take place in proper length. It identifies the crime category and the crime nature.
- Investigating evidence registration module: This module makes a collection of information related to all the evidences that become categorically important under the normal sequence of the investigation, this module dynamically concentrates upon the changes that take place while the system of investigation is under process.
3.0 Software Requirement Specification
Purpose: The main purpose for preparing this document is to give a general insight into the analysis and requirements of the existing system or situation and for determining the operating characteristics of the system.
Scope of the Development Project
Database Tier: The concentration is applied by adopting the Oracle 9i Enterprise versions. SQL is taken as the standard query language. The overall business rules are designed by using the power of PL/SQL components like stored procedures stored functions and database triggers.
User Tier: The use interface is developed is a browses specific environment to have distributed architecture. The components are designed using HTML standards and Java server pages power the dynamic of the page design.
Developer Responsibilities Overview
The developer is responsible for:
- Developing the system, which meets the SRS and solving all the requirements of the system?
- Demonstrating the system and installing the system at client’s location after the acceptance testing is successful.
- Submitting the required user manual describing the system interfaces to work on it and also the documents of the system.
- Conducting any user training that might be needed for using the system.
- Maintaining the system for a period of one year after installation.
3.2. Hardware Requirements
- PIV 2.8 GHz Processor and Above
- RAM 512MB and Above
- HDD 20 GB Hard Disk Space and Above
3.3. Software Requirements
- WINDOWS OS (XP / 2000 / 200 Server / 2003 Server)
- Visual Studio .Net 2005 Enterprise Edition
- Internet Information Server 5.0 (IIS)
3.4. Performance Requirements
Performance is measured in terms of the output provided by the application.
Requirement specification plays an important part in the analysis of a system. Only when the requirement specifications are properly given, it is possible to design a system, which will fit into required environment. It rests largely in the part of the users of the existing system to give the requirement specifications because they are the people who finally use the system. This is because the requirements have to be known during the initial stages so that the system can be designed according to those requirements. It is very difficult to change the system once it has been designed and on the other hand designing a system, which does not cater to the requirements of the user, is of no use.
The requirement specification for any system can be broadly stated as given below:
- The system should be able to interface with the existing system
- The system should be accurate
- The system should be better than the existing system
The existing system is completely dependent on the user to perform all the duties.