Final doc

ABSTRACT

To secure common citizens, police department is under taking a major rescue
operations and giving protection to us. So in order to acquire such services from
them in the right time and keep ourselves in protective shield police departments
took a step forward and introduced technical system “e-COPS”.

electronic Computerized Operations for Police Service

• “Serving those who protect”

• Users of the system citizen, police officer and the admin.

• Citizen can place complaints, apply for license and tracks the status of
them.

• Police officer can update the status of license and complaints.

• Admin can create a new police station and also add new police.

Contents
Abstract

List of figures

List of tables

Chapter 1 Introduction

1.0 Introduction to this chapter

1.1vision

1.2Objective

1.3Scope

1.4Technology

Chapter 2 Analysis

2.0 Introduction

2.1Usecase

2.2Test cases

2.3SRS

Chapter 3 Design

3.0Introduction

3.1Usecase diagram

3.2Sequence diagram

Chapter 4 Implementation Technology

4.0Introduction

4.1Module name and description

Chapter 5 Testing and Screens

5.0Introduction

5.1Test results

5.2Screens

5.3conclusion

List of Figures

Sno Figure No Figure Name
1 1 Class diagram

2 2 Usecase diagram
3 3 Sequence diagrams

SLNO

TABLE

NO

TABLE

NAME

1

1

Citizen

zone

2

2

Police

station

3

3

police

4

4

Login

5

Screens
Screeen1…………………………………………………………..Home page

Screeen2…………………………………………………………..Registration

Screeen3…………………………………………………………..Login

Screeen4………………………………………………………….Complaint registering

Screeen5…………………………………………………………..Complaint status

Screeen6… …………………………………………………Updating complaint status

Screeen7…………………………………………………………..Criminal details

Chapter1

Introduction

1.0 Introduction to This Chapter

1.1Introduction:
The project is for providing a way to the citizens to complaint who is busy in their
own works single interface. The user can search any of the above mentioned files starting with
Query string entered.

It provides the user to view, the image or play the audio/video files .This project gives
you clear picture by giving novel solution in immediate searching of mobile in an organized way,
in no second .And the same with playing audio/video files and searching for contacts. The
system uses current mobile and web technology to achieve all these handful output. Mobile
Search is an evolving branch of information retrieval services that is centered around the
convergence of mobile platforms and mobile phones and other mobile devices.

1.2Vision:
"Serving those who protect"
To deliver next generation police and law enforcement reporting tools, and setting up
intelligence platforms that agencies use to take incoming incident reports, lessen live employee
resources and allow these enforcement agencies to reallocate resources to much needed
community areas

1.3 Objective:
To secure common citizen, police department is undertaking rescue operations and giving
protection to them. In order to acquire such services from them in the right time and keep
ourselves in protective shield police departments took a step forward and introduced technical
system “e-COPS”.

1.4Scope:

To deliver next generation police and law enforcement reporting tools and setting up intelligence
platforms that agencies use to take incoming incident reports lessen live employ resources and
allow these enforcement agencies to reallocate resources to much needed community areas.

1.5Technology

Software Requirements:
a. Front End Tools:

1.HTML

2.JSP

3.SERVLETS

b. Back End Tools: Java DB

Glassfish sever V2.0

c. Tools used:

NetBeans 6.5

Hardware Requirements:

• 80GB hard disk

• 1GB R.A.M

Chapter 2

Analysis

2.0 Introduction

The analysis phase defines the requirements of the system, independent of how these
requirements will be accomplished. This phase defines the problem that the customer is trying to
solve. The deliverable result at the end of this phase is a requirement document. Ideally, this
document states in a clear and precise fashion what is to be built. This analysis represents the
``what'' phase. The requirement document tries to capture the requirements from the customer's
perspective by defining goals and interactions

The analysis team develops the requirement document, which talks about things and actions on
things. This document should also include states, events, typical scenarios of usage, and a typical
scenarios of usage

2.1 Use case

A use case in software engineering and systems engineering is a description of a system’s

