Software Requirements

Specification
For Crime Reporting System

Version 1.0 approved

Prepared by

PAIA DONDOR SIANGSHAI 01FB16ECS474

NAMAN MITTAL 01FB16ECS472
NIDHEESH S N 01FB16ECS900
V KARTHIK PRABHU 01FB17ECS715

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for Crime Reporting system
Page ii

Table of Contents
Table of Contents.................................................................................................ii
Revision History...................................................................................................ii
1. Introduction....................................................................................................1
1.1 Purpose................................................................................................................................1
1.2 Document Conventions........................................................................................................1
1.3 Intended Audience and Reading Suggestions......................................................................1
1.4 Product Scope......................................................................................................................1
1.5 References............................................................................................................................1
2. Overall Description..........................................................................................2
2.1 Product Perspective.............................................................................................................2
2.2 Product Functions................................................................................................................2
2.3 User Classes and Characteristics..........................................................................................2
2.4 Operating Environment........................................................................................................2
2.5 Design and Implementation Constraints..............................................................................2
2.6 User Documentation............................................................................................................2
2.7 Assumptions and Dependencies..........................................................................................3
3. External Interface Requirements.....................................................................3
3.1 User Interfaces.....................................................................................................................3
3.2 Hardware Interfaces.............................................................................................................3
3.3 Software Interfaces..............................................................................................................3
3.4 Communications Interfaces..................................................................................................3
4. System Features..............................................................................................4
4.1 System Feature 1..................................................................................................................4
4.2 System Feature 2 (and so on)...............................................................................................4
5. Other Nonfunctional Requirements.................................................................4
5.1 Performance Requirements.................................................................................................4
5.2 Safety Requirements............................................................................................................5
5.3 Security Requirements.........................................................................................................5
5.4 Software Quality Attributes..................................................................................................5
5.5 Business Rules......................................................................................................................5
6. Other Requirements........................................................................................5
Appendix A: Glossary...........................................................................................5
Appendix B: Analysis Models...............................................................................5
Appendix C: To Be Determined List.......................................................................6

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for Crime Reporting System Page 1

1. Introduction

1.1 Purpose

This Software Requirements Specification provides a complete

description of all the functions and specifications of the Crime Reporting
System.
Crime Reporting System allows user to store police department’s case
details, Complaint Details, FIR Details, etc. This Software Package allows
Police Departments to store all the details related to the department and
use them whenever necessary. This project will also be able to provide
reports of various cases, FIR report, charge sheet report, Most Wanted
Criminals record, payroll, attendance reports and also be able to upload
and view criminal photos and scanned documents.

1.2 Document Conventions

This document uses the following conventions.
 Dataflow diagram
 Class Diagram

1.3 Intended Audience and Reading Suggestions

This project is a prototype for Crime reporting system and it is restricted

within the college premises. This has been implemented under the
guidance of college professors. This project is useful for the Police Officers
and as well as to the people to help to report crimes and get updates
related to the crimes happening in their areas.
Software Requirements Specification for Crime Reporting System Page 2

1.4 Product Scope

Online Crime Reporting System project’s main idea is to implement an

automated software application for maintaining the proper common
people complaints of different police departments. By using this
application people who are afraid or don’t have enough time to go police
station for complaint about their personal legal issues here they can give
their complaint through online to register any type of complaint.

2. Overall Description

2.1 Product Perspective

A Crime Reporting System stores the following information.

 It contains all the details related to the department and use them
whenever necessary.
 It has information for the crimes reported and all the wanted
criminals on the web application.
 The public can easily access the data which shows the latest crime
reports.
 It also contains the information of the nearest police station and
how to contact them for emergencies.
 Any reports or FIR filed by the user can be check online to see the
status of the report and actions taken.

2.2 Product Functions

The major features of Crime Reporting system as shown in below
Software Requirements Specification for Crime Reporting System Page 3
Software Requirements Specification for Crime Reporting System Page 4
Software Requirements Specification for Crime Reporting System Page 5
Software Requirements Specification for Crime Reporting System Page 6
Software Requirements Specification for Crime Reporting System Page 7

2.3 User Classes and Characteristics

The various users or actors who all will be involved in the system are:
 Administer: Administer will have the complete control over the system. They will have the 
technical access to the system. The role of the administrator involves a great deal of 
multitasking like track, compile and analyze website using data. The admin is responsible 
for providing service to victims.
 Citizens: whenever any crime is going on in the locality, it is the duty of every individual to 
take action against it. Citizens are the members joined in the system. They will have access 
to all the services of the system.
 Police Officers: The police department plays a major role in crime management system in 
preventing the criminal activity. Therefore, in each locality there should be a police stations. 
The officers work according to the orders given by the admin.
 NGO’s : These are the Non­ Government organizations who mostly help in nonsocial 
activities like any crime against women empowerment and others. They conduct several 
campaigns which would be useful to act against the crimes.

2.4 Operating Environment

Operating environment for Crime Reporting system is as listed
below.
Server side
Front End : ASP.NET 3.5, Microsoft Framework3.5
Back End : SQL
OS : Windows
Browser : Firefox, Google Chrome, Safari
Minimum Requirement
Processor : Pentium 4 or Later, 1.8GHz
System Memory : 256 MB

Hard Disk : 20 GB
Recommended Requirement
Processor : Pentium 4 or Later
System Memory : 1 GB
Hard Disk : 40 GB
Software Requirements Specification for Crime Reporting System Page 8

2.5 Design and Implementation Constraints

