1. E-POLICE STATION
by
Riddhi Mittal
Submitted to the
NATIONAL INSTITUTE OF
ELECTRONICS AND
INFORMATION TECHNOLOGY
AUGUST , 2013
1
2. DECLARATION
We hereby declare that this submission is our own work and that, to the best of our knowledge and belief, it
contains no material previously published or written by another person nor material which to a substantial
extent has been accepted for the award of any other degree or diploma of the university or other institute of
higher learning, except where due acknowledgment has been made in the text.
2
Signature:
Name :RIDDHI MITTAL
Roll No.: 1009113075
Date :5 AUGUST, 2013.
3. ACKNOWLEDGEMENT
The satisfaction that accompanies that the successful completion of any task would be incomplete without the
mention of people whose ceaseless cooperation made it possible, whose constant guidance and encouragement
crown all efforts with success.
We are grateful to our project guide professor ASHISH SINGH ATWAL for the guidance, inspiration and
constructive suggestions that helpful us in the preparation of this project.
We also thank our colleagues who have helped in successful completion of the project.
3
4. CERTIFICATE OF ORIGINALITY
This is to certify that the project report entitled “E-POLICE STATION” prepared Riddhi Mittal is the
documentation of authentic work carried out by them under my guidance.
The matter embedded in this project work has not been submitted earlier for award of any degree or diploma to
the best of my knowledge and belief.
4
Signature of project guide
PROFESSOR ASHISH SINGH ATWAL
6. 2.4.1 Software language used…………………………………….………………..14
2.4.2 Developmeent tools…………………………………………….……………..14
2.5 Assumptions and dependencies………………………………………….…………..14
2.6 Use case……..……………………………………………………………………....15
2.6.1 Use case model ………………………………………………………………...15
2.6.2 Use case diagram………………………………………………………….......16
2.6.3 Use case report……………………………………………………………...…17
2.6.4 Use case scenario…………………………………………………………...…18
CHAPTER 3 System Design
`
3.1 Data Flow Diagram…………………………………………………………………..28
3.1.1 1-Level DFD…………………………………………………………………..28
3.1.2 2-Level DFD………………………………………………………………….29
3.2 E-R diagram…………………………………………………………………………31
6
CHAPTER 4 Implementation and Results
4.1 Hardware Requirement…………………………………………………………….…32
4.2 Software Requirement………………………………………………….……………..32
4.3 Assumption and dependencies…………………………………………..…………….32
4.4 Snapshots …………………………………………………………………..………….33
CHAPTER 5
5.1 (CONCLUSIONS) .........................................................................
5.2REFERENCES
7. LIST OF FIGURES
2. 2.1 use case diagram………………………………………………..……………………………..16
2.2 Sequence diagram for complaints……………………………………………………………25
2.3 Sequence diagram for wanted criminals……………………………………………………...26
2.4 for making a complaint……………………………………………………………………….27
7
3. Data Flow Diagram
3.1 DFD of e police station………………………………………………………………………..28
3.2 DFD of criminal and missing items…………………………………………………………....29
3.3 DFD of citizen and employes………………………………………………………………….30
3.4 DFD of missing person and missing valuables………………………………………………...30
3.5 ER diagram of e-police station …………………………………………………………….....31
8. CHAPTER 1
INTRODUCTION
8
1.1 Problem introduction
Conventionally a citizen has to go to the police station in person to make complaints.
But oftenly people are afraid of walking up to the police station to register a complaint.
With the launch of the E-POLICE STATION, filing a complaint would be just a click away making it possible to
file an FIR from through the internet.
E-POLICE STATION is an electronic platform which is capable of maintaining the records of crime like FIR,
criminals’ details and police department administration.
It is an attempt to overhaul the police administration system. It will boost the confidence of citizens in the
machinery and can help the police officials to find first hand information. As the system is directly supervised by
DSPs, higher-level officials will look into them personally.
Also the citizen can make a report about missing persons, report missing valuables and can report about wanted
criminals. And the police department administration can be done online.
1.1.1 Motivation
The motivation behind building this e-police station was to develop a platform in order to attempt to overhaul
the police administration system. It will boost the confidence of citizens in the machinery and can help the police
officials to find first hand information. As the system is directly supervised by DSPs, higher-level officials will
look into them personally.
1.1.2 Project objective
People need not physically visit an actual Police station. They can simply register themselves to the site and can
avail its simple and user-friendly method of complaint registration.
To develop an online comprehensive crime reporting system.
To develop a user-friendly and effective crime management system that enhances the complaint
registration procedure.
To create an online web portal for exhibiting latest crime related news and wanted criminals.
9. To engage public, police and government agencies to be more quick, proactive and responsive to fight
9
with crime and criminals.
1.1.3 Scope
The project targets users from different fields can give their contribution to the site while availing its advantages
in the following ways:
GENERAL PUBLIC: common citizens can access this website for latest crime related information. They can
create their accounts and register their complaints online.
POLICE OFFICIALS: Police will investigate crime reports and other complaints and the arrested criminals details
are added in the crime directory.
DETECTIVES: General public can hire detectives .
ADMINISTRATOR: Admin authenticates all the end users and the officers, provides login account and maintains
the system server and the database.
1.2 Related Previous Work
It briefly includes previous work carried out in this field, researching the problem studied, summarization of the
results obtained etc.There are few sites related to this project which are as follows:
SINGAPORE E-POLICE FORCE(www.spf.gov.sg)
SPF provides an online platform for reporting of lost properties or crime cases which do not prepare immediate
police action.
HONKKONG POLICE FORCE (www.police.gov.hk/ppp_en/)
This is a very efficient system providing online complains registration , licensing and permits, traffic and other
useful information.
KERALA POLISE STATION (http://www.keralapolice.org/)
10. CHAPTER 2
SYSTEM REQUIREMENT SPECIFICATION
10
2.1 Product perspective
The E-POLICE STATION is an application which is providing the features of dynamic web
application as well as that of the stand alone application on the administrator side.The application will be used
across the state by the citizens, the law enforcement bodies, private detectives . It can be used to gather the
information about the crime or about criminal and missing person and to broadcast or communicate related
information (of any criminal activities and other alerts). The citizen can register their e-complaints here which will
ease out the process for the citizens and also for the police to maintain records as the status of the case can be
viewed as well as can be updated.
This project is independent and totally self –contained and is not a component of a larger system.
It is a complete system of itself
. 2.1.1 Hardware Interface
Minimum Hardware Requirements:
CLIENT SIDE
PROCESSOR RAM DISK
SPACE
Pentium III at 500
MHz
128MB 1GB
PROCESSOR RAM DISK SPACE
P Pentium IV at 1.3GHz 512 MB 1G B
Pentium IV at 1.3 GHz 512 MB 2GB
Internet Explorer 6.0 and
above,Mozilla Firefox,Chrome
SERVER SIDE
ORACLE
APACHE TOMCAT SERVER
11. 11
2.1.2 Software Interface
Front End Client: The system is a web b
ased application clients are requiring using modern web browser such as Mozilla Firefox 1.5, Internet Explorer 6
and Google Chrome.
Web Server: The web application will be hosted on Apache Tomcat Server.
Data Base Server: The database server we used is Oracle.
Back End: We use backend as Oracle.
2.1.3 Communication Interface
Client on Internet will be using HTTP/HTTPS protocol.
Client on Intranet will be using TCP/IP protocol.
2.1.4 Memory Constraints
Client Side: We will be requiring RAM of 128MB or more.
Disk space of 1GB.
Server Side: RAM OF 512 MB.
Disk space of 1 GB.
2.1.5 Operation
o Employee logs on to their accounts to view complaints and file GENERAL COMPLAINTS
which is sent by citizens.
o Creating dynamic members like Inspector, Head constables and other officials as the first
time setup.
o Supervision of lower designation officers by higher designation officers.
12. o Maintains contact details of the employees.
o All the users are authenticated to avail the service.
o FEEDBACK section is also included for Users suggestions.
12
2.1.5 Site Adaptation Requirements.
HARDWARE REQUIREMENT:
RAM of 128 MB or more
HARD DISK of 2GB
Internet connectivity using wifi or modem
Pentium iv processor
SOFTWARE REQUIREMENTS-WEBSERVER:
ApacheTomcatServer
DATABASE: mysql
IDE : eclipse
BROWSERS: Mozilla Firefox 1.5, Internet Explorer 6 and Google Chrome.
OPERATING SYSTEM: Windows 7
2.2 Product functions
Product function includes major function that the web site will perform. It includes the following modules:-
1. USER LOGIN
2. ADMINISTRATOR LOGIN
3. COMPLAINT REGISTRATION
4. VIEW COMPLAINT STATUS
13. 13
5. UPDATE STATUS
6. HIRE DETECTIVES
1. USER LOGIN: This includes a user login. There will be a username and password to login into
the system to use all the facilities.
2. ADMINISTRATOR LOGIN: This includes An admin login. There will be a username and
password to login into the system to use all the facilities
3. COMPLAINT REGISTRATION: This module helps to register the details about the crime. This
is done by entering some details, such as incident details, victim details, crime details etc.
4. VIEW COMPLAINT STATUS: This module allows us to view the status of the complaint that
you have registered earlier.
5. UPDATE STATUS: This module allows admin to view the status of the complaint that user had
registered earlier.
6. HIRE DETECTIVE: User can hire detective who can help in solving their personal problems.
2.3 User characteristics
All users can be assumed to have the following characteristics:
Ability to read and understand English.
Familiarity with the operation of the basic Graphical User Interface (GUI) components of the Windows
NT operating system.
Beyond the above, no further facility with computer technology can be assumed.
Software Designers:
These are the most obvious users. They will use the system as a means of laying out the design of an as
yet unimplemented system.
The Software Designer users can be assumed to have the following characteristics:
o A thorough knowledge of object oriented design notation.
o Familiarity with common design environments. For example, the concept of selecting a tool to
draw with.
o Software Developers User Characteristics.
14. 14
Software Developers:
These are the people that take the model generated by the designers and implement it in code. They may
also use the system to identify the design of an existing system in order to maintain it.
Quality Engineers:
These users are usually responsible for ensuring that a design is feasible and/or reliable. They will
therefore also need to be looking at the output from our system.
System Administrator:
Due to the client/server/concurrent nature of the system, some one needs to be responsible for security and
maintenance of the system. This is the System Administrators role. The Administrator of the system,
project or model need not be a member of the any of the other roles identified here.
The Client:
More often than not, software is designed for a client. The client may wish to see the design as layed out
by the system and be able to see what exactly they are buying.
2.4 Constraints
• GUI is only in English.
• Limited to HTTP/HTTPS.
• The biometric identification system is not affordable along with the existingcost of the project both the
man power and financial factors
• This e-service will not be very effective in reporting of those crime cases which require immediate police
action.
• There are not many policemen educated in cyber technology which can act as a major roadblock in the
implementation of this system.
• All the target users are not comfortable in English language. People from small towns and villages hardly
know the language.
• No internet access in small villages and remote areas.
• People from small towns and villages are not even accustomed to handling computer systems let alone
accessing websites and online registration.
• Security of sensitive crime details in the database from hackers and intruders remains the major barrier.
15. 15
Design Constraints:
2.4.1 Software Language Used
The languages that shall be used for coding Corporate Employee Welfare System are
JAVA,J2EE,JSP,Servlets and HTML. For working on the coding phase of the Corporate Employee System
the ApacheTomcat Server needs to be installed..
2.4.2 Development Tools
We will make use of available tools Netbeans and Oracle.
2.5 Assumptions And Dependencies
• The end user should have a basic knowledge of English and computer usage
• The end user should be able to scan the required documents and upload while applying for various
licenses and for creating account.
2.6 Use case
If all interaction with a system is described in terms of procedures written as use cases, then the Use Case Model
provides a complete, black-box, outside-in view of system functionality. The Use Case Model is not intended to
be an exhaustive definition of system functionality - that only comes with a full internal system model that results
from a detailed system analysis. The Use Case Model rather serves to scope the system functionality by defining
what functions will or will not be performed by the system in sufficient detail that we can be sure we haven't
missed anything important. The Use Case Model consists of:
16. Actors, Use Cases and their relationships which appear on
16
2.6.1 Use case model
A number of Use Case Diagrams which together cover all of the proposed system functionality and are
supported by
Use Case Documents, written largely in text, which describe the detail of the flow of each use case and
supported by and consistent with
Optional Prototype Screens or Human Interfaces and
Optional Activity Diagrams
17. 17
2.6.2 Use case diagram
Figure 2.1 use case diagram
18. 18
2.6.2 Use Case Reports
End User
a) Sign Up
End user must give their details (such as name, age, contact no…etc) and fill their sign up
form physically and these forms are checked, approved and stored by the admin.
b) Sign in
After getting the user name and password, end user can log onto their account and access the website.
c) View Profile
End user can view their profile which contains own details that citizen were given already in the signup form
approved by admin.
d) Make a complaint
End user who signed in this e-cops website have given full rights to complaints a crime oran event or incident.
e) Report about criminals
End user who have signed in this website have a rights to report about criminals andcriminals information were
stored by the admin. The user information is useful to find out the criminals easily insuch case the government
provides a reward to that user.
ADMINISTRATOR
a) Verify details and login account
Admin checks the end users username and password and allow to login in the e-cops website.
b) Maintaining e-cops details
Maintaining criminal detail, case details, centralized data base and additional information areupdated accordingly.
c) Adding department details
Adding law and acts section enrolled by admin using Indian Penal Code.Adding FAQ and POLLS for user
benefits
19. 19
2.6.4 Use case scenario
Signup
Inordertoapplyforvariouscertificatessuchasbirth,community,incomeandrationcard,andend usermustsign
up byfillingthesign up formand getitapproved by admin.
Signin
Aftergettingtheusernameand password,end userscanlogontotheiraccount and can access the website.
Open profile
Endusercanopentheirprofilewhichcontainsthepersonaldetailswhichhe/sheprovidedduring signup.
View profile
End user canviewtheirprofile whichcontainsthe personaldetailswhich he/sheprovided during signup
Updateprofile
Endusercanupdatetheirprofilewhichcontainsthepersonaldetailswhichhe/sheprovidedduring
signupifanyupdaterequired.
20. 20
Enter details
Enduserwhosignedincanopentherequisitionformandentersthemandatorydetailsrequiredi
n thatform.
Submitform
Afterfillingthemandatory and otherdetails,Endusersubmitstheform.
.
Make a Complaint
End user whosigned in cancomplainta crimeasancomplainant orinformant.
Report MissingValuablesand Persons
Enduserwhosignedincanreportaboutthemissingvaluablesandcancollecttherewardsfromthe
complainant if applicable.
Citizen Use Cases ---Citizen Signup :-
Use Case Name: Citizen Signup ID:CSU
Primary Actors:Citizen, End Users
Brief Description:
This use case describes creation of citizens’ profile in the E-copdatabase system.
Goal:
Successful creation of users account
Success Measurement:
Message will be shown displaying `your request has been accepted`.
Preconditions:
User should meet the terms and conditions
User id should be unique
All the mandatory fields should be filled up
Trigger:
21. When citizen wants to create an account
21
Typical flow of Events:
User first logs on to the E-cops website through the Internet
In the servicepage he will click on `Register for an account` link
User should fill all the necessary fields appropriately
After that User must click on submit button to submit his registration
form
The form will go to assigned police officers for verification and
approval
Assumptions:
It is assumed that user will enter all meaning full data
It is assumed that workflows will be carried out internally
Citizen Use Cases ---Citizen Login:-
Use Case Name: Citizen Login ID:CLI
Primary Actors:Citizen, End Users
Brief Description:
This use case describes successful log in by the user
Goal:
Successful log in by the user
Create session for logged in user
Success Measurement:
Message will be shown displaying `Welcome username` and the user
will be redirected to services page.
Preconditions:
User id and password, both should match
That user must be approved by station house officer
User must submit registration form before log in
Triggers:
When citizen wants to log in
Typical flow of Events:
User first logs on to the E-cops website through the Internet
In the servicepage he has to fill the E-mail ID/User ID and password
fields
If log in is successful user will redirected to `services` page
Otherwise message will be shown for unsuccessful log in
Assumptions:
Citizen Use Cases --- Make an Emergency Complaint:-
22. Use Case Name: Make an Emergency
Complaint
22
ID:MEC
Primary Actors:Citizen, End Users
Brief Description:
This use case describes creation of unapproved emergency complaint by user.
Goal:
Successful creation of unapproved emergency complaint
Success Measurement:
Message will be shown displaying `yours complaint has been filed `
and your complaint no.
Preconditions:
User may or may not be logged in
Mandatory fields are filled
Trigger:
When citizen wants to make an emergency complaint
Typical flow of Events:
User first logs on to the E-cops website through the Internet
Click on the Emergency Complaint link in the home page
User should fill all the necessary fields appropriately
After that User must click on submit button to submit his complaint
The form will go to assigned police officers for verification and
approval
Assumptions:
It is assumed that user will enter all meaning full data
It is assumed that workflows will be carried out internally
Citizen Use Cases --- Report Missing Person:-
Use Case Name: Report Missing Person ID:RMP
Primary Actors:Citizen, End Users
Brief Description:
This use case describes how an user can report about missing person
Goal:
Successful creation of unapproved missing person complaint
Success Measurement:
Message will be shown displaying `yours complaint has been filed `
and your complaint no.
Preconditions:
User must be logged in
Mandatory fields are filled
Trigger:
When citizen wants to report a missing person
23. 23
Typical flow of Events:
User first logs on to the E-cops website through the Internet
User logs in with user id and password
Select Missing Person link
Fill the necessary fields
Submit the form
The form will go to assigned police officers for verification and
approval
Assumptions:
It is assumed that user will enter all meaning full data
It is assumed that workflows will be carried out internally
Citizen Use Cases --- Approve Complaints:-
Use Case Name: Approve Complaints ID:ACOM
Primary Actors:Employees, Station House Officer, Police Officer, DGP
Brief Description:
This use case describes how employees can approve complaints.
Goal:
Successful creation of approved complaints
Success Measurement:
Message will be shown displaying `complaint is approved ` and
complaint no.
Preconditions:
Complaints filed by users already exits
Trigger:
When Employee wants to approve complaints
Typical flow of Events:
Employee first logs on to the E-cops website through the Internet
Employee logs in with user id and password
Select Complaints link
Click on approve link to approve complaint
Assumptions:
It is assumed that workflows will be carried out internally
Citizen Use Cases --- Adding Criminal Details:-
Use Case Name: Adding Criminal Details ID:ACD
Primary Actors:Employees, Station House Officer, Police Officer, DGP
Brief Description:
This use case describes how employees can add criminal records.
Goal:
24. Successful addition of criminal records
24
Success Measurement:
Message will be shown displaying `criminal record added successfully`
Preconditions:
Employee must be logged in
Employee must have necessary permission
Trigger:
When Employee wants to add criminal details
Typical flow of Events:
Employee first logs on to the E-cops website through the Internet
Employee logs in with user id and password
Select Criminals link
Fill mandatory fields
Click Submit Button
Assumptions:
It is assumed that workflows will be carried out internally
Citizen Use Cases --- Adding Police Officers:-
Use Case Name: Adding Police Officers ID:APO
Primary Actors:Administrator
Brief Description:
This use case describes how admin can add police officers.
Goal:
Successful addition of police officers
Success Measurement:
Message will be shown displaying `police officer added successfully`
Preconditions:
Admin must be logged in
Trigger:
When Admin wants to add police officers
Typical flow of Events:
Admin first logs on to the E-cops website through the Internet
Admin logs in with user id and password
Select Police Officers link
Fill mandatory fields
Click Submit Button
Assumptions:
It is assumed that workflows will be carried out internally
Citizen Use Cases --- Adding Police Stations:-
Use Case Name: Adding Police Stations ID:APO
25. Primary Actors:Administrator
Brief Description:
This use case describes how admin can add police stations.
Goal:
Successful addition of police stations
25
Success Measurement:
Message will be shown displaying `police station added successfully`
Preconditions:
Admin must be logged in
Trigger:
When Admin wants to add police stations
Typical flow of Events:
Admin first logs on to the E-cops website through the Internet
Admin logs in with user id and password
Select Police Station link
Fill mandatory fields
Click Submit Button
Assumptions:
It is assumed that workflows will be carried out internally
26. 26
2.6.5 Sequence diagram
Case 1:NORMAL FLOWFOR COMPLAINT,FIRFILLINGANDINVESTIGATION PROCESS
Figure 2.2 for complaints
33. CHAPTER 4
IMPLEMENTATION AND RESULTS
33
4.1 Hardware Requirement
PROCESSOR Pentium IV
RAM 128 MB
HARD DISK 20 GB
MONITOR 14” SVGA
KEYBOARD Normal
4.2 Software Requirement
OPERATING SYSTEM Windows 7, Windows XP
LANGUAGE Java, java script, HTML,XML
DATABASE My SQL
4.3 Assumption and Dependencies
• The end user should have a basic knowledge of English and computer usage
• The end user should be able to scan the required documents and upload while
applying for various licenses and for creating account.
34. CHAPTER 5
CONCLUSION
5.1 Comparison With Existing State of Art Technology
The existing system does not involve any government employees to monitor its
34
activities.
They do not have any chat facility among the working officers.
The existing system do not include the involvement of NGOs for solving various social
problems.
Regarding basics rights like food, clothing and educations.
Visually not intuitive
It don’t provide any compatibility issues with new web browsers
In earlier system user feedback status tracking not facilitated
We are providing user registration facility
5.2 Future Extensions
Our project can be further very well extended in future. We may further include other
functionalities which it lacks now, some of them are like adding functionality of chatting,
uploading videos by police officrs , adding groups to share common space between employees
having same common interest, sms facility etc.
REFERENCES
1. Software Engineering by R.S. Pressman
2. Database System Concepts by Silberschatz, Korth and Sudarshan
3. The Unified Modelling Language (UML) by Grady Booch, Dr. James Rumbaugh, Dr.
Jacobson
4. www.spf.gov.sg.com
5. www.police.gv.hk/ppp_en.com
6. http://www.keralapolice.org/