behavior as it responds to a request that originates from outside of that system. In other words, a

use case describes "who" can do "what" with the system in question. The use case technique is

used to capture a system's behavioral requirements by detailing scenario-driven threads through

the functional requirements. Usecase specifies what to do but does not specify how to do. It only

specifies functional requirements of the system.

2.2 Test Cases

A test case in software engineering is a set of conditions or variables under which a tester will

determine whether an application or software system is working correctly or not. The mechanism

for determining whether a software program or system has passed or failed such a test is known

as a test oracle. It may take many test cases to determine that a software program or system is

functioning correctly. Test cases are often referred to as test scripts, particularly when written.

Written test cases are usually collected into test suites.

The test cases in the project are:
Requirement lookup table :

S.No Requirement Requirement Name Source Stable Priority Need Verifiable(y/
ID (customer/vendor) (Y/N) n)

1 ECPS-UR-01 Registration Citizen/police Y high Essential y
2 ECPS-UR-02 Place complaint Citizen Y high Essential y

3 ECPS-UR-03 Apply for license Citizen Y high Essential y

4 ECPS-UR-04 View police station Citizen Y high Essential y

5 ECPS-UR-05 View complaint Citizen Y high Essential y
status
6 ECPS-UR-06 View license status Citizen Y high Essential Y

7 ECPS-UR-07 Process complaint Police Y high Essential Y
request
8 ECPS-UR-08 Process license Police Y high Essential Y
request

Requirement ID ECPS-UR-01
Title Registration
Description The purpose of registration is:
-provides proof of citizenship.
-provides proof of police.

Actor Citizen/police
Input Login id, name, address, contact, Citizen id/ employee id, email id.
Behavior • store the details in application
• Validate details.
Output Login id
Pre condition Citizen/police should have the citizen id/police id.
Post condition E-mail login id to the Citizen/police
Exceptions If there is a problem in storing information or generating login id display error
message
Use case diagram

Citizen/police Registration

Special instructions NA

Title Place complaint
Description The purpose of this use case is :
To give complaint .

Actor Citizen
Input Complaint on, description.
Behavior • Store the details in complaint form
• Generate complaint id.
Output Complaint id
Pre condition 1. Citizen should be logged in.
2. Complaint on.
Post condition Email complaint id to the Citizen.
Exceptions If there is a problem in storing information or generating complaint id display
error message
Use case diagram

Citizen Place complaint

Title Apply for licence
Description The purpose of this use case is applying for the license
Actor Citizen
Input 1. Type of license.
2. License description.
Behavior • Store the details in the license application.
• generate license application id
Output License application id
2. Type of license.
Post condition Email license application id to the Citizen
Exceptions If there is a problem in storing information or generating license application id
display error message
Use case diagram

Citizen Applies for license

Title View police station
Description The purpose of this use case is to view the police station details.
Actor Citizen
Input 1. Login id.
2. Select police station.
Behavior • Validate citizen id
• Shows details of the station.
Output NA
2. Selection of police station..
Post condition NA
Exceptions If there is a problem to display information of selected police station display error
message.
Use case diagram

Citizen View police station

Title View complaint status.
Description The purpose of this use case is to view the complaint status.
Actor Citizen
Input Login id, Complaint application id.

Behavior • Read the complaint id.
• View the status of the complaint.
Output NA
2. Complaint id.
Post condition NA
Exceptions If there is a problem in finding the record of complaint id display error message
Use case diagram

Citizen View complaint status

Title View license status.
Description The purpose of this use case is to view the license status.
Actor Citizen
Input Login id, license application id.

Behavior • Read the license application id.
• View the status of the license application.
Output Rejected / accepted
2. License application id.
Post condition NA
Exceptions If there is a problem in finding the record of license application id display error
message
Use case diagram

Citizen View license status

