WSU-TC CptS 322

Software Requirements Specification Template

<CRIME MANAGEMENT SYSTEM>

Software Requirements Specification
<1.1>
<28.02.2014>
<NIKITA SINDWANI, SARANSH
GOYAL,ALISHA>
STUDENTS OF MCA, II YEAR

Prepared for
WSU-TC CptS 322Software Engineering Principles I
Instructor:Ms. Nidhi Kashyap,

<Project Name>

2014

Software Requirements Specification

Page ii

<Project Name>

Revision History
Date
28.02.201
4

Description
1.1

Author
NIKITA,SARANSH,ALISHA

Comments

Document Approval
The following Software Requirements Specification has been accepted and approved by the
following:
Signature
Printed Name
Title
Date
<Your Name>

Lead Software Eng.

A. David McKinnon

Instructor, CptS 322

Software Requirements Specification

Page iii

<Project Name>

Table of Contents
REVISION HISTORY...............................................................................................................................................III
DOCUMENT APPROVAL....................................................................................................................................... III
1. INTRODUCTION.....................................................................................................................................................1
1.1 PURPOSE............................................................................................................................................................... 1
1.2 SCOPE....................................................................................................................................................................1
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS................................................................................................ 2
1.4 REFERENCES......................................................................................................................................................... 2
1.5 OVERVIEW............................................................................................................................................................ 2
2. GENERAL DESCRIPTION.................................................................................................................................... 2
2.1 PRODUCT PERSPECTIVE........................................................................................................................................ 2
2.2 PRODUCT FUNCTIONS........................................................................................................................................... 2
2.3 USER CHARACTERISTICS...................................................................................................................................... 3
2.4 GENERAL CONSTRAINTS ......................................................................................................................................5
THE INTERNET CONNECTION IS ALSO A CONSTRAINT FOR THE APPLICATION. SINCE THE APPLICATION FETCHES
DATA FROM THE DATABASE OVER THE INTERNET, IT IS CRUCIAL THAT THERE IS AN INTERNET CONNECTION FOR
THE APPLICATION TO FUNCTION. THE USERS WILL BE CONSTRAINED BY THE CAPACITY OF THE DATABASE. SINCE
THE DATABASE IS SHARED AMONGST THE USERS, IT MAY BE FORCED TO QUEUE INCOMING REQUESTS AND
THEREFOR INCREASE THE TIME IT TAKES TO FETCH DATA......................................................................................... 5
2.5 ASSUMPTIONS AND DEPENDENCIES......................................................................................................................5
3. SPECIFIC REQUIREMENTS................................................................................................................................ 5
3.1 EXTERNAL INTERFACE REQUIREMENTS............................................................................................................... 5
3.1.1 User Interfaces............................................................................................................................................. 5
3.1.2 Hardware Interfaces.................................................................................................................................... 5
3.1.3 Software Interfaces.......................................................................................................................................6
3.1.4 Communications Interfaces..........................................................................................................................6
3.2 FUNCTIONAL REQUIREMENTS...............................................................................................................................6
3.2.1 <Functional Requirement or Feature #1>.................................................................................................. 6
3.2.2 <Functional Requirement or Feature #2>.................................................................................................. 7
3.3 USE CASES............................................................................................................................................................7
3.4.1 <Class / Object #1>.....................................................................................................................................8
3.4.2 <Class / Object #2>.....................................................................................................................................8
3.5 NON-FUNCTIONAL REQUIREMENTS...................................................................................................................... 9
3.5.1 Performance.................................................................................................................................................9
3.5.2 Reliability..................................................................................................................................................... 9
3.5.3 Availability................................................................................................................................................... 9
3.5.4 Security.........................................................................................................................................................9
3.5.5 Maintainability.............................................................................................................................................9
3.5.6 Portability.................................................................................................................................................... 9
3.6 INVERSE REQUIREMENTS......................................................................................................................................9
3.7 DESIGN CONSTRAINTS.......................................................................................................................................... 9
3.8 LOGICAL DATABASE REQUIREMENTS.................................................................................................................. 9
3.9 OTHER REQUIREMENTS........................................................................................................................................ 9
4. ANALYSIS MODELS.............................................................................................................................................. 9
4.1 SEQUENCE DIAGRAMS........................................................................................................................................ 10
4.3 DATA FLOW DIAGRAMS (DFD)..........................................................................................................................10
4.2 STATE-TRANSITION DIAGRAMS (STD)...............................................................................................................14
5. CHANGE MANAGEMENT PROCESS.............................................................................................................. 14

