Software Requirements

Specification
for

CRIME RECORDS
MANAGEMENT SYSTEM
Version 1.0

Prepared by Siddarth Mohan Kotewal

27-April-2022

TABLE OF CONTENT

TABLE OF CONTENT...............................................................................................................2
1. INTRODUCTION............................................................................................3
2. FEATURES.....................................................................................................3
3. PURPOSE ........................................................................................................3
4. SCOPE..............................................................................................................3
5. DEFINITIONSAND ABBEREVIATIONS .....................................................4
6. OVERVIEW .....................................................................................................4
7. OVERALL DESCRIPTION.............................................................................4
8. PRODUCT PERSPECTIVE ............................................................................4
9. PRODUCT FUNCTIONS ................................................................................5
9.1. PROCESS DATA ................................................................................................5
9.2. ADD USER.........................................................................................................5
9.3. SEARCH RECORD............................................................................................5
10. CONSTRAINTS, ASSUMPTIONS AND DEPENDENCIES.......................6
11. SPECIFIC REQUIREMENTS .......................................................................6
11.1. INTERFACE REQUIREMENTS...................................................................6
11.2. FUNCTIONAL REQUIREMENTS ...............................................................6
11.3. NON-FUNCTIONAL REQUIREMENTS .............................................................7
11.4. DESIGN CONSTRAINTS .....................................................................................7
 1. INTRODUCTION

CRMS is an android application which is supported on all android versions

above android KITKAT. This system will help to manage all the data of the
criminals of a jail. There are either only web-based applications or it is driven
manually in most of the organizations. The application will provide a multiuser
platform.

2. FEATURES

CRMS is an android application which is supported on all android versions

above android KITKAT. This application enables two types of authentication,
one is user authentication through which user can view data of criminals from
the database and other is the admin authentication through which admin can
add new users and add as well as modify criminal data.

3. PURPOSE

This document aims to give a brief description about the Criminal Record
Management System Project. With the help of this document the needs of the
police officers to get data of criminals anytime will be completed with very
ease.

4. SCOPE

This document covers the whole definition of the Criminal Record

Management System (CRMS) project. It basically includes data of criminals
which will be of great help to police officers. By taking security in
consideration, the authentication is of great concern. Also, normal users can
onlyview the records of criminal. Only admin can make changes to database.

 5. DEFINITIONSAND ABBEREVIATIONS

SRS: Software
Requirements Specification
CRMS: Criminal Record
Management System
CR: Criminal Record

6. OVERVIEW

This SRS is organized in a way that any user of the organization can easily
understand and use theCRMS. In other words, it constitutes a user guideline for
CRMS. Basically, this document starts with a brief explanation of the problem.
Later on, it continues with a detailed solution we proposed.Also block diagrams
of our solution to visualize the solution and system better, specific and
functional requirements, interface requirements, constraints that may be
confronted while developing the software, relationship between user types each
of which is a data object. This document ends with the planning and estimating
the basic schedule of our process.

7. OVERALL DESCRIPTION

The overall description of our project can be stated as creating and managing
the database, developing a friendly user interface to manipulate the database,
provide an authentication mechanism to safely accomplish tasks mentioned
above.

8. PRODUCT PERSPECTIVE

With the CRMS we will provide them with capabilities and properties

 organized neatly. CRMS which is an android application will be used by police

officers. Admin will basically query and edit the database via CRMS. They will
also add, update and delete data of criminals.

9. PRODUCT FUNCTIONS

CRMS implements some major functions in order to accomplish required

tasks. These functions constitute a basis for the whole system. These functions
can be stated as:

9.1. PROCESS DATA

These functions which can be examined in that process data major function are
basically provides admin to manage the database according to the desired task.
These management tasks constitute the major feature of the CRMS. With the
help of these functions a admin can update some basic data of criminals like
address, Aadhar number etc. In addition to update data, a user can also searchthe
database in order to obtain the list of the criminal record by comparing images.
Also, a user may also see the specific information about a criminal which can
be named as report.

9.2. ADD USER

Registration of a user will not be as straight forward. It will not be in the users’
hand to register himself. Only admin of the organization can add a new user by
verifying all the details of the userto be registered.

9.3. SEARCH RECORD

There are two types of search processes in this application. One is by entering
id of the criminal and other is by image, i.e. by providing an image as input.

 10. CONSTRAINTS, ASSUMPTIONS AND DEPENDENCIES

Regularity Policies: Each user must be a police officer, jailor, CBI officer.
Hardware Limitations: Since CRMS is an android application, the operating
system must be ANDROID with version greater than ANDROID KITKAT.
However, the CRMS system and the database will work on a server that needs
to be always online.

11. SPECIFIC REQUIREMENTS

11.1. INTERFACE REQUIREMENTS

All the user will be taken to a user authentication page. If the user is already
registered he/she canlogin directly through there or in case of admin there is an
option below the login button to go to admin authentication page. From there
admin can login. After login, admin will get three tabs as follows:

Add data tab: With the help of this tab, admin will be able to add data of the
criminal to databasesuch as name, contact number, address, Aadhar, etc.

Update data tab: his tab will enable the admin to update the record of the criminal in
the database.

Delete data tab: This tab will enable the admin to delete records of a particular
criminal from the database. If the user sign in as normal user instead of admin,
then he/she will get only one tab in which there will be only the listing of all
criminals present in the database.

11.2. FUNCTIONAL REQUIREMENTS

In this section, we will explain the major functions of CRMS along with the
data flow. So, the major functionality of the project such as authentication
mechanism, personal data processing, recruitment, report, and graphical user

 interface unit will explain step by step.

Authentication: Login User can login to the CRMS system with his/her
username and password.Logout User can logout from the CRMS system.
Login failure if the user does not exist in the database or the user did not get
authorized by the CRMS admin yet.

Authorization: User role check after logging in, the user role will be checked
from the database and the user interface will be created according to that role/
roles.

Process data: Display User with defined roles can display the content of the
database. Being more specific, a normal user can only view criminal data.
Admin can see not only criminal data but also alter the database. A normal user
can search a criminal record but entering the id of the criminal or by uploading
an image to the application.

11.3. NON-FUNCTIONAL REQUIREMENTS

Performance requirement: The number of online users of the CRMS can be

estimates as 50 at most. There is no restriction on the number of the users to be
added to the databases.

11.4. DESIGN CONSTRAINTS

Hardware Requirements: The CRMS application will be storing 500

criminals’ data which willroughly requires 100 MB of database storage space.

Software Requirements: Since our CRMS project is an android-based

application, so we will require mobile handsets for the deployment of the
project. To store and fetch the data to and from the database online i.e. MySQL
database on the localhost server, the user also requires an active internet
connection for smooth working of the project. The CRMS will run on any
mobile phone with android 4.4 or higher. Application will run on 256MB or
higher of RAM. It requires a spaceof 2.5 MB to deploy onto the machine.