Title
Requirement ID Process complaint request.
ECPS-UR-08
Description
Title The purpose of request. case is to process the complaint request.
Process license this use
Actor
Description Police.
The purpose of this use case is to process the license request.
Input
Actor NA
Police.
Behavior
Input • To verify the complaint.
NA
• Move status to next state.
Output
Behavior NA Validate the licence details.
•
• Move status to next state. in.
Pre condition 1. Police should be logged
Output NA
Post condition Email status of the complaint to Citizen.
Pre condition 1 . police should be logged in.
Exceptions If there is a problem in changing the status of complaint, display error message
Post condition Email status of the complaint to applicant(citizen) .
Use case diagram
Exceptions If there is a problem in changing the status of the licence, display error message
Use case diagram

Police Process the complaint

Police Process the license

Title Maintain criminal information
Description The purpose of this use case is to store the information about crime
Actor Police.
Input criminal id, name, age, address, case type.

Behavior • Read the details of criminal.
• Validate the details.
• Store the crime information by age .
Output NA
Pre condition 1. Police should be logged in.
2. Criminal id.
Post condition Criminal details Should be stored in records.
Exceptions If there is a problem in storing the record of criminal id display error message
Use case diagram

Police Maintain crime information

Title Manage reports
Description The purpose of this use case is to manage the reports.
Actor Police.
Input Criminal id.

Behavior • Read the criminal id.
• Verify the records.
• Clear the records.
Output NA
Pre condition 1. Police should be logged in.
2. Criminal Id.
Post condition There is no record on the current criminal id.
Exceptions If there is a problem in managing details of criminal, display error message
Use case diagram

Police Manage the reports

2.3Software Requirements Specification

Look up table
S. No System Feature ID Title Requirement ID

Citizen
1 ECPS-SF-01 Registration
2 ECPS-SF-02 Log in

3 ECPS-SF-03 Place complaint

4 ECPS-SF-04 Apply for license
5 ECPS-SF-05 View police station
6 ECPS-SF-06 View complaint status
7 ECPS-SF-07 View License status

8 ECPS-SF-08 Change password
9 ECPS-SF-09 Forgot password

10 ECPS-SF-10 Log out
Police

11 ECPS-SF-11 Police Log in

12 ECPS-SF-12 View complaints

13 ECPS-SF-13 View licenses

14 ECPS-SF-14 Process complaint

15 ECPS-SF-15 Process license

16 ECPS-SF-16 Add record

17 ECPS-SF-17 Delete record

18 ECPS-SF-18 View record

19 ECPS-SF-19 Change Password

20 ECPS-SF-20 Forgot Password

21 ECPS-SF-21 Log out

System ECPS-SF-01
feature ID
Title Registration
Actor Citizen
Description This System Feature allows a citizen to register
Input Name, gender, age, Nationality, occupation, Address, pin code, net salary, Contact no, Email id, signature,
id proof with address.
Business • Click on the hyperlink registration.
Logic • System displays the registration form window.
• Enter all input details.
• Submit the form
• Perform validation.
• If data is valid, call the program on server.
• If not valid display an alert message.
• Read the details from the form.
• Connect to the data base.
• Store the details on the database.
• Generate new log in id.
• Close connection to the database.
• Call the program on server to send email of the login id to user.
• Stop the execution on the server.
• Close the system resources.
Conditions • Citizen name should be alphabet with spaces.
to be • Gender must be male or female.
checked on • Nationality must be alphabets only.
data • Pin code must be at least 6 digits.
Output • Display log in
Sequence
diagram
user User interface controller database

Click on Registration

display screen to the user

enter all input details

submit the form

perform data validation

call the program on server

read details
connect to database

Store the details in database

Generate login id

close the connection

Email login id to user

System feature ID ECPS-SF-02

Title Log in
Actor Citizen
Description This System Feature allows a citizen to login user account.
Input Log in id, password.
Business Logic • Log in page displayed on the screen.
• enter log in id, password .
• click on log in button.
• Perform validation on client side.
• If not valid display appropriate error message on login page
• Read inputs again from user.
• Again Validate the inputs till valid data.
• Connect to database.
• Validate the input data at server side.
• If data is valid, call server program to display user home
screen.
• If not display appropriate error message on login screen.
• Read the input data again till valid
Conditions to be • Log in id should be enter in the log in id text field.
checked on data • Password should be enter in the password field.
Output • Display user home screen

