PROJECT REPORT
ON
CRIME REPORTING SYSTEM
BY
HAROON ALAM
CLASS NO. 204
BS (CS)
SESSION 2012-2015
A project report submitted to the IBMS, The University of Agriculture, Peshawar in partial fulfillment
of the requirements for the degree of
BACHELOR OF SCIENCE IN COMPUTER SCIENCE
SUPERVISED BY
Mr. FAWAD ALI
INSTITUTE OF BUSINESS AND MANAGEMENT SCIENCE
THE UNIVERSITY OF AGRICULTURE
PESHAWAR, PAKISTAN
FEBRUARY, 2016
PROJECT REPORT
ON
CRIME REPORTING SYSTEM
BY
HAROON ALAM
CLASS NO. 204
BS (CS)
SESSION 2012-2015
A project report submitted to the IBMS, The University of Agriculture, Peshawar in partial fulfillment
of the requirements for the degree of
BACHELOR OF SCIENCE IN COMPUTER SCIENCE
Approved By:
_______________________________
Mr. Fawad Ali
(Advisor)
_______________________________
Mr. Imran Ud Din
(Member)
_______________________________
Mr. Sadiq Shah
(Member)
_______________________________
Mr. Muhammad Shahid
(Incharge CS/IT)
_______________________________
Dr. Muhammad Fayaz
(Additional Director IBMS)
INSTITUTE OF BUSINESS AND MANAGEMENT SCIENCE
THE UNIVERSITY OF AGRICULTURE
PESHAWAR, PAKISTAN
FEBRUARY, 2016
TABLE OF CONTENTS
CHAPTER 1 .........................................................................................................................................1
CHAPTER # 1 Introduction ...................................................................................................................2
1.1 Introduction..............................................................................................................................2
1.2 Overview of the Present System.................................................................................................2
1.3 Drawbacks in the Present System ...............................................................................................3
1.3.1 Time Consuming .................................................................................................................3
1.3.2 Redundancy of Data (Duplication of Data) ............................................................................3
1.3.3 Changing/Removing Of Records ...........................................................................................3
1.3.4 Storage Media ....................................................................................................................3
1.3.5 Information Updating..........................................................................................................3
1.3.6 Backup and Recovery ..........................................................................................................4
1.3.7 Integrity .............................................................................................................................4
1.3.8 Burden of Work ..................................................................................................................4
1.4 Background...............................................................................................................................4
1.5 Proposed System and Objectives of the System ..........................................................................6
1.6 Advantages of Proposed System.................................................................................................6
1.6.1
Accessibility..................................................................................................................6
1.6.2 Accuracy and Consistency....................................................................................................7
1.6.3 Input Improvements............................................................................................................7
1.6.4 Faster Information Retrieval ................................................................................................7
1.6.5 Reduction of Workload........................................................................................................7
1.6.6 Flexibility............................................................................................................................7
1.6.7 Reduced Redundancy ..........................................................................................................7
1.6.8 Reduction in Cost................................................................................................................8
1.6.9 Security ..............................................................................................................................8
1.6.10 Backup Facilities................................................................................................................8
1.6.11 Data retrieval ....................................................................................................................8
1.7 Operational feasibility................................................................................................................8
1.8 Technical Feasibility...................................................................................................................8
1.9 Financial Feasibility....................................................................................................................9
1.10 Requirement Analysis ..............................................................................................................9
1.10.1 Requirement Definition .....................................................................................................9
1.10.2 Requirement Specification .................................................................................................9
1.11 Main Components of Our Project ........................................................................................... 10
1.12 Tools Used ............................................................................................................................ 11
CHAPTER # 2
System Design ........................................................................................................ 13
2.1 Introduction............................................................................................................................ 13
2.1.1 Logical Design....................................................................................................................... 13
2.1.2 Physical Design..................................................................................................................... 13
2.2 Input Design............................................................................................................................ 13
2.3 Data Capturing ........................................................................................................................ 14
2.4 Input Validation ...................................................................................................................... 14
2.5 Output Design......................................................................................................................... 14
2.6 Data Base Design..................................................................................................................... 14
2.7 Architectural Design ................................................................................................................ 15
2.8 Conceptual Database Design .................................................................................................... 15
2.9 Modular Design....................................................................................................................... 15
2.10 Internal Data Base Design ...................................................................................................... 20
2.11 Internal Data Base Design of Crime Reporting System.............................................................. 20
Figure 2.5 FIR Table....................................................................................................................... 20
Figure 2.6 Online FIR Details Table ................................................................................................. 21
Figure 2.7 Crime Type Table .......................................................................................................... 21
Figure 2.8 Admin Login Table ......................................................................................................... 22
Figure 2.9 FIR Forward Table ......................................................................................................... 22
Figure 2.10 City Table .................................................................................................................... 22
2.12 Logical Database Design......................................................................................................... 22
2.13 Entity .................................................................................................................................... 23
2.14 Entity Relationship Model ...................................................................................................... 23
2.15 Entity Relationship Diagram ................................................................................................... 23
Figure 2.11 Data flow Diagram....................................................................................................... 26
CHAPTER # 3 System Implementation ................................................................................................ 28
3.1 Overview ................................................................................................................................ 28
Figure 3.3 FIR Page........................................................................................................................ 32
CHAPTER # 4 System Testing ............................................................................................................. 34
4.1 Introduction................................................................................................................................ 34
4.2 Testing Objectives ................................................................................................................... 34
4.3 Testing Strategies.................................................................................................................... 34
4.3.1 White Box Testing ............................................................................................................. 35
4.3.2 Stress Testing.................................................................................................................... 35
4.3.3 Acceptance Testing ........................................................................................................... 35
4.3.4 Assertion Testing .............................................................................................................. 36
4.3.5 Unit Testing ...................................................................................................................... 36
4.3.6 System Testing ..................................................................................................................... 36
4.4 System Evaluation ................................................................................................................... 36
4.5 Implementation ...................................................................................................................... 37
4.6 Installation of Computer Equipment’s....................................................................................... 37
4.7 Testing the New System........................................................................................................... 37
4.7.1 Unit Testing ...................................................................................................................... 37
4.7.2 Integrated Testing............................................................................................................. 37
4.7.3 System Testing.................................................................................................................. 37
4.7.4 Direct/ Cash Conversion .................................................................................................... 38
4.8 Conclusion........................................................................................................................... 38
Reference List................................................................................................................................... 40
List of Figures
Figure 2.1 General Data Entry ........................................................................................... 16
Figure 2.2 Delete Module .................................................................................................. 17
Figure 2.3 Update Module ................................................................................................. 18
Figure 2.4 Login Module ................................................................................................... 19
Figure 2.5 FIR Table ........................................................................................................ 20
Figure 2.6 Online FIR Details Table................................................................................... 21
Figure 2.7 Crime Type Table ............................................................................................. 21
Figure 2.8 Admin Login Table........................................................................................... 22
Figure 2.9 FIR Forward Table............................................................................................ 22
Figure 2.10 City Table ...................................................................................................... 22
Figure 2.11 Entity Relation Diagram .................................................................................. 25
Figure 2.12 Data flow Diagram.......................................................................................... 26
Figure 3.1 User interface ................................................................................................... 30
Figure 3.2 Admin Page...................................................................................................... 31
Figure 3.3 FIR Detail Page ................................................................................................ 32
List of abbreviation:
CRS: Crime Reporting System
FIR: First Information Report
PHP: Hypertext Preprocessor
MYSQL: Structure Query Language
HTML: Hyper Text Markup Language
CSS: Cascading Style Sheet
CHAPTER 1
INTRODUCTION
1
CHAPTER # 1 Introduction
1.1 Introduction
Online FIR System is the Computerization of present manual system of Police Stations. There
are many flaws and shortcomings in the present system. The present system is a manual system.
In case of present manual system all the record is kept in documented form and stored in various
types of registers. The manual system has no proper system for record storage and storing the
information about crimes and criminals. The present system of police is not automated. The
documentation of criminal records is done manually. Case files are dumped in heaps while some
are kept on shelves. These important documents quickly get dusty and because of lack of proper
storage, some criminal documents are seriously damaged. With this kind of situation, it becomes
highly difficult and even impossible to track down known criminal, access past criminal history
of a suspect and know the status of some concluded cases.
In police stations all the file work is done by the staff, so burden of work leads to the criminal’s
information to be delayed. There are also problems of record storage, updating, backup and
recovery and redundancy of data. To overcome the problems in present system we design such a
computerized information system, which is free of all the flaws, present in the manual system of
the institute. As computer is one of the leading technologies nowadays, so we propose a
computer based system that will fulfill the requirements of the police stations easily and will be
the solution to the problems faced by Police stations. It will facilitate both the user as well as
administrative staff of the Police Stations. Computerized system provides accuracy, security, and
reduced redundancy, reduction of work load, backup facilities and faster information retrieval.
1.2 Overview of the Present System
The present system of the Police Stations in KPK is a manual system. In order to make a
computerized system, we first check the present system so that we get to know about the flaws
and shortcomings in this system. This study will help us to design such a computerized system
for Police, which is free of all the flaws presented in manual system of the police station and will
facilitate both the user as well as administrative staff of police station.
2
1.3 Drawbacks in the Present System
There are some drawbacks and flaws existing in current manual system. For example, record
about crime cases and FIR’s are recorded manually. There is no proper security of these record
books, because all the record books are stored in the cabinet and anyone can damage them or
anything can possibly damage them, these problems have plagued the police department and
affect the policing system in the country. Some of these problems are enumerated below.
1.3.1 Time Consuming
In the existing system, the information about the crimes is stored in registers. When information
about a particular crimes or FIR’s is required or when some changes are needed in the record,
one has to search many registers for required register. Moreover, it is time consuming task to
change or update information manually.
Also the present system requires a lot of time to accomplish the task of complaining a report, and
other updating or changing in the current information.
1.3.2 Redundancy of Data (Duplication of Data)
There are a lot of redundant data found in the present system. The data of a crime and criminals
is to be kept at many places; i.e. in many different files. Similarly, the complaint forms and the
other important information about crime or criminal are also produce redundant data.
1.3.3 Changing/Removing Of Records
If there is an error in a single record then the police department has to make changes in many
files. If they want to remove or change the data, they will have to change them at all place, where
they kept them.
1.3.4 Storage Media
For handling data and related information, several registers are used i.e. the same data is stored at
multiple locations which wastes a lot of stationary.
1.3.5 Information Updating
It is a well-known fact that with the passage of time, old data needs modification. Process of
modification, updating and addition of new information and data are very slow.
3
1.3.6 Backup and Recovery
In the existing manual system there is always a risk of accidental data lost. There is no backup
and recovery facility presented in manual system, so important data may be lost.
1.3.7 Integrity
It has been proved that the manual system of collecting and storing personal information is
devoid of integrity.
1.3.8 Burden of Work
In police department all the files work is done by the staff, so burden of work leads to the
important works to be delayed.
All the above mentioned drawbacks in the present system lead to an inefficient and time
consuming process of handling records about crimes. The present manual system is not capable
of fulfilling the requirements of the reports about a crime on the basis of particular criteria.
Besides, in time retrieval of crimes and criminal’s complete record is also not possible without
devoting enough time for searching different files. In the existing manual system there is always
a risk of accidental lost of recorded data. If once such information is damaged, then there remain
no backup copies to be used in the future. So it becomes difficult to recover information once
destroyed in the manual system.
1.4 Background
Our Police Stations are still represents 19th century, nothing has changed nor upgraded if you go
there to register the FIR you will witness that same old constabulary system, Same old registers
same old ways Carbon papers kept between two for multiple copies and registering FIR least
takes an hour.
Later when the police forward the registered FIR to designated Investigation officer, he adds up
more papers in it, in which he reviews the crime scene and other technicalities, there is no such
thing as Copy of CNIC attached with Registered FIR by the Complainer, 14 days of duration for
the investigation after which case gets forwarded to the court or either ends up in the record
room.
4
Does it has to be like this all the way since dark ages, to ensure that after FIR has been registered
informing onto the computerized data base doesn’t exists by which all other Police Stations in
other respective areas , cities , town across Pakistan gets to know if they have any information
regarding that issue or suspect?
Even if the government start upgrading the policing and FIR system one by one, I think there
will be a day when people would be able to know the status of their registered FIR online and if
nothing has happened for far, forward the complaint to the courts, but unfortunately nobody
seems to be bothered about Computerized FIR Registration which is must advantages I wouldn’t
be able to list down all but I am sure if you are educated person than you know what is possible
in this age when the data gets Online,
What to expect from such departments ( JUSTICE ) please don’t joke with me, increasing
salaries and benefits reducing the ratio of bribery in this department but until and unless FIR’s
will not get logged Online we wouldn’t be able to know what is actually happening.
I feel like crying after seeing such policing system, 1947 till 2012 only thing which has upgraded
is SHO’s Room with AC rest It’s a place where you can say Timeless world you cannot tell
which year it is when you are in the police station, neither proper place to seat, nor the
environment is good. Over all you will witness yourself that Years even centuries doesn’t matter,
are we improving the System? or we have become the part of it by accepting just the way it is,
beside this what other options to do have, The answer is NONE, Speak up like me, somebody
might hear you out.
Else, only Personal Source is most welcome, if anyone from authorities above IO and SHO read
this would ask them and order them as if without that, it is not their duty to perform on regular
basis. Where are we living some sort of Stone age?
Speak up to improve and for the change by yourself, else nobody is bothered to hear the deeds.
Police Departments of KPK, the overall System is manual .There are many problems in this
manual System all record of crimes and criminals are store in register which is very difficult for
administrative department to find the record of different crimes and criminals.
5
Police Departments of KPK, the overall System is manual .There are many problems in this
manual System all record of crimes and criminals are store in register which is very difficult for
administrative department to find the record of different crimes and criminals. In manual system
also find out the missing criminals and most wanted for Police Department. We want to
computerize this manual system .we developed Online FIR System for Police department which
is user friendly and allots of facility. For Police department it saves the time easy to use and very
easy for the admin as well as for users.
1.5 Proposed System and Objectives of the System
Since we have discussed that present manual system of the Police Station of KPK is lengthy and
time consuming. After a detailed study of the current system, it is a good time to propose a new
system which is based on a computer. As computer is one of the leading technology now a days,
so we propose a computer based system that will fulfill the requirements of the Police Stations of
KPK easily and will be the solution to the problems faced to the Police department. The
proposed system is aimed to remove all the drawbacks and limitations of existing system and
making it more responsive to the users and management needs. In the proposed system, we have
tried our best to meet all the objectives of the Police Department. The major objectives of the
proposed system are to provide the faster means of Crime Compliant Report. It will reduce the
time consumed in preparation of reports and to get benefit from the latest technology of
computers.
The proposed system includes the following features:
1. To provide a secure system to users
2.
Complaint registration
3. Online FIR System
4. Giving Feedback to users.
1.6 Advantages of Proposed System
In contrast to old manual system the proposed system has the following advantages:
1.6.1
Accessibility
Accessibility refers to the design of products, devices, services, or environments for people with
disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and
6
"indirect access" meaning compatibility with a person's assistive technology (for example,
computer screen readers).
Accessibility can be viewed as the "ability to access" and benefit from some system or entity.
The concept focuses on enabling access for people with disabilities.
1.6.2 Accuracy and Consistency
The basic advantage of computerized system is its accuracy. A man is vulnerable to mistake
where computer software is free. Similarly, the consistency of the records and transactions make
a computer more advantageous over manual system.
1.6.3 Input Improvements
In the proposed system, all the input data is stored in the appropriate database files. Moreover,
the user can store the same data only at a single location thus reducing consumption and
redundancy and hence the chances of errors are minimized.
1.6.4 Faster Information Retrieval
The data of individual criminals including chest number is stored in a computer and can be
retrieved which is required by the police department. Thus the user can also obtain the required
information by clicking buttons etc in no time in contrast to the manual system.
1.6.5 Reduction of Workload
In the proposed system no work is involved. It helps in reducing workload on staff members of
the police department. The computer does all the work of making entry of data of crimes and
criminals… The computers will do the rest of the work.
1.6.6 Flexibility
The proposed system is flexible enough i.e. addition of new records, updating of records and
handling of new application are possible.
1.6.7 Reduced Redundancy
In the new system data is stored centrally. The storage of the same data is done at a single
location. So the redundancy of data has been reduced up to a great extent as compared to the
present system, where the same data has to be stored in different registers and files.
7
1.6.8 Reduction in Cost
The cost of conducting the information manually is greatly reduced. Because computers do all
work then there is no need of paper work. The reduced manual and paper work minimizes the
cost of the process of new entry of criminal record. This reduction in cost is especially important
for all police department.
1.6.9 Security
The proposed system provides enough security against data loss and also ensures that illegal
access to the data is denied.
1.6.10 Backup Facilities
Proposed system provides the facility to back up the data for safety purposes in case of data
corruption or data loss.
1.6.11 Data retrieval
Data retrieval means obtaining data from a database management system such as ODBMS. In
this case, it is considered that data is represented in a structured way, and there is no ambiguity in
data.
1. It will reduce redundancy
2. The users can retrieve information fast and timely.
3. It will reduce workload of employee
4. It will be more flexible
5. It provide more security
6. It has backup facilities
1.7 Operational feasibility
The software is very user-friendly, the admin and user can easily operate the software without
any difficulty. There are somewhat trained computer personal indifferent and some of them are
not familiar with computer and they can be trained.
1.8 Technical Feasibility
This is a web base application. The following technology needed for the system to be developed
and is available to us at our work place.
8
DBMS
MYSQL
Operating system
Microsoft Windows10
Design and coding tools
HTML5, CSS3, JavaScript, PHP5
Documentation tools
MSOffice 2016
Designing tools
Adobe Photoshop and Paint
1.9 Financial Feasibility
The cost of converting the manual system into a computerized is one of important factor. The
proposed system is financially very visible and feasible. It is not very inexpensive because it is
an individual project .So there are no costs invaded like searching and hiring personal. The
technologies that we are going to use are in common use and are always made available to work
with. So there is no purchase costs involved, no huge cast involved in training. Also no extra
hardware or additional staff is required for the department.
1.10 Requirement Analysis
It is a communication between customer and software development team. To get better
understanding of the requirement, a prototype was made and then we visited to many time in
Police department’s of KPK for requirement gathering, which resulted more benefits and
functionalities which was impossible without requirement specification.
1.10.1 Requirement Definition
In this stage we define different users of the system and their role in operating this software. .i.e.
the administrator can manage the whole system i.e. Administrator manages user, requirements.
While users manage information of his own.
1.10.2 Requirement Specification
Out of various alternatives structured language is used to write down functional requirement.
Structure language which is a restricted form of natural language use template to specify
requirements.
9
A feasibility study is a short focus study that aims to answer of a number of questions
1. Does the system contribute to overall object of organization?
2. Can the system be implemented using current technology and with given cost and
schedule constraints?
3. Can the system integrated with other system which are already in place?
4. You should talk with information source to discover the answer to the question?
5. How would the organization cope if this system not works?
6. What is the problem with current processes and how a new system would help alleviate
these problems?
7. What direct contribution will the system make to the business objective and
requirements?
8. Can information be transform to and from other organizational system?
9. Does the System require technology that has not previously been used in organization?
10. What must be supported by the System and what need not to be supported?
A successful completion and adoption of the automated system will definitely make the work
easier around its field by maintaining all records about police department i.e. FIR management
system, feedback, etc.
The existing manual system will be replaced by automated. As it is mentioned earlier that a
manual system is more laborious, insecure and time consuming. All the information are kept and
derived manually. This system will be able to meet all the requirements of easy to use, easy to
maintain, secure etc. Records and information will be kept and upgraded safely and data will be
processed faster in proposed automated system.
1.11 Main Components of Our Project
1. User
2. Admin
3. FIR System
4. Feedback
5. Program
10
1.12 Tools Used
The tool used in the development of “Crime Reporting System” is MYSQL at
the backend.
For front end for window base application we use PHP. Besides these tools we used have the
number of other CASE tools (CSS, HTML, and JavaScript).
11
CHAPTER 2
SYSTEM DESIGN
12
CHAPTER # 2 System Design
2.1 Introduction
The design is a solution, the translation of requirements into center ways of meeting. The design
is actually the process of analyzing, organizing and developing a database model that accurately
reflects the organization functioning in the real world and implementing that model by creating a
database requires an appropriate methodology. System can be divided into two phases:
1. Logical Design
2. Physical Design
2.1.1 Logical Design
The logical design describes the detail specification for the proposed system. We can say that it
describes its own feature. Input, output, file (table) and database in manner that meets the project
needs. In logical design work with users is done to develop general design, choose best design,
develop system flow charts, identify hardware, software and personal needs and revise estimates
etc.
2.1.2 Physical Design
The purpose of physical design is to translate the logical description of data into the technical
specification for storing and retrieving data. The goal is to create design for storing data that will
provide adequate performance and ensure database integrity, security and recovery.
Physical database design does not include implementing files and databases (i.e. creating them
and loading data into them).
2.2 Input Design
The input design specifies the number in which the user enters the data to the system for
processing at later stage. Input design can insure the reliability of the system and provide an
accurate result. The input determines whether the user interacts with the system efficiently or
not. The input design can also be explained as a link between the user and the world. Input
design consists of those steps necessary to put transactions data into usable form of processing.
While designing the input for the Crime Reporting System for police departments of KPK has
the following objectives were kept in mind as guidelines.
13
1. Reducing the amount of input
2. Avoiding errors in data
3. Keeping extra steps
4. Keeping the process simple
5. Avoiding delays
2.3 Data Capturing
In input design only those items are captured which must actually be the subject
of input
while designing the input, following points were kept in mind.
1. Crime information
2. Complaint report record
3. Admin information
4. User information
2.4 Input Validation
Input validation is general term given to method, aim for detecting errors in the input. The main
thing, which is considered in the input, is that what the chances of error are? Following are input
validation used for centralized system for Crime Reporting System for police department.
1. Empty entry Control
2. Data Type Validation
3. Not Null
2.5 Output Design
A system is considered to be successful or unsuccessful on the basis of output design. The term
“output” means that after compilation of physical design what errors come out of the computer
system for the user. The output in project is considered as the backbone of the project. All
managerial design is actually made through these reports. Basically the reports are very
important aspect of the output. The user creates various reports in response to queries.
2.6 Data Base Design
Database Design is a creative process of transforming:
14
1. Problems into Solution
2. The description of solution
3. Intelligent database design is perhaps the most critical element of an optimal solution
with respect to performance. In fact, poor design is usually the culprit for poorly
performing solutions.
4. Designer of the database should satisfy the user.
2.7 Architectural Design
The primary objective of architectural design is to develop a modular program structure and
represent the control relationship between them.
2.8 Conceptual Database Design
Tells the user exactly
1. What the system will do
2. Describe the functions of the systems
3. The system will work in the following areas
4. Unique authorized access to all registered users
5. Purchasing of products
6. Data Validation checks
7. The system is defined by its boundaries, entities, attributes, and relationship
2.9 Modular Design
Modular design occurs after data; architecture and interface designs have been established. In
and world, the modular specification required to be define algorithmic details would be stated in
a natural language such as English because it is easily understandable. And then that straight
forward plain English are converted to diagrams.
There is no question that graphics tools such as flow charts or box diagrams provide excellent
pictorial patterns that readily depict modular details. However graphical tools are misused, the
wrong picture may lead to wrong software. In this section we will demonstrate some of our basic
modules by using Flow Charts. Such as form entry, deletion, insertion, updating and reports.
15
Start
Form
YES
Stored in database
Confirmation
Message
End
NO
Enter Data
Form
Is Valid?
Back
Figure 2.1 General data entry
16
Start
Load Data
Form
No
Is Found?
Back
Yes
Runs Delete
Module
Delete
Confirmation
Message
End
Figure 2.2 Delete Module
17
Start
Load Data
Form
No
Is Found?
Yes
Runs Update
Module
Store
Update
Confirmation
Message
End
Figure 2.3 Update Module
18
Start
LOGIN
Enter User
Name and
Password
Back
Form
Incorrect
Message
No
Is Correct?
Yes
Runs Login
Module
Logins
End
Figure 2.4 Login Module
19
2.10 Internal Data Base Design
The purpose of the Internal or physical database design is to translate the logical description of
data into the technical specification for storing and retrieving data. As we know that the physical
database design requires several critical decisions that will affect the integrity and performance
of the application system. One of those decisions is the storage format (data type). So for our
project we have taken the decision to the following data types and length for the attributes. The
following are the tables, their attributes and the primary and foreign keys in the table
2.11 Internal Data Base Design of Crime Reporting System
Tables
Column
Type
Null
Id
int(11)
No
first_name
varchar(50)
No
last_name
varchar(50)
No
Gender
varchar(10)
No
date_of_crime
Date
No
time_of_crime
varchar(50)
No
Address
varchar(300)
No
City
varchar(50)
No
contact_no
varchar(20)
No
Email
varchar(50)
No
crime_type
varchar(50)
No
crime_location
varchar(200)
No
Incident
Text
No
photo1
varchar(200)
No
photo2
varchar(200)
No
Figure 2.5 FIR Table
20
Default
Column
Type
Null
Default
F_id
int(10)
No
date
Datetime
No
time
Datetime
No
description
varchar(45)
Yes
NULL
status
varchar(45)
Yes
NULL
crime_id
int(10)
No
id_proof
varchar(45)
No
id_proof_no
int(10)
No
crimephoto1
varchar(255)
Yes
NULL
crimephoto2
varchar(255)
Yes
NULL
crimelocation
varchar(45)
No
reg_id
int(10)
No
claim_id
int(10)
No
victim_id
int(10)
No
dt_time
Datetime
Yes
NULL
area_id
int(10)
Yes
NULL
Figure 2.6 Online FIR Details Table
Column
Type
Null
crime_id
int(10)
No
crime_type
varchar(45)
No
description
varchar(45)
No
Default
Figure 2.7 Crime Type Table
21
Column
Type
Null
Default
Username
varchar(45)
No
Password
varchar(45)
No
Type
varchar(15)
Yes
NULL
Status
varchar(10)
Yes
NULL
last_logindatetime
datetime
Yes
NULL
Figure 2.8 Admin Login Table
Column
Type
Null
F_id
int(10)
No
username
varchar(45)
No
status
varchar(15)
Yes
description
varchar(45)
No
dt_time
Datetime
Yes
from
varchar(45)
No
Default
NULL
NULL
Figure 2.9 FIR Forward Table
Column
Type
Null
city_id
int(10)
No
city_name
varchar(45)
No
Default
Figure 2.10 City Table
2.12 Logical Database Design
Logical design describes the detail specification for the proposed system. We can say that it
describes its own features. Input output tables and database in a manner that meets the project
needs. In logical design work with users is done to develop general system design, choose best
22
design, develop system flowcharts, identify hardware, software and personal needs and revise
estimates etc.
2.13 Entity
Anything that produces or consumes information is called entity. The representation of any
composite information that must be understood by software is called data object, by composite
information we mean something that has a number of different properties or attributes.
We have used the following entities in our project.
1. FIR
2. Login
3. Get Crime Alert
4. Join us
5. About us
6. FAQs
7. Paragraph
8. Emergency contact Numbers
9. Services
10. Quick links
11. Online Registration
2.14 Entity Relationship Model
The entity relationship model is a tool for analyzing the semantic feature of an application that is
independent of events.
Entity-relationship modeling helps reduce data redundancy. This
approach includes a graphical notation, which depicts entity classes as rectangles, relationships
as diamonds and attributes as ovals. For example situations a partial entity relationship diagram
may be used to present a summary of the entities and relationships but not include the details of
the attributes.
2.15 Entity Relationship Diagram
The entity relationship diagram provides a convenient method for visualizing the interrelationship among entities in a given application. This tool has proven useful in making the
transition from an information application description to a formal database schema. The entity
23
relationship model is used for describing the conceptual scheme of an enterprise without
attention to the efficiency of the physical database design. The entity relationship diagrams are
later turned into a conceptual schema in one of the other models in which the database is actually
implemented.
24
First
Name
Last
Name
Gender
D_Incident
City
Detail
Incident
Location
Time
Contact
Address
FIR
M
Manage
FIR
Register
Crime
Type
Picture
ID
ID
M
User
name
M
M
Admin
1
Feedback
User
Password
M
M
M
Receive
Contact
Give
Figure 2.11 ERD
ID
Name
Email
25
Message
Subject
Figure 2.12 Data flow Diagram
26
CHAPTER 3
SYSTEM IMPLEMENTATION
27
CHAPTER # 3 System Implementation
3.1 Overview
It is particularly important first to design how the system will look and respired to user before
designing the software structure. The most critical and creative aspect of development is to
design the user interface. User interface design determines how the system will look the user
from outside.
The interface design create in effective communicate medium between human and a computer,
following a set of design principle. The design identifier interface objects action and then creates
a screen layout that formats the basic for a user interface prototype. User interface begins with
the identification of user, tasks and environment requirements. User interface for the software
should be design in such a way that is friendly to the user, easy to use and easy to understand. It
should provide high quality interface between the user and the system. The results produce by
our software should be consistence.
In designing the user interface it has been kept in mind that non-technical personnel will operate
the system with very little or no technical knowledge. Therefore the user interface has been
designed is user friendly as possible that facilitate easy and quick and has been used and
designing the screen are:
1. Home
2. Join Us
3. Get Crime Alert
4. FIR
5. Services
6. Emergency Contacts
7. About Us
8. Missing Citizens
9. Police Initiatives
10. Traffic Warden Service
28
11. Rapid Responsive Force
12. Dispute Resolution Council
13. Help Prevent Crime
14. Police Access Services
15. Police Services Lines
16. Elite Women Commandos
17. CNIC verification
18. Vehicle verification system
19. Reporting Room
20. Geo Tagging
29
Figure: 3.1 Crime Reporting System
30
Figure: 3.2 Admin Page
31
Figure 3.3 FIR Page
32
CHAPTER 4
SYSTEM TESTING
33
CHAPTER # 4 System Testing
4.1 Introduction
System testing is essential step for the development of a reliable and error free system .in a
software development project ,errors can be introduced at any stage during the development
.Each phase has its own techniques for the detection and correction of errors in that phase .
However, some requirements errors and design errors are likely to remain undetected.
Ultimately these errors will be reflected in a code. Since code is the only product that can be
executed and whose actual behavior can be observed, testing is the phase where the errors
remaining from the early phases also must be detected. Testing is the process of detecting
and correcting as many errors as possible in the developed software before delivery to the
customer. Test case is specification of the test and the output from the system plus a
statement of what is being tested. Test data are the inputs which have devised to test the
system.
4.2 Testing Objectives
1. To find errors in the developed software.
2. To check that working of the software function is according to the specifications. Their
behavior and performance requirement are fulfilled.
3. To check the reliability and quality of the software.
4.3 Testing Strategies
Following are the basics strategies that were used for testing of the software.
Black box testing
White box testing
Stress testing
Acceptance testing
Assertion testing
34
Can only be determined by studying its inputs and the related outputs. It is called functional
testing because here the tester has only concerned with functionality and not with the
implementation of the software.
In black box testing only the functionality of the software was tested without a record to the
code .If the functionality which was expected from a component is provided then the black
box testing is completed.
4.3.1 White Box Testing
White box testing is also called glass box testing and structural testing .The objective of
white box testing is not to exercise all the different input or output condition but to exercise
the different programming and data structure used in the program.
In white box testing internal code return in every component was tested and it was checked
that the code written is efficient in utilizing various resources of the system like memory etc.
4.3.2 Stress Testing
Stress test is designed to confront program with abnormal situation. Stress testing executes
system in a manner that demands rescore in abnormal quality, frequency or volumes. For
example:
1: Input data rates may increase to determine how input function will respond
2: Tests that’s requires maximum memory or other resources are executed.
Basically, the tester wants to break the program.
In stress testing the software was tested against the boundary conditions. Various inputs
fields were tested against
Abnormal values and it was tested that the software does not behave abnormally at any time.
4.3.3 Acceptance Testing
Acceptance testing is performed with realistic data of the client to demonstrate that the
software is working properly.
35
In acceptance testing the software was checked for completeness that it is ready. Quality
assurance department performs the acceptance testing that the software is ready and can be
given to the customer.
4.3.4 Assertion Testing
In assertion testing the software is tested against the possible assertion. Assertion is used to
check the program and various locations that whether the state of the program at a particular
point is the same as expected or not.
4.3.5 Unit Testing
Unit testing focuses verification effort on software component or module which is the
smallest unit of software design. The unit testing is white box oriented and it can be
conducted in parallel for multiple components.
In unit testing we checked that all individual components were working properly. Before
integration of all components unit testing is essential because it gives a confidence that all the
components individually are working fine and ready to be integrated with the other ones.
4.3.6 System Testing
System testing is actually a series of different tests whose primary purpose is to fully exercise
the computer based system. Although each test has a different purpose, all work to verify that
system elements have been properly integrated and perform allocated functions.
When all the units were working properly and unit testing was performed and checked all the
integrated components as a whole and looked for possible discrepancies, which could have
arisen after the integration.
4.4 System Evaluation
The objectives of the system evaluation is to determine whether the desired of objectives
have been accomplished or not. Determining the merits and demerits of the proposed system
over the existing system is also covered in system evaluations. This is concerned with the
detailed study of the developed system, from implementation point of view.
36
4.5 Implementation
This phase consists of bringing the new system in operation and turning it over the users.
Briefly involves the following steps.
Training: It involves
1. User group
2. Administrator
4.6 Installation of Computer Equipment’s
It involves
1. Locations
2. Power supply
3. Space requirements
4. Air conditioning
4.7 Testing the New System
System testing of the developed system was performed in these three steps.
4.7.1 Unit Testing
In unit testing the different modules of software were tested independently to locate errors.
This helps in locating errors, in coding and logic that were contained within a particular
module.
4.7.2 Integrated Testing
After unit testing, combined testing of all modules was carried out. The purpose was to
determine that all the modules are correctly integrating with each other.
4.7.3 System Testing
Final testing was done on the entire system to check that whether the desired specification
and requirements are met or not. The main aim here was to determine the inconsistencies in
the developed system. Hence the whole system was tested. Put the New System into
37
Operation At this point, a final dress rehearsal sometimes runs. It is done in the following
ways.
4.7.4 Direct/ Cash Conversion
In this approach, as entire new system is installed, the old system is completely dismantled,
leaving the organization suddenly to rely on the new system alone. The advantage of the
crash conversion is that when the old system is seriously inadequate or radically different
from the new system and when the conversion will be so rapid that it will not severely
disrupt operations. The crash conversion also has advantages i.e. the crash conversion is
risky, and even for minor problem can seriously delay the implementation schedule. Careful
planning and attention to detail are necessary for a successful crash conversion.
4.8 Conclusion
The project titled as “Crime Reporting System” is a web based application. This
software provides facility for reporting online crimes, complaints, missing persons, show
criminal details. This software is developed with scalability in mind. Additional modules can be
easily added when necessary. The software is developed with modular approach. All modules in
the system have been tested with valid data and invalid data and everything work successfully.
Thus the system has fulfilled all the objectives identified and is able to replace the existing
system.
The project has been completed successfully with the maximum satisfaction of the organization.
The constraints are met and overcome successfully. The system is designed as like it was decided
in the design phase. The project gives good idea on developing a full-fledged application
satisfying the user requirements. The system is very flexible and versatile. This software has a
user-friendly screen that enables the user to use without any inconvenience. Validation checks
induced have greatly reduced errors. Provisions have been made to upgrade the software.
The
application
has been tested with live data and has provided a successful result. Hence the software has prove
to work efficiently.
An effective criminal justice response to hate crimes involves a number of important elements:
close police-community relations, public confidence in the effectiveness of the police response to
reports of hate crimes as well as appropriate processing of those reports by the courts. The
quality of the police response to hate crimes is critical, as is the public perception of that
response. If people feel that the criminal justice system is not responding appropriately and
vigorously to the problem of hate crimes, these incidents will remain unreported. However,
38
nothing is more critical than having an accurate idea of the true nature and full extent of the
problem. This can only come about if a greater effort is made to collect comprehensive hate
crime statistics. At the present, KPK lags behind other provinces in this regard. The present
report represents the first, small step towards documenting the incidence of this pernicious form
of criminal activity, which, by its very nature, strikes at the heart of a multicultural society.
39
Reference List
1. http://www.w3school.com
2. http://en.wikipedia.org/wiki/Waterfall_model
3. http://en.wikipedia.org/wiki/Software_development_process,
4. http://en.wikipedia.org/wiki/Spiral_model
5. http://en.wikipedia.org/wiki/Prototype
6. https://www.google.com.pk/?gws_rd=cr,ssl&ei=ey3HVPXGC6HmyQOCxIDQCA#q=prototype
+model+diagrams
7. https://www.google.com.pk/?gws_rd=cr,ssl&ei=9LXNVMaeI9bnatzKgng#q=history%20of%20o
nline%20fir%20system%20in%20pakistan
8. http://www.incpak.com/editorial/govt-must-upgrade-police-computerized-fir-online-record/
40