Software Requirements Specification

Page iv

<Project Name>
A. APPENDICES........................................................................................................................................................ 14
A.1 APPENDIX 1........................................................................................................................................................14
A.2 APPENDIX 2........................................................................................................................................................14

Software Requirements Specification

Page v

<Project Name>

1. Introduction
1.1 Purpose
The purpose of the document is to collect and analyze all assorted ideas that have come up to
define the system, its requirements with respect to consumers. Also, we shall predict and sort out
how we hope this product will be used in order to gain a better understanding of the project,
outline concepts that may be developed later, and document ideas that are being considered, but
may be discarded as the product develops.
In short, the purpose of this SRS document is to provide a detailed overview of our software
product, its parameters and goals. This document describes the project's target audience and its
user interface, hardware and software requirements. It defines how our client, team and audience
see the product and its functionality. Nonetheless, it helps any designer and developer to assist in
software delivery lifecycle (SDLC) processes.

1.2 Scope
The project titled as Online Crimefile Management is a web based application. This software
provides facility for reporting online crimes, complaints, missing persons, show most wanted
person details mailing as well as chatting. Any Number of clients can connect to the server. Each
user first makes their login to server to show their availability. The server can be any Web
Server. An SMTP Server must be maintained for temporary storage of emails and chat jar files
for enable the chatting facilities.The main modules in this project
The intended audience are:

Visitors-views hot news.

Registered Users-can add and view missing person reports, complaints, crime reports and
view details of most wanted people.

Administrator-can view and manage missing persons FIR, replies the register users
complaints and grievances, and also manages database related to most wanted people,
prisoners and hot news.

Software Requirements Specification

Page 1

<Project Name>

1.3 Definitions, Acronyms, and Abbreviations

This subsection should provide the definitions of all terms, acronyms, and abbreviations
required to properly interpret the SRS. This information may be provided by reference to one or
more appendixes in the SRS or by reference to other documents.

1.4 References
This subsection should:
(1) Provide a complete list of all documents referenced elsewhere in the SRS, or in a separate,
specified document.
(2) Identify each document by title, report number - if applicable - date, and publishing
organization.
(3) Specify the sources from which the references can be obtained.
This information may be provided by reference to an appendix or to another document.

1.5 Overview
The remaining sections of this document provide a general description, including characteristics
of the users of this project, the product's hardware, and the functional and data requirements of
the product. General description of the project is discussed in section 2 of this document.
Section 3 gives the functional requirements, data requirements and constraints and assumptions
made while designing the Crime File Management system. It also gives the user viewpoint of
product. Section 3 also gives the specific requirements of the product. Section 3 also discusses
the external interface requirements and gives detailed description of functional requirements.
Section 4 is for supporting information.

2. General Description
2.1 Product Perspective

2.2 Product Functions

The project titled as Online Crimefile Management is a web based application. This software
provides facility for reporting online crimes, complaints, missing persons, show most wanted
person details mailing as well as chatting. Any Number of clients can connect to the server. Each
user first makes their login to server to show their availability. The server can be any Web
Server. An SMTP Server must be maintained for temporary storage of emails and chat jar files
for enable the chatting facilities.

Software Requirements Specification

Page 2

<Project Name>

2.3 User Characteristics

Modules

Visitors

Registered Users

Administrator

The visitor module include

View Hot news: This module helps the visitor to see the latest hot news which can be
updated by the admin.

The registered user module includes

Add Complaint: This module helps the user to report complaints online.
Add Crime report: This module helps the user to report crimes online.
Add Missing person: This module helps the user to report missing persons details online
and also add photos of missing person.
View Missing persons: This module helps the user to view all the missing persons
details.
View Most Wanted persons: This module helps the user to view all most wanted persons
which can be given by the administrator.
Edit Complaint: This module helps the user to edit his or her complaint details.
Edit Account: This module helps the user to update his or her profile.
View complaint status: This module allows viewing the status of all complaint that he/she
has posted earlier.
View crime status: This module allows viewing the status of the all crimes that he/she has
posted earlier.
Add and View feedback: This module helps the user to add and view feedbacks
Chat: This module help the user to chat with the administrator or with other registered
users
Mail: This module helps the user to send mail to the administrator.
Software Requirements Specification

