85
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.

Final doc

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: 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.

Page 2: Final doc

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

Page 3: Final doc

Chapter 5 Testing and Screens

5.0Introduction 5.1Test results 5.2Screens 5.3conclusion

Page 4: Final doc

List of Figures

Sno Figure No Figure Name

1 1 Class diagram

2 2 Usecase diagram

3 3 Sequence diagrams

Page 5: Final doc

SLNO

TABLE

NO

TABLE

NAME

1 1 Citizen zone

2 2 Police station

3 3 police

4 4 Login

5 5 complaint

6 6 License permission

7 7 criminal

Page 6: Final doc

Screens

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

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

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

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

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

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

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

Page 7: Final doc

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

Page 8: Final doc

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.

Page 9: Final doc

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

Page 10: Final doc

Chapter 2

Analysis

2.0 Introduction

Page 11: Final doc

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

Page 12: Final doc

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.

Page 13: Final doc

The test cases in the project are:

S.No Requirement ID

Requirement Name Source (customer/vendor)

Stable (Y/N)

Priority Need Verifiable(y/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 status

Citizen Y high Essential y

6 ECPS-UR-06 View license status Citizen Y high Essential Y

7 ECPS-UR-07 Process complaint request

Police Y high Essential Y

8 ECPS-UR-08 Process license request

Police Y high Essential Y

Requirement lookup table :

Requirement ID ECPS-UR-01

Page 14: Final doc

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

Special instructions NA

Requirement ID ECPS-UR-02Title Place complaintDescription 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

Citizen/police Registration

Page 15: Final doc

Use case diagram

Requirement ID ECPS-UR-03

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

Pre condition 1. Citizen should be logged in.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

Requirement ID ECPS-UR-04

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.

Citizen Place complaint

Citizen Applies for license

Page 16: Final doc

Output NA

Pre condition 1. Citizen should be logged in.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

Requirement ID ECPS-UR-05

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

Pre condition 1. Citizen should be logged in.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 police station

Citizen View complaint status

Page 17: Final doc

Requirement ID ECPS-UR-06

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

Pre condition 1. Citizen should be logged in.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

Requirement ID ECPS-UR-07

Title Process complaint request.

Description The purpose of this use case is to process the complaint request.

Actor Police.

Input NA

Behavior To verify the complaint. Move status to next state.

Output NA

Pre condition 1. Police should be logged in.

Citizen View license status

Page 18: Final doc

Post condition Email status of the complaint to Citizen.

Exceptions If there is a problem in changing the status of complaint, display error message

Use case diagram

Requirement ID ECPS-UR-08

Title Process license request.

Description The purpose of this use case is to process the license request.

Actor Police.

Input NA

Behavior Validate the licence details. Move status to next state.

Output NA

Pre condition 1 . police should be logged in.

Post condition Email status of the complaint to applicant(citizen) .

Exceptions If there is a problem in changing the status of the licence, display error message

Use case diagram

Requirement ID ECPS-UR-09

Police Process the complaint

Police Process the license

Page 19: Final doc

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

Requirement ID ECPS-UR-10

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.

Police Maintain crime information

Page 20: Final doc

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

2.3Software Requirements Specification

Police Manage the reports

Page 21: Final doc

Look up tableS. No System Feature ID Title Requirement ID

Citizen1 ECPS-SF-01 Registration2 ECPS-SF-02 Log in

3 ECPS-SF-03 Place complaint

4 ECPS-SF-04 Apply for license5 ECPS-SF-05 View police station6 ECPS-SF-06 View complaint status7 ECPS-SF-07 View License status

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

10 ECPS-SF-10 Log outPolice

11 ECPS-SF-11 Police Log in

12 ECPS-SF-12 View complaints

Page 22: Final doc

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 feature ID

ECPS-SF-01

Title RegistrationActor CitizenDescription 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 Logic

Click on the hyperlink registration. System displays the registration form window. Enter all input details. Submit the form

Page 23: Final doc

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 to be checked on data

Citizen name should be alphabet with spaces. Gender must be male or female. Nationality must be alphabets only. 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

Email login id to user

Store the details in database

Generate login id

close the connection

Page 24: Final doc

System feature ID ECPS-SF-02

Title Log inActor CitizenDescription 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 data is valid, call the program on server. 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 Stop the execution on the server. Close the system resources.

Conditions to be checked on data

Log in id should be enter in the log in id text field. Password should be enter in the password field.

Output Display user home screen

Page 25: Final doc

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

Email login id to user

Store the details in database

Generate login id

close the connection

Page 26: Final doc

System feature ID

ECPS-SF-03

Title Place complaint

Actor Citizen

Description This System Feature allows a citizen to give complaint

Input Complaint on,description,

Business Logic

Click on the hyperlink place complaint. System displays the complaint form window. Enter all input details. 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. Close connection to the database. Call the program on server to send email of the complaint id to user. Stop the execution on the server. Close the system resources.

Conditions to be checked on data

Citizen should be logged in.

Output Display complaint form

Page 27: Final doc

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

Email login id to user

Store the details in database

Generate login id

close the connection

Page 28: Final doc

System feature ID

ECPS-SF-04

Title Apply for licenseActor CitizenDescription This System Feature allows a citizen to apply for license. Input License for, descriptionBusiness Logic

Click on the hyperlink apply for license. System displays the license form window. Enter all input details. Submit the form Call server the program Read the details from the form. Connect to the data base. Store the details on the database. Generate new license id. Close connection to the database. Call the program on server to send email of the license id to user. Stop the execution on the server. Close the system resources.

Conditions to be checked on data

Citizen log in id should be in database..

Output Display license form

Page 29: Final doc

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

Email login id to user

Store the details in database

Generate login id

close the connection

Page 30: Final doc

System feature ID

ECPS-SF-05

Title View police stationActor CitizenDescription This System Feature allows a citizen to view police station details Input NABusiness Logic

Click on the hyperlink view police station. System displays the window contains police station details. Click on the hyperlink back. System displays current user home window. Stop the execution on the server. Close the system resources.

Conditions to be checked on data

Citizen log in id should be in database.

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

Email login id to user

Store the details in database

Generate login id

close the connection

Page 31: Final doc

System feature ID

ECPS-SF-06

Title View complaint statusActor CitizenDescription This System Feature allows a citizen to view the status of the complaint Input Compliant id.Business Logic

Click on the hyperlink view complaint status. System displays the view complaint status form window. Enter the complaint id. Submit the form Perform validation. If data is valid, call the program on server. If not valid display an alert message. read the complaint id from the form. Connect to the data base. Search the status of the complaint. Display the status of the complaint in new window. Close connection to the database. Stop the execution on the server. Close the system resources.

Conditions to be checked on data

Citizen log in id should be in database. Complaint id should be in database..

Output Display complaint status

Page 32: Final doc

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

Email login id to user

Store the details in database

Generate login id

close the connection

Page 33: Final doc

System feature ID

ECPS-SF-07

Title View license statusActor CitizenDescription This System Feature allows a citizen to view license status Input License idBusiness Logic

Click on the hyperlink view license status. System displays the license status form window. Enter the license id. 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. Search the status in database. Close connection to the database. Display the status of the license in new window. Call the program on server to send email of the license status to user. Stop the execution on the server. Close the system resources.

Conditions to be checked on data

Citizen log in id should be in database. License id should be in database.

Output Display status of the license.

Page 34: Final doc

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

Email login id to user

Store the details in database

Generate login id

close the connection

Page 35: Final doc

System feature ID

ECPS-SF-08

Title Change passwordActor CitizenDescription

This System Feature allows a citizen to change the password.

Input password.Business Logic

Click on the hyperlink change password. System displays the change password form window. Enter the password, new password. Submit the form Perform validation. If password is valid, call the program on server. If not valid display an alert message. Read the password, new password from form Connect to the data base. Update the password as new password. Close connection to the database. Stop the execution on the server. Close the system resources.

Conditions to be checked on data

Citizen log in id should be in database. Password should be in database.

Output Display password changed

Page 36: Final doc

Sequence diagram

user user interface controller database

Click on Opening Account

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

Send Email and SMS to the customer with account number

Store the details in database

Generate Account number

close the connection

Page 37: Final doc

System feature ID

ECPS-SF-09

Title Forgot passwordActor CitizenDescription This System Feature allows a citizen to recover the password.Input Log in id, recovery question answer.Business Logic

Click on the hyperlink forgot password. System displays the forgot password form window. Enter the input log in id. Submit the form Perform validation. If log in id 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. 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. If not valid display an alert message. Read the details from the form. Search for the password in database. Display the password with log in id in new window. Close connection to the database. Stop the execution on the server. Close the system resources.

Conditions to be checked on data

Citizen log in id should be in database. Answer for the question.

Output Display password with log in id

Page 38: Final doc

Sequence diagram

user user interface controller database

Click on Opening Account

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

Send Email and SMS to the customer with account number

Store the details in database

Generate Account number

close the connection

Page 39: Final doc

System feature ID

ECPS-SF-10

Title Log outActor CitizenDescription

This System Feature allows a citizen to logout.

InputBusiness Logic

Click on the hyperlink log out. System displays the log in form window. Stop the execution on the server. Close the system resources.

Conditions to be checked on data

Citizen log in id should be in database.

Output Display log in windowSequence diagram

user user interface controller database

Click on Opening Account

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

Send Email and SMS to the customer with account number

Store the details in database

Generate Account number

close the connection

Page 40: Final doc

System feature ID ECPS-SF-11

Title Police Log inActor PoliceDescription 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 data is valid, call the program on server. 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 Stop the execution on the server. Close the system resources.

Conditions to be checked on data

Log in id should be enter in the log in id text field. Password should be enter in the password field.

output Display log in

Page 41: Final doc

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

Email login id to user

Store the details in database

Generate login id

close the connection

Page 42: Final doc

System feature ID

ECPS-SF-12

Title View complaintsActor PoliceDescription This System Feature allows a police to view the complaints Input NABusiness Logic

Click on the hyperlink view complaints. Connect to the data base. Display the complaints in new window. Close connection to the database. Stop the execution on the server. Close the system resources.

Conditions to be checked on data

Police log in id should be in database.

Output Display view complaints window 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

Email login id to user

Store the details in database

Generate login id

close the connection

Page 43: Final doc

System feature ID

ECPS-SF-13

Title View licenseActor PoliceDescription This System Feature allows a police to view the licenseInputBusiness Logic

Click on the hyperlink view license. Connect to the data base. Display the license in new window. Close connection to the database. Stop the execution on the server. Close the system resources.

Conditions to be checked on data

Police log in id should be in database.

Output Display view license window

Page 44: Final doc

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

Email login id to user

Store the details in database

Generate login id

close the connection

Page 45: Final doc

System feature ID

ECPS-SF-14

Title Process the complaintsActor PoliceDescription This System Feature allows a police to process the complaints Input Status Business Logic

Click on the hyperlink process the complaints. Connect to the data base. Display process of complaints the in new window. Close connection to the database. Stop the execution on the server. Close the system resources.

Conditions to be checked on data

Police log in id should be in database.

Output Display process complaints window 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

Email login id to user

Store the details in database

Generate login id

close the connection

Page 46: Final doc

System feature ID

ECPS-SF-15

Title Process the licenseActor PoliceDescription This System Feature allows a police to process the license InputBusiness Logic

Click on the hyperlink process the license. Connect to the data base. Display process of the license in new window. Close connection to the database. Stop the execution on the server. Close the system resources. Send the license to citizens.

Conditions to be checked on data

Police Log in id should be in database.

Output Display process of the license window

Page 47: Final doc

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

Email login id to user

Store the details in database

Generate login id

close the connection

Page 48: Final doc

System feature ID

ECPS-SF-16

Title Add recordActor policeDescription

This System Feature allows a police to add the record

Input Record detailsBusiness Logic

Click on the hyperlink add record. 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.

Conditions to be checked on data

Record must be exist.

Output Display added record

Page 49: Final doc

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

Email login id to user

Store the details in database

Generate login id

close the connection

Page 50: Final doc

System feature ID

ECPS-SF-17

Title delete recordActor policeDescription

This System Feature allows a police to delete the record

Input Record detailsBusiness Logic

Click on the hyperlink delete record. select record to delete. Show a message successfully deleted.

Conditions to be checked on data

Record must be exist.

Output Displayed message “record deleted”.

System ECPS-SF-18

Page 51: Final doc

feature IDTitle View recordActor policeDescription This System Feature allows a police to view records Input NABusiness Logic

Click on the hyperlink view record. System displays the window contains record details. Click on the hyperlink back. System displays current user home window. Stop the execution on the server. Close the system resources.

Conditions to be checked on data

police log in id should be in database.

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

Email login id to user

Store the details in database

Generate login id

close the connection

Page 52: Final doc

System feature ID

ECPS-SF-19

Title Change passwordActor policeDescription

This System Feature allows a police to change the password.

Input password.Business Logic

Click on the hyperlink change password. System displays the change password form window. Enter the password, new password. Submit the form Perform validation. If password is valid, call the program on server. If not valid display an alert message. Read the password, new password from form Connect to the data base. Update the password as new password. Close connection to the database. Stop the execution on the server. Close the system resources.

Conditions to be checked on data

police Log in id should be in database. Password should be in database.

Output Show a message password changed.

Page 53: Final doc

Sequence diagram

user user interface controller database

Click on Opening Account

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

Send Email and SMS to the customer with account number

Store the details in database

Generate Account number

close the connection

Page 54: Final doc

System feature ID

ECPS-SF-20

Title Forgot passwordActor policeDescription

This System Feature allows a police to recover the password.

Input Log in id, recovery question answer.Business Logic

Click on the hyperlink forgot password. System displays the forgot password form window. Enter the input log in id. Submit the form Perform validation. If log in id 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. 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. If not valid display an alert message. Read the details from the form. Search for the password in database. Display the password with log in id in new window. Close connection to the database. Stop the execution on the server. Close the system resources.

Conditions to be checked on data

police log in id should be in database. Answer for the question.

Output Display password with log in id

Page 55: Final doc

Sequence diagram

user user interface controller database

Click on Opening Account

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

Send Email and SMS to the customer with account number

Store the details in database

Generate Account number

close the connection

Page 56: Final doc

System feature ID

ECPS-SF-21

Title Log outActor policeDescription This System Feature allows a police to log out.InputBusiness Logic

Click on the hyperlink log out. System displays the log in form window. Stop the execution on the server. Close the system resources.

Conditions to be checked on data

police log in id should be in database.

Output Display log in windowSequence diagram

user user interface controller database

Click on Opening Account

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

Send Email and SMS to the customer with account number

Store the details in database

Generate Account number

close the connection

Page 57: Final doc

Chapter3

Design

Page 58: Final doc

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

Page 59: Final doc

Use case diagram

Class diagram

Dynamic

Object diagram

State diagram

Activity diagram

Sequence diagram

Collaboration diagram

Implementation

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

Page 60: Final doc

Citizen

Registration

Place complaint

Apply for Licence

Track status

Police Officer

Registration

Process complaint

Process Permission

Page 61: Final doc

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()

Page 62: Final doc

Chapter 4

Implementation Technology

Page 63: Final doc

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.

Page 64: Final doc

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.

RegistrationPlace complaintApply for licenseView police stationView 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 requestProcess license request

Page 65: Final doc

Chapter5

Testing and Screens

5.0 Introduction

Page 66: Final doc

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.

Page 67: Final doc

5.2 Screens

Page 68: Final doc
Page 69: Final doc
Page 70: Final doc
Page 71: Final doc

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.