Developers need to keep in mind that the End users database linked to the CWC need to be 
accessible all the times and should never lead to any loss of information. The software developed 
should be such that it should take minimum amount of load time. The capital investment over the 
whole setup of the cloud based database along with the required number of system is limited and 
thus should be met with proposed budget. It would be better to implement it using bootstrap so as to
accommodate in mobile devices.

2.6 Assumptions and Dependencies

The software works best on the assumption that the latest versions of web browsers will be used to 
access the website and the servers are to be kept up and running at all times so that the link to site is 
never broken and it should be accessible for 24*7. Further the site depends on the reliability and 
safety factors which will be further discuss in non­ functional requirements. It is needed to think 
about a future way of making the system more efficient and easily accessible.

3. External Interface Requirements

3.1 User Interfaces

 Front-end software: Vb.net version
 Back-end software: SQL+

3.2 Hardware Interfaces

 Windows.
 A browser which supports CGI, HTML & Javascript.

3.3 Software Interfaces

Following are the software used for Crime Reporting System
online application.
Software used Description

We have chosen Windows operating system for its best support and

Operating system user-friendliness.

Database To save the FIR, files and complaints we have chosen SQL+ database.
Software Requirements Specification for Crime Reporting System Page 9

To implement the project we have chosen Vb.Net language for its more

VB.Net interactive support.

3.4 Communications Interfaces

This project supports all types of web browsers. We are using
simple electronic forms for the user complaints and reports.

4. System Features
The system features could simply be stated in the form if Functional Requirements. This 
Basically includes the user and the requirements for their authentication followed by the 
level of abstraction that they provided with while displaying the different segments if the 
system.

4.1 Registration

4.1.1 Description and Priority

All the citizens, admin, police officers and NGOs need to register with the
system by providing personal details that is required during the registration in order to
avail the facilities of the system. On successful registration, a user id and password
would be provided to them. They can use these credentials for future assistance. The
priority for this functionality is average.

4.1.2 Stimulus/Response Sequences

In this feature the user needs to specify their name and personal detail. The job
type is a priority in this that directs them to a page for inputting information that
is different for all job types. The user id and password are another priority that
needs to be inputted to move further in the process.

4.1.3 Functional Requirements

To avail the services of the system one must go through a registration process.
The registration process will be different for different actors.
INPUT: Members basic information
OUTPUT: registered successfully and supply user id and password
Software Requirements Specification for Crime Reporting System Page 10

4.2 Login

4.2.1 Description and Priority

A registered member of the system can login to the system by providing his user id and 
password as set by the him during the registration. If a user has not yet registered, he cannot 
access the home page and login failure message would be shown to him and he would be 
redirected to the sign up page. Priority for this is high as without logging in a user can’t use 
the software. 

4.2.2 Stimulus/Response Sequences

In this feature, the users need to specify their user id and password in their respective login 
pages that is different for different job type. Only after they login they can access the 
functionalities of the system.

4.2.3 Functional Requirements

Login page is very important in order to access functionalities of the system. After login 
citizen, NGOs, admin get access to their respective accounts and their functionalities. They 
can then report crime as victim, take immediate action as a admin, and act against the crime 
as a police officer and NGO.

4.3 News Section

4.3.1 Description and Priority

The news section would be the area where information and news about the crime is posted. 
The news would be about the recently criminal activity going on and the scars and loss it 
would have done to the people. The priority of this functionality s average.

4.3.2 Stimulus/Response Sequences

The admin can post any current news which he thinks that the citizens should be aware of. 
The response of the people could be seen in the comment section.

4.3.3 Functional Requirements

INPUT: NEWS about crime
OUTPUT: News Posted on the news section
Software Requirements Specification for Crime Reporting System Page 11

4.4 Complaint Registration

4.4.1 Description and Priority

Any member of the system can report a crime against any kind of criminal activities. All the 
information needed are mandatory. If he fails to fill any of these, error would be shown. The 
priority for this functionality is high.

4.4.2 Description and Priority

Here the crime details would be entered by the victim and then the managing authority 
would respond to it through the actions they take. The actions taken should be effective and 
should be effective.

4.4.3 Functional Requirements 

The victim has to report crime against any criminal activities and then a confirmation dialog 
box would be shown after the crime has been reported successfully.

INPUT: crime category, description and date of crime, incident location, attachments
OUTPUT: notification will be sent to the member reporting the crime.

Other Nonfunctional Requirements

4.5 Performance Requirements

The hardware end of the system should be very much efficient in performance. The system should 
be accessible 24*7. The system should perform well when many users can access the software 
simultaneously. Also the reports which sent by the members should only be read by the managing 
authority, others can’t read or access it. The system should support backup ad recovery. It will help 
the police officers to maintain old records of the crime in proper statistics so that whenever any 
member or administrator wants to search some data, can find it easily  

4.6 Safety Requirements

If there is extensive damage to a wide portion of the database
due to catastrophic failure, such as a disk crash, the recovery
method restores a past copy of the database that was backed up
to archival storage (typically tape) and reconstructs a more
current state by reapplying or redoing the operations of
Software Requirements Specification for Crime Reporting System Page 12

committed transactions from the backed up log, up to the time of

failure.

4.7 Security Requirements

Security systems need database storage just like many other
applications. However, the special requirements of the security
market mean that vendors must choose their database partner
carefully.

4.8 Software Quality Attributes

These are the following software quality Attributes of the system
 Availability
 Maintainability
 Correctness
 Usability

4.9 Other Requirements

Other requirements would be to include fingerprint authentications. Through this the 
complaints registered remain secure and the personal details of the victims too are protected.
This requirement makes the system more secure and the outsiders cant access it.