Page 3

<Project Name>

The administrator module includes

View and reply user complaint: This module helps the admin to view and reply users
complaint details
View and reply user crimes: This module helps the admin to view and reply users crimes
details
New admin: This module is used for add new admin
Add and delete latest hot news: This module helps the admin to add and delete latest hot
news.
View and delete users feedback: This module helps the admin to add and delete users
feedback.
Add, delete and view most wanted persons: This module helps the admin to add, delete
and view most wanted person details
Add, delete and view missing persons: This module helps the admin to add, delete and
view missing person details
Add and view Criminal registration: This module helps the admin to add and view
criminal registrations
Add and view FIR: This module helps the admin to add and view Fir reports
Add and view history sheet: This module helps the admin to add and view history reports
View and delete all complaint reply: This module helps the admin to view and delete
complaint reply.
Add and view prisoner report: This module helps the admin to add and prisoner reports
Change password: This module helps the admin to update his or her password
Chat: This module help the admin to chat with the administrator or with other registered
users
Mail: This module helps the user to send mail to the user.

Software Requirements Specification

Page 4

<Project Name>

2.4 General Constraints

The Internet connection is also a constraint for the application. Since the
application fetches data from the database over the Internet, it is crucial
that there is an Internet connection for the application to function. The
users will be constrained by the capacity of the database. Since the
database is shared amongst the users, it may be forced to queue incoming
requests and therefor increase the time it takes to fetch data.
2.5 Assumptions and Dependencies
We are assuming that our software would be backward compatible and requires high speed
internet for uploading purpose.

3. Specific Requirements
This will be the largest and most important section of the SRS. The customer requirements will
be embodied within Section 2, but this section will give the D-requirements that are used to
guide the projects software design, implementation, and testing.
Each requirement in this section should be:
Correct
Traceable (both forward and backward to prior/future artifacts)
Unambiguous
Verifiable (i.e., testable)
Prioritized (with respect to importance and/or stability)
Complete
Consistent
Uniquely identifiable (usually via numbering like 3.4.5.6)
Attention should be paid to the carefuly organize the requirements presented in this section so
that they may easily accessed and understood. Furthermore, this SRS is not the software design
document, therefore one should avoid the tendency to over-constrain (and therefore design) the
software project within this SRS.

3.1 External Interface Requirements

This section provides a detailed description of all inputs into and outputs from the system. It also
gives a description of the hardware, software and communication interfaces and provides basic
prototypes of the
user interface.
3.1.1 User Interfaces
3.1.2 Hardware Interfaces
Processor
:
Pentium III/AMD Athlone XP
Software Requirements Specification

Page 5

<Project Name>
RAM

Hard disk

FDD

128 MB

20 GB
:

1.44MB

Monitor

14 inch

Mouse

3 Button scroll

CD Drive

52 X

Keyboard

108 keys

3.1.3 Software Interfaces

Operating System

Windows 2000/xp

Languages

java 2(EJB2.0, JDBC, JSP, Servlet, Java Mail)

Front End

HTML, JavaScript

Platform

J2EE

Web Servers

Web Logic8.1/Tomcat 5.0

Backend

Browser Program

My SQL
: Internet explorer/Mozilla Fireworks

3.1.4 Communications Interfaces

Client (system user) on Internet will be using HTTP/HTTPS protocol.

Client (system user) will be using SMTP protocol for Mailing Services.

3.2 Functional Requirements

This section describes specific features of the software project. If desired, some requirements
may be specified in the use-case format and listed in the Use Cases Section.
3.2.1 <Functional Requirement or Feature #1>
3.2.1.1 Introduction
3.2.1.2 Inputs
3.2.1.3 Processing
3.2.1.4 Outputs
Software Requirements Specification

Page 6

<Project Name>
3.2.1.5 Error Handling
3.2.2 <Functional Requirement or Feature #2>