Sequence
diagram




submit the form



read details
connect to database


Generate login id



System ECPS-SF-03
feature ID
Title Place complaint

Actor Citizen

Description This System Feature allows a citizen to give complaint

Input Complaint on,description,

Business • Click on the hyperlink place complaint.
Logic • System displays the complaint form window.
• Submit the form
• Connect to database
• Read the data from the form.
• Store them in database.
• Return to user log in Screen.
• Generate new compliant id.
• Call the program on server to send email of the complaint id to user.
Conditions • Citizen should be logged in.
to be
checked on
data
Output • Display complaint form

Sequence
diagram




submit the form



read details
connect to database


Generate login id



System ECPS-SF-04
feature ID
Title Apply for license
Actor Citizen
Description This System Feature allows a citizen to apply for license.
Input License for, description
Business • Click on the hyperlink apply for license.
Logic • System displays the license form window.
• Submit the form
• Call server the program
• Store the details on the database.
• Generate new license id.
• Call the program on server to send email of the license id to user.
Conditions • Citizen log in id should be in database.
to be .
checked on
data
Output • Display license form
Sequence
diagram




submit the form



read details
connect to database


Generate login id



System ECPS-SF-05
feature ID
Title View police station
Actor Citizen
Description This System Feature allows a citizen to view police station details
Input NA
Business • Click on the hyperlink view police station.
Logic • System displays the window contains police station details.
• Click on the hyperlink back.
• System displays current user home window.
to be
checked on
data

System ECPS-SF-06
feature ID
Title View complaint status
Actor Citizen
Description This System Feature allows a citizen to view the status of the complaint
Input Compliant id.
Business • Click on the hyperlink view complaint status.
Logic • System displays the view complaint status form window.
• Enter the complaint id.
• Submit the form
• read the complaint id from the form.
• Search the status of the complaint.
• Display the status of the complaint in new window.
to be • Complaint id should be in database.
checked on .
data
Output • Display complaint status

System ECPS-SF-07
feature ID
Title View license status
Actor Citizen
Description This System Feature allows a citizen to view license status
Input License id
Business • Click on the hyperlink view license status.
Logic • System displays the license status form window.
• Enter the license id.
• Submit the form
• Search the status in database.
• Display the status of the license in new window.
• Call the program on server to send email of the license status to user.
to be • License id should be in database.
checked on
data
Output • Display status of the license.

System ECPS-SF-08
feature
ID
Title Change password
Actor Citizen
Descripti This System Feature allows a citizen to change the password.
on
Input password.
Business • Click on the hyperlink change password.
Logic • System displays the change password form window.
• Enter the password, new password.
• Submit the form
• If password is valid, call the program on server.
• Read the password, new password from form
• Update the password as new password.
Conditio • Citizen log in id should be in database.
ns to be • Password should be in database
checked .
on data
Output • Display password changed

Sequence
diagram user user interface controller database

Click on Opening Account



submit the form



read details
connect to database


Generate Account number


Send Email and SMS to the customer with account number

System ECPS-SF-09
feature ID
Title Forgot password
Actor Citizen
Description This System Feature allows a citizen to recover the password.
Input Log in id, recovery question answer.
Business • Click on the hyperlink forgot password.
Logic • System displays the forgot password form window.
• Enter the input log in id.
• Submit the form
• If log in id is valid, call the program on server.
• Search the log in id in the database.
• System Displays secrete question in new window.
• Enter the answer
• Submit the form
• Perform validation
• If answer is valid, call the program on server.
• Search for the password in database.
• Display the password with log in id in new window.
to be • Answer for the question.
checked on
data
Output • Display password with log in id

System ECPS-SF-10
feature ID
Title Log out
Actor Citizen
Descriptio This System Feature allows a citizen to logout.
n
Input
Business • Click on the hyperlink log out.
Logic • System displays the log in form window.
to be
checked on
data
Output • Display log in window
Sequence




submit the form



read details
connect to database





System feature ID ECPS-SF-11

Title Police Log in
Actor Police
Description This System Feature allows a police to log in.
Input Log in id, password.
Business Logic • Log in page displayed on the screen.
• enter log in id, password .
• click on log in button.
• Perform validation on client side.
• If not valid display appropriate error message on log in page
• Read inputs again from user.
• Again Validate the inputs till valid data.
• Connect to database.
• Validate the input data at server side.
• If data is valid, call server program to display user home
screen.
• If not display appropriate error message on log in screen.
• Read the input data again till valid
Conditions to be checked • Log in id should be enter in the log in id text field.
on data • Password should be enter in the password field.
output • Display log in

System ECPS-SF-12
feature ID
Title View complaints
Actor Police
Description This System Feature allows a police to view the complaints
Input NA
Business • Click on the hyperlink view complaints.
Logic • Connect to the data base.
• Display the complaints in new window.
Conditions • Police log in id should be in database.
to be
checked on
data
Output • Display view complaints window

System ECPS-SF-13
feature ID
Title View license
Actor Police
Description This System Feature allows a police to view the license
Input
Business • Click on the hyperlink view license.
• Display the license in new window.
to be
checked on
data
Output • Display view license window

System ECPS-SF-14
feature ID
Title Process the complaints
Actor Police
Description This System Feature allows a police to process the complaints
Input Status
Business • Click on the hyperlink process the complaints.
• Display process of complaints the in new window.
to be
checked on
data
Output • Display process complaints window

System ECPS-SF-15
feature ID
Title Process the license
Actor Police
Description This System Feature allows a police to process the license
Input
Business • Click on the hyperlink process the license.
• Display process of the license in new window.
• Send the license to citizens.
Conditions • Police Log in id should be in database.
to be
checked on
data
Output • Display process of the license window

System ECPS-SF-16
feature
ID
Title Add record
Actor police
Descripti This System Feature allows a police to add the record
on
Input Record details
Business • Click on the hyperlink add record.
Logic • Give an appropriate name to record.
• Verify the record details
• if record details are valid then add record.
• If record details are not valid give an error message.
Condition • Record must be exist.
s to be
checked
on data
Output • Display added record

System ECPS-SF-17
feature
ID
Title delete record
Actor police
Descripti This System Feature allows a police to delete the record
on
Input Record details
Business • Click on the hyperlink delete record.
Logic • select record to delete.
• Show a message successfully deleted.
Condition • Record must be exist.
s to be
checked
on data
Output • Displayed message “record deleted”.

System ECPS-SF-18

feature ID
Title View record
Actor police
Description This System Feature allows a police to view records
Input NA
Business • Click on the hyperlink view record.
Logic • System displays the window contains record details.
• Click on the hyperlink back.
• System displays current user home window.
Conditions • police log in id should be in database.
to be
checked on
data
Sequence
diagram




submit the form



read details
connect to database


Generate login id



System ECPS-SF-19
feature ID
Title Change password
Actor police
Descriptio This System Feature allows a police to change the password.
n
Input password.
Business • Click on the hyperlink change password.
Logic • System displays the change password form window.
• Enter the password, new password.
• Submit the form
• If password is valid, call the program on server.
• Read the password, new password from form
• Update the password as new password.
Conditions • police Log in id should be in database.
to be • Password should be in database
checked on .
data
Output Show a message password changed.

System ECPS-SF-20
feature ID

Title Forgot password
Actor police
Descriptio This System Feature allows a police to recover the password.
n
Input Log in id, recovery question answer.
Business • Click on the hyperlink forgot password.
Logic • System displays the forgot password form window.
• Enter the input log in id.
• Submit the form
• If log in id is valid, call the program on server.
• Search the log in id in the database.
• System Displays secrete question in new window.
• Enter the answer
• Submit the form
• Perform validation
• If answer is valid, call the program on server.
• Search for the password in database.
• Display the password with log in id in new window.
to be • Answer for the question.
checked on
data
Output • Display password with log in id