3.3 Use Cases

View Hot News

Visitor

Sign Up

Edit Account

Manage Account

View Missing Person

Add & Edit Crime Report

Add & Edit Complaint

Add & Edit Missing Person

View Most Wanted

Registered
User
View Complaint Status

View Crime Report Status

Software Requirements Specification

Page 7

<Project Name>

Add Hot News

Add Most Wanted

Add Missing Person

Add

Add Criminal Registration

Add Prisoner Report
Add FIR

User's Crime Report

Users's Feedback
Admin
View

Most Wanted Person

User's Complaint
Missing Person
Criminial Registration

Prisoner's Report

Hot News
Complaint Reply

Delete

Feedback

Most Wanted Person

Missing Person

3.4.1 <Class / Object #1>

3.4.1.1 Attributes
3.4.1.2 Functions
<Reference to functional requirements and/or use cases>
3.4.2 <Class / Object #2>

Software Requirements Specification

Page 8

<Project Name>

3.5 Non-Functional Requirements

Non-functional requirements may exist for the following attributes. Often these requirements
must be achieved at a system-wide level rather than at a unit level. State the requirements in the
following sections in measurable terms (e.g., 95% of transaction shall be processed in less than
a second, system downtime may not exceed 1 minute per day, > 30 day MTBF value, etc).
3.5.1 Performance
3.5.2 Reliability
3.5.3 Availability
3.5.4 Security
3.5.5 Maintainability
3.5.6 Portability

3.6 Inverse Requirements

State any *useful* inverse requirements.

3.7 Design Constraints

Specify design constrains imposed by other standards, company policies, hardware limitation,
etc. that will impact this software project.

3.8 Logical Database Requirements

Will a database be used? If so, what logical requirements exist for data formats, storage
capabilities, data retention, data integrity, etc.

3.9 Other Requirements

Catchall section for any additional requirements.

4. Analysis Models
List all analysis models used in developing specific requirements previously given in this SRS.
Each model should include an introduction and a narrative description. Furthermore, each
model should be traceable the SRSs requirements.

Software Requirements Specification

Page 9

<Project Name>

4.1 Sequence Diagrams

4.3 Data Flow Diagrams (DFD)

Context flow diagram

Complaint Management

UserID, Complaints
User

Online Crime
File System

Administrator

Solutions,
Feedback

Level 1 DFD- Administrator

Software Requirements Specification

Page 10

<Project Name>
Administrator

Registration details
User name, Password

View user details

Online
Crime
File
System

Login

View Complaints
Complaints

Add Solutions
View Feedback
User

Feedback
Add FIR Reports

Add mortem analysis

FIR

Mortem Details

Level 2 DFD- Administrator

Software Requirements Specification

Page 11

<Project Name>

View
complaints

Administrator

FIR
Management

Logi
n

Complaints
Complaint
Details

FIR No:
Details
FIR
FIR Details

Postmortem
Management

Mortem details
Mortem
Details

Report
Generation

User

Add
Reports

Reports

View
Reports

Software Requirements Specification

Page 12

<Project Name>
Level 1 DFD- User

Registration

Registration

User

Username/Password
Username/Password

Login

Verify
Login

Complaints
Complaints
Complaint
Registration

Level 2 DFD- User

Collectin
g
Feedbac
k

User
User name
Password

Login

Solutions

Complaint
Registratio
n

Feedback

Complaint

Complaint Details
Complaint ID
Complaint Status
Complai
nt Status

Complaint Status

Software Requirements Specification

Page 13

<Project Name>

4.2 State-Transition Diagrams (STD)

5. Change Management Process

Identify and describe the process that will be used to update the SRS, as needed, when project
scope or requirements change. Who can submit changes and by what means, and how will these
changes be approved.

A. Appendices
Appendices may be used to provide additional (and hopefully helpful) information. If present,
the SRS should explicitly state whether the information contained within an appendix is to be
considered as a part of the SRSs overall set of requirements.
Example Appendices could include (initial) conceptual documents for the software project,
marketing materials, minutes of meetings with the customer(s), etc.

A.1 Appendix 1
A.2 Appendix 2

Software Requirements Specification

Page 14