System ECPS-SF-21
feature ID
Title Log out
Actor police
Description This System Feature allows a police to log out.
Input
Business • Click on the hyperlink log out.
Logic • System displays the log in form window.
to be
checked on
data
Output • Display log in window
Sequence




submit the form



read details
connect to database





3.0 Introduction

Software design is a process through which the requirements are translated into a representation

of software. The software design involves three technical activities: design, code generation and

testing. The design phase is of main importance because in this activity, decisions ultimately

affect the success of software implementation and maintenance.

The design document describes a plan to implement the requirements. This phase represents

the ``how'' phase. Details on computer programming languages and environments, machines,

packages, application architecture, distributed architecture layering, memory size, platform,

algorithms, data structures, global type definitions, interfaces, and many other engineering

details are established. The design may include the usage of existing components.

UML Diagrams

UML stands for Unified Modeling Language.UML is a language for specifying, visualizing and

documenting the system. This is a step while developing any product after analysis.

The UML diagrams fall under each of these categories are:

• Static

• Use case diagram
• Class diagram
2Dynamic
• Object diagram
• State diagram
• Activity diagram
• Sequence diagram
• Collaboration diagram
3Implementation
• Component diagram
• Deployment diagram

3.1 Use case Diagram

A use case describes an interaction between a user and a system. A use case diagram displays the

relationship among actors and use cases. The two main components of use case diagram are use

cases and actors.

An actor represents a user or another system that will interact with the system we are

modeling. A use case is an external view of the system that represents some action the user might

perform in order to complete a task.

The use case diagram for the project is as follow

Registration

Place complaint

Apply for Licence
Citizen

Track status

Registration

Process complaint

Police Officer

Process Permission

3.2Sequence Diagram

A sequence diagram Unified Modelling Language(UML) is a kind of Interaction diagram that
shows how processes operate with one another and in what order. It is a construct of a chart
Sequence diagrams are sometimes called event diagrams, event scenarios, and timing diagrams

Citizen User interface Controller Database

1 : Registration form()
2 : submit()

3 : verify()

4 : invalid()

5 : check existance()

6 : not available()

7 : available()

8 : search()

9 : Police()
10 : Is Police()
11 : login()

Chapter 4

Implementation Technology

4.0 Introduction
System implementation is used to bring a developed system or sub system into operational use

and turning it over to the user. It involves programmer users and operational management.

Implementation is the process of having systems personnel checkout and put new equipment into

use, train users, installs the new application and constructs any files of data needed to use it.

Modules

There is only one module in this system:

User module

The module is explained clearly along with their contents.

4.1 User Module

The user needs to give the keystrokes to search for the file types and should have
minimum knowledge to operate the software created as part of this project.

Registration
Place complaint
Apply for license
View police station
View complaint status
View license status

4.1 Police Module

The user here is police who access the requests of the citizen and processing takes
place
Process complaint request
Process license request

Chapter5
Testing and Screens

5.0 Introduction

5.1Testing

Software testing is a critical element of software quality assurance and represents ultimate

reviews of specification, design and coding. The testing phase involves the testing of the

developed system using various test data. While testing the system, errors are found and

corrected using the testing steps and corrections are also noted for future use.

Testing is a process of detecting errors. Testing performs a very critical role for quality assurance

and for ensuring reliability of software. The results of testing are used later on during

maintenance also.

5.3Conclusion

• “ELECTRONIC COMPUTERIZED OPERATIONS
for POLICE SERVICE” provides various services to
citizens in order to protect and guide them.
• The main motto of this is to provide services to people
in a user friendly manner i.e. citizens can place their
complaints by registering with there id, to their
respective zonal office. Then the respective officer views
the details, make a report and process the request.
Later the officer acknowledges us with an e-mail or a
phone call.

Final doc

Recommended

Recommended

More Related Content

Similar to Final doc

Similar to Final doc (20)

Final doc