Debre Berhan Crime File Management System
Debre Berhan Crime File Management System
Debre Berhan Crime File Management System
Contents
LIST OF TABLES.................................................................................................................................................iii
LIST OF FIGURES......................................................................................................................................................iv
Acknowledgment....................................................................................................................................................vii
Abstract................................................................................................................................................................. viii
CHAPTER ONE...........................................................................................................................................................1
1.1 Introduction....................................................................................................................................................1
1.3 Problem of the statement..............................................................................................................................1
1.4 Objectives of the project................................................................................................................................2
1.4.1 General objectives...................................................................................................................................2
1.4.2 Specific objective.....................................................................................................................................2
1.5 Methodology..................................................................................................................................................2
1.5.1 Fact Finding Techniques..........................................................................................................................2
1.5.2 System Analysis and Design Techniques..................................................................................................3
1.5.3 Tools used................................................................................................................................................4
1.6 Feasibility study..............................................................................................................................................4
1.6.1. Technical feasibility................................................................................................................................4
1.6.2. Economic Feasibility...............................................................................................................................4
1.6.3 Operational Feasibility.............................................................................................................................5
1.6.4 Political feasibility....................................................................................................................................5
1.6.5 Behavioral feasibility...............................................................................................................................5
1.6.6 Schedule Feasibility.................................................................................................................................5
1.7 scope of the project........................................................................................................................................6
1.8 Significance of the project..............................................................................................................................6
1.8.1 Benefits to police station.........................................................................................................................6
1.8.2 Benefits to Citizens..................................................................................................................................6
1.8.3 Benefits to Police Department.................................................................................................................7
1.9 limitations...................................................................................................................................................7
i
Debre Berhan crime file management system 2007
CHAPTER TWO......................................................................................................................................................8
2.1 Introduction....................................................................................................................................................8
2.2 Existing system description............................................................................................................................8
2.2.1 Drawbacks of Existing System..................................................................................................................8
2.2.2 Explanation of the business rule of the organization...............................................................................9
2.2.3 CRC (class responsibility and collaboration)..........................................................................................10
2.3 Proposed system description.......................................................................................................................11
2.3.2Functional requirements........................................................................................................................13
2.3.3Nonfunctional requirements..................................................................................................................14
2.4 System models and the artifacts..................................................................................................................15
2.4.1 Use case diagram...................................................................................................................................15
2.4.2Dynamic models.....................................................................................................................................32
2.4.3 State chart diagram...............................................................................................................................64
2.4.4 UML class diagram.................................................................................................................................70
CHAPTER THREE.....................................................................................................................................................72
SYSTEM DESIGN......................................................................................................................................................72
3.1 Introduction..................................................................................................................................................72
3.2Design goals and objectives...........................................................................................................................72
3.3 System decomposition.................................................................................................................................73
3.4 Component diagram.....................................................................................................................................75
3.5 deployment diagram....................................................................................................................................76
3.6 user interface prototyping design................................................................................................................78
3.7 design of class diagram (class mapping).......................................................................................................78
3.8Data base design...........................................................................................................................................80
CHAPTER FOUR.......................................................................................................................................................81
IMPLEMENTATION DELIVERABLE OF THE NEW SYSTEM.......................................................................81
4.1 Introduction............................................................................................................................................81
4.2 User Interface...............................................................................................................................................81
CHAPTER FIVE....................................................................................................................................................85
PROTOTYPE DEVELOPMENT...........................................................................................................................85
CHAPTER SIX.......................................................................................................................................................97
ii
Debre Berhan crime file management system 2007
6.1 Conclusion....................................................................................................................................................97
6.2 Recommendation.........................................................................................................................................97
Reference...........................................................................................................................................................97
LIST OF TABLES
Table 1.1: Time Schedule for Our Project …………………………………………………….…6
Table 2.5: Main Course of Action about Add New User Account………….….……..24
Table 2.13: Main Course of Action about posting missing persons …………...……30
iii
Debre Berhan crime file management system 2007
Table 2.14:main course of action about view posted information’s…………...……31
Table 2.17: main course of action about assign investigation team ……..…………33
LIST OF FIGURES
Figure 2.1: usecase diagram for Debre Berhan police station management
system…………………………………………………………………………………20
Figure 2.4: activity diagram for posting safety tips and missing persons ….…….…..37
iv
Debre Berhan crime file management system 2007
Figure 2.19: sequence diagram for register new crime case ………………………..……53
Figure 2.33: collaboration diagram for register new crime case ………………………...69
Figure 2.39: State chart diagram for add new user ……………….……………..………75
Figure 2.40: State chart diagram for generate investigation report …......……………..76
v
Debre Berhan crime file management system 2007
Figure 2.41: State chart diagram for generate FIR report..…..... …………………….….77
Figure 2.43: State chart diagram for post missing persons and safety tips
criminals…………………………………………………………………………………….....78
Figure 2.44: State chart diagram for register new crime case …………….......................79
Figure 2.47: class diagram for Debre Berhan police station crime file
management……………………………………………………………………………….….81
Figure 3.1: component diagram for Debre Berhan police station crime file management system….70
Figure 3.2: deployment diagram for Debre Berhan police station crime file management system....71
Figure 3.4: Class diagram designs for Debre Berhan police station crime file management system...73
Figure 3.5: database design for Debre Berhan police station crime file management system……...74
vi
Debre Berhan crime file management system 2007
ACRONYM
BR Business Rule
PHP Hypertext Preprocessor
HTML Hypertext Markup Language
CHMO Condominium House Management Office
CHMA Condominium House Management Administrator
.
UC-ID Use Case Identification Number
HTTP Hypertext Transfer Protocol
vii
Debre Berhan crime file management system 2007
viii
Debre Berhan crime file management system 2007
Acknowledgment
First of all, we would like to thank our almighty God, who gives us love, patience, healthy, wisdom and
ability to walk through all the problems and obstacles during the period of our study.
Our heartfelt appreciation for our adviser Instructor Endalkachew Ali for his indefatigable guidance,
valuable suggestion, moral support, and constant encouragement in the documentation part and also
instructor shamble for his constructive opinion and willingness to participate in each part of our project
and his effective direction, assistance and guidance for the accomplishing of implementation part of this
project. we also want to thank inspector DagnachewWorku and inspector BelaynehDamtew, who gave
us information about Debre Berhan police station that we are asking for our project.
Finally but not the least, we would like express our love, thanks, appreciation, and respect for the
ongoing support of our parents and family members, for their continues encouragement and financial
support. And also we would like to thank the teaching staffs of computing who have contributed wholly
to the success of this project.
ix
Debre Berhan crime file management system 2007
Abstract
In current competitive scenario every business/public establishment needs quality and systematic
process to increase their working efficiency as well as improve their productivity. It is keeping in mind
this business philosophy that we propose Crime files Management System for Debre Berhan police
station. Our system will deal with all the aspects of Managing a Crime Report against any FIR lodged by
citizen starting from Citizen’s FIR entry, investigation processing, case resolution, tracking of cases as
well as report generation.
x
CHAPTER ONE
1.1 Introduction
The main purpose of this project is to develop crime file management system for Debre Berhan police
station. Debre Berhan police station has established in order to prevent crimes and sustain peace in the
city and around the city. This station has mainly two functions. Those are preventing crimes before
happening and investigation on different crimes after happening. Currently Debre Berhan police station
uses manual file handling system which is a very time consuming activity and unsecured.
After completed this project the proposed system will help the police department to manage
investigation files and FIRs, to generate fast reports, and to retrieve criminal cases in efficient manner.
This system will also provide facility for reporting FIRs and missing persons online, and show most
wanted person details. Generally the new system will change the existing manual system in to
computerized system.
1.5 Methodology
1.5.1 Fact Finding Techniques
The Methods and techniques we use to analyze the existing system and designing web based system
includes, interview, document analysis and practical observation. Those methods which help us to gather
the required data to analyze our project and those methods selected due to the time and the
organization’s willingness.
Primary Techniques: Interview
To get the basic information and background information about the existing system, we have asked the
police officer of Debre Berhan Police station.
This technique provides information on how the existing system works .There for we have analyzed
different forms in current manual system.
During this phase the team uses to model the function of the system (use case modeling), find and
identify the business objects, organize the objects and identify the relationship between them and finally
model the behavior of the objects in detail.
During this phase our team uses Microsoft Visio software to refine the use case model and rational rose
for designing the sequence, collaboration, activity diagrams and to model object interactions and
behavior that support the use case scenario.
The reason why we have selected object oriented system analysis and design method specifically UML
(Unified Modeling Language) model is because of the following advantages:-
1.9 limitations
Limitation is element of factor or subsystem it restricts the system decision making from achieving
potential goal of the system. There are many constraints within our proposed system that limit their
effectiveness of performance. Our system is limited only in the process of crime file management
system of the Debre Berhan police station.
The above activities or subsystems are proposed system limitations because of the following reasons:
Time:-Is the main factor of limitation our proposed systems that limit its performance
because while we are developing the system it takes more time and we may not get
enough time to automate the system.
Resource: - we have not laptop as an alternative when arbitrary failed the desktop and
also when the power is off for a long time.
CHAPTER TWO
SYSTEM ANALYSIS
2.1 Introduction
In this chapter the existing system of Debre Berhan police station is clearly defined by answering how
existing system was working? In what way the FIRs (first information report) are managed? What are
techniques being used to handle investigation files? What are the business rules of the station? And what
are the problems in the existing system? After studying the existing system it is possible to understand
that how the proposed system can solve the existing system problems. Studying the existing system also
used to determine both functional and nonfunctional requirements.
Br1: New crime reports (first information reports) have to received and organized by front line police
officer
Br2: FIRs should get fast response as much as possible if and only if the FIR is crime case
Br4: The crime should be happened in Debre Berhan city or around the city, in order to start
investigation process.
Br8: A national army staff military can’t asked by police for his crime.
Br9: Front line police officer should work for 24 hours to accept crime reports
Br10: In case of disagreements between husband and wife, the reports should be submitted by him or
herself in order to get response from police.
Br11: Investigation officer cannot use force and other illegal methods to do their investigation.
Br12: Victims should qualify whatever asked by officer In order to record their case
Br13: Closed criminal cases should be recorded, and should be ordered by name of investigator
The administrator of Debre Berhan police station crime file management system has a permission to add
account when polices are transferred from another region, and inactive or update police account when
needed. On the admin page the administrator can view and easily manage the reports, can assign
investigation team for each case, can easily identify which criminal case is investigated by whom,
which cases are closed and which are in progress and also can easily retrieve criminal cases.
In the proposed system, investigative officers can register and update progress case information’s, can
easily retrieve criminal’s case for investigation purpose, can generate investigation reports, and post
wanted criminal information.
In proposed system polices can accept FIRs online and organizes them to generate FIR report, can post
safety tips and missing persons, can generate reports and can easily search criminals case.
In Debre Berhan police station crime file management system, the users can send FIRs online, can view
wanted criminals, missing persons and safety tips.
Since crime file management system is actually a serious process, even a simple error lead to big
problems. So the proposed Debre Berhan police station crime file management system should be error
free.
The aim of proposed system is to develop a system of improved facilities. The proposed system can
overcome all the limitations of the existing system. The system provides proper security and reduces the
manual work. The existing system in police station has several disadvantages and many more difficulties
to work well. The proposed system tries to eliminate or reduce these difficulties up to some extent. The
proposed system helps the police station employees to work user friendly.
The proposed system includes the following features:
Login for admin, investigative officer and front line officers
FIR registration
Investigation file management
FIR Management
manage reports
Manage list about most wanted criminals and missing persons
2.3.1 Purpose of the new system
The proposed system will provide
Greater efficiency for recording investigation file:Since the proposed system uses
database system, registering investigation files, and updating of progress files from the
database will be easy and also there will not be loose of data.
Security: since the proposed system requires verification of logon form, sensitive
information’s will not be accessed or modified by unauthorized users.
Better service: since the proposed system allows users to register FIR online without a need
of going to police station, there will be fast response for crimes. Users will also view all
posted information’s from anywhere.
Efficient retrieval of criminal files: since the proposed system record each and every
criminal file on the data base, retrieval of criminal files from the database at any time will be
a very easy process.
Efficient FIR management: in the proposed system polices can view and easily identify
whether the FIR is crime and report FIR in efficient and organized way.
Increase Operational Efficiency: The proposed system should help in reducing the
repetitive paperwork/records and making the back-office functions more efficient.
2.3.2Functional requirements
Functional Requirement no 1:
Input: FIR no, FIR Date, FIR Time , Information Type, Place of crime, Act for crime, Address of
victim, Name of Police, Received Time, Information Received, accused persons full name and address.
Processing: After inputting data validation checks on various fields is performed. On submission of the
information the record is stored on database
Output: If the submitted information is valid, and found in the database then the corresponding record
is displayed.
Functional Requirement No 2:
Introduction: manage staff
Processing: After entering the required information the various validation checks are performed. On
submission of the information the updating are made to the database.
Functional Requirement 3:
Input: none
Processing: On clicking the view button the system search for the specified database stored.
Output: if the specified database is stored then the posted information’s display.
Functional Requirement no 4:
Input:
Criminal’s personal details with – Criminal No., Criminal Name, Age, Occupation, Crime Type,
address, gender.
Victim’s information- victim name, occupation, age, gender, address, victims no, and case no
Witness information -witness name; witness no, occupation, gender, age, witness no, case no,
address and Resident ID with their witness word
Processing: validation checks are performed on the input data like
Functional Requirement no 5:
Introduction: Retrieve criminal files
Output: if the entered information is correct, the required information will be displayed.
Performance: the system should be responsibly fast in order to access the required crime information’s.
Security: The system must confidentially be controlled from being accessed by unauthorized users.
Virus scanning software should be installed to protect from viruses. Duplicate record must be discarded
by the administrator.
Maintenance: New additional features can be added if required and also the system components i.e.
memory, disk, drives shall be easily serviceable without much alteration in the code.
Use case Diagram Describe the functional behavior of the system as seen by the user.It is a sequence of
action that provides a measurable value to an actor another way to look at it is that a use case describes a
way to which a real world to interacts with the system.
An essential use case sometimes called a business the case is simplified, abstract, generalized use case
that captures the intention of the user in a technology and implementation independent manner.
In the proposed system a use case describes a sequence of action that provides a measurable
value to an actor and draw as a horizontal ellipse.
An actor is a person in the proposed system that plays a role in one or more interactions with the
system.
Relationships between actors of Debre Berhan police station crime file management system and use
cases exist whenever an actor is involved with.
Actor identification
The purpose of actor analysis is to identify all of the actors that interact with the system. An actor has a role in
that interacting with the system. The actors that interact with the system are:-
Administrator: administrator is who interact in the proposed system that has full control over
the system. After login to the system whose responsibility is manage staff (add, update and
inactive user), assign investigation team, and generate charge sheet.
Investigative officer: investigative officer is an employee who has a roll (account type) of
investigative officer in the system. Whose responsibility is manage investigation files (register
new case, update progress file, and post wanted criminals), and generate investigation report.
He/she can retrieve closed criminal files and view assigned team by login in to the system.
Front line officer: front line officer is a police whose responsibility is manage FIRs (view and
identify, delete, and post missing persons), and generate FIR report for administrator.
User: user in this system represents all communities who interact to the system in order to add
FIRs and view posting information’s.
Use-case identification
Identifying the activities that are mainly performed on the proposed system is the basic thing in
analyzing a new system. The following use cases have been identified from the system specification.
Login
Manage staff
View report
Manage FIRs
Add FIR
Use case diagrams graphically describe system behavior (use cases). These diagrams present a high
level view of how the system is used as viewed from an outsider’s (actor’s) perspective. From the
identified use cases and actors the use case diagram of Debre Berhan police station crime file
management system is shown below.
Br2: FIRs should get fast response as much as possible if and only if the FIR is crime case
Br4: The crime should be happened in Debre Berhan city or around the city, in order to start
investigation process.
Br8: National army staff military can’t ask by polices for his crime.
Br9: police officers should work for 24 hours to accept crime reports
Br10: In case of disagreements between husband and wife, the FIR should be submitted by him or
herself in order to get response from police.
Br11: Investigation officer cannot use force and other illegal methods to do their investigation.
Br12: Victims should qualify whatever asked by officer In order to record their case
Br13: since investigation processes completed, progress files should be recorded as closed criminal
cases.
Br14: Closed criminal cases should be recorded on the data base for only retrieval purpose.
Debre berhan police station crime file managment system
view posted
information
add FIR
user
investiga
tive manage include assign investigative
include Login officers front line
officer investigation
officer admin
file
add new
user
delete
register new
case
include
view report
Figure 2.1: use case diagram for Debre Berhan police station management system
Name: Login
UC_ID: UC_01
Actor: administrator, front line officer, and investigative officer
Description: this use case is used to ensure security in system usage.
Precondition: the user must have at least username and password.
Post condition: the user get access to the system according to their predefined system privilege and
finally he/she logout or turn off the page.
step6:the investigative officer enters all the step8:The system display victims information
requested information form
step7:The investigative officer clickon the next step11: the system display witness information
button form
step9:the investigative officer enters all the step14: The system will check the filled
requested victims information form
step10:the investigative officer click on the next step15: The system will save the form on
button database
step12: the investigative officer enters all the step16:The system will display successful
requested witness information register message
step 13: the investigative officer clicks on the step17: the system ends
register button
Alternative course of action:
5.1:if the case id is already existed, the system will display ‘case id is exist please add another’
5.2: the system displays empty text field.
5.3:if the investigative officer clicks on the registration button, the system will check the filled form,
save the form on the data base, display successful message and display the next form.
16.1: If the investigative officer left blank the text boxes that are mandatory to be filled by him/her then
the system will display a fill again message and allow him/her to fill again.
16.2:if the detective police fill error info the system display empty form again
If the user clicks the reset button then the basic flow begins
11.1: if the investigative officer select the no option, the system displays ‘updating aborted’
message.
5.1: the system doesn’t save the new account to the system database
5.2: it displays a fill again message.
About inactivate the account:
7.1: if the file doesn’t exist in the database the system displays ‘there is no criminal file record in
this name’ message
7.2: use case ends
Step 2: The system should validate the user by checking user name and password.
Post conditions: If investigative officer valid user name and password then he/she can post the
information.
Step 2: The system should validate the user by checking user name and password.
Post conditions: If a Police officer entered valid user name and password then he/she can post the
information.
Name: logout
UC_ID: UC_12
Actor: administrator, investigative officer and polices
Description: this use case allows to logout and back to the login page
Preconditions: the administrator, detective police and the police should be login to the system and
wants to log out
Post conditions: the administrator, investigative officer, and polices logged out from their privileges
and go back to home page.
2.4.2Dynamic models
In order to login to the system the admin, investigative officer and police browses the system and view
home page. Then he/she enters user name, password and user type to login form and click on login
button. If the entered information is valid, he/she views available page that can be displayed based on
their user type, unless he/she views try again message and home page.
Figure 2.3: activity diagram for register new case
An investigative officer first browses the system and view the home page. Then the officer fills the
displayed login form and clicks login button. If the login information is invalid, the system displays
home page again, otherwise main menu displays. Then investigative officer selects on manage
investigation file and click register new. Then investigative officer fills displayed victims, witness and
criminals form, thenthe system checks whether the filled information is correct. If it is correct,
successful message will display otherwise main menu page displays.
Figure 2.4: activity diagram for posting safety tips and missing persons
In order to post missing persons and safety tips, the front line officer browses the system and view home
page. Then he/ she fill the login form. If the entered information is in valid, the home page will be
displayed and he/she tries to login again, else he/she views front line page and select post button. Then
he/she select the post information type either safety tips or missing persons. After this the front line
officer fills necessary information’s requested by the form then clicks on post button. If the entered
information is correct, displays successful message. Otherwise police officer views unsuccessful
message and police officer page.
Figure 2.5: activity diagram for generate charge sheet
In order to generate charge sheet, the administrator browses the system and fill login form. If the entered
information is invalid, the home page will be displayed and he/she tries to login again, else he/she views
administrator page and select charge sheet button then the admin fills the charge sheet form. Then the
admin clicks on submit button. If the entered information is incorrect, he/she views empty charge sheet
form else he/she views successful message.
Figure 2.6: activity diagram for view report
Since the administrator is the only privileged person to view reports, he/she browses the system and fills
login form. If the login information is invalid, the home page will be displayed and he/she tries to login
again. Unless admin can view admin page will be displayed. Then admin clicks on view report button
and select and view report type either investigation report prepared by investigative officer or FIR report
prepared by police officers.
post wanted criminal
Uc # 07
Actor: investigative officer
select type
of user
fill username &
browse homepage password
click on
login button
invalid
valid
display
investigative
officer page
incorrect
correct display
successfull
message
In order to post want criminals information’s, investigative officers browses the system and fill login
form. If the filled information invalid, he/she views empty login form else investigative officer views
investigative officer page. Then investigative officer click post button and fill wanted criminals form
and clicks on post button. If the entered information is incorrect, he/she views empty form, else view
successful message.
Figure 2.8: activity diagram for add new use
In order to add new user the administrator browses the system and view home page. After inserting the
login information on login form, administrator clicks login button and the system validates login
information. If it is invalid, the home page will be displayed and he/she tries to login again. Unlessadmin
can view admin page, then he/she selects add new user button and enter new user information and clicks
on submit button. The system validates/ checks whether the new information is correct. If it is correct
the system displays successful message else admin page displayed again.
Figure 2.9: activity diagram for update user
In order to update user account administrator should perform the above activities. First he/she browses
the system and view home page. Administrator fills login form and clicks login button then the system
validates entered information. If it is invalid, the home page will be displayed and he/she tries to login
again, else admin can view administrator page. He/she selects manage staff and update user then enters
user detail. If it is not found, admin page displays again unless he/she enters the needed information and
clicks update button. If the entered information correct, successful message displayed. Otherwise admin
page displayed again.
Figure 2.10: activity diagram for inactive user
In order to inactive user account administrator first browses the system and fills login form. If the login
information is invalid, the home page will be displayed and he/she tries to login again. Unless admin
view administrator page will display. Then admin clicks on manage staff and select inactive user. Then
she/he enters user detail. If the user detail not found on the database, unsuccessful message will
displayed unless successful message will displayed.
Figure 2.11: activity diagram for retrieve closed files
The above diagram shows all the activities needed to retrieve criminal cases. First
administrator/investigative officer /front line officer browse the system and view home page. He/she fills
login information to login form and clicks on login button. If login information is invalid, the home page
will be displayed and he/she tries to login again. Otherwise available page will be displayed. in order to
retrieve crime cases he/she have to click retrieve info button and fills needed criminalname, then clicks
on search button. The system then checks whether the needed file exist in the database. If it is found, the
system displays case information unless displays unsuccessful message and available main page
displayed again.
Sequence diagram describe behavior as a sequence of messages exchanged among a set of objects.
Sequence diagram which is also known as interaction diagrams are one of the diagrams seed in UML,
for modeling the dynamic aspects of the system. It shows an interaction consisting of a set of objects and
their relationship including message that may be dispatched among them. It emphasizes the time
ordering of messages. A sequence diagram shows an interaction arranged in time sequence. In
particular, it shows the instances participating in the interaction by their “lifelines” and the stimuli that
they exchange arranged in time sequence. It does not show the associations among the objects. Sequence
diagrams are used to display the interaction between users, screens, objects and entities within the
system. It provides a sequential map of message passing between objects over time( Sumi Thomas
PainumkaL - March 2009 ).
Login
UC# 01 Main Login Login Login Database
: administrator/investigative
window link form controller
officer/ police
1: activate UI()
1:he/she select
retrival case link()
2: the system Send 1: select retrival case link()
message to search
2: Send message()
page()
3:the system
Displays search
page() 3: display search page()
4:he/she Enters
requested
4: Enter requested information()
information ()
5:he/she Clicks on
search button() 5: Click search button()
6: the system
sends message to 6: send message()
case retrival
controler()
7: chek to database()
7: the system
checks to
database()
8: check() 8: check()
9:the system
responce message
9: send message()
to case retrival
controler
10: the system 10: Display not found message()
Displays not found
message() 11: Display requested information()
11: the system
displays
requested
information()
14:validate()
16:update database()
17:check()
13:check()
14:Display response()
13: check ()
8: add to database ()
9: check ()
The UML Collaboration diagram is used to model how objects involved in a scenario interact, with each
object instantiating a particular class in the system. Objects are connected by links, each link
representing an instance of an association between the respective classes involved. The link shows
messages sent between the objects, and the type of message passed ( Sumi Thomas PainumkaL -
March 2009).
: User
9: Check()
8:Continue()
4: Fill The Username and Password() 6:
Validate()
2: 2: Send message()
11: 11: Display requested information()
8: 8: check()
Data
base
View retrive
case link
6: 6: validate () 9: 9: check ()
View posted
info link
6: 6: send message()
3: 3:transfer message()
5: 5:check()
: Investigative
officer/ police
14: 14: Display response ()
6: 6: display form ()
Data
base
7: 7: fill display report form () 11: 11: display fill again message ()
8: 8: click report button ()
5: 5: send message ()
Datab
ase
7: 7:fetch() Data
Report
controller base
:
administrator
2: 2: send message ()
Update
user link
9: 9: update data ()
Update User Data
controller base
Figure 2.33: State chart diagram for post missing persons and safety tips criminals
Figure 2.34: State chart diagram for register new crime case
CHAPTER THREE
SYSTEM DESIGN
3.1 Introduction
System design is the transformation of the analysis model into a system design model. System design is
the first part to get into the solution domain in a software development. This chapter focuses on
transforming the analysis model into the design model that takes into account the non-functional
requirements and constraints described in the problem of the statement and requirement analysis
sections discussed earlier.
The purpose of designing is to show the direction how the system is built and to obtain clear and enough
information needed to drive the actual implementation of the system. It is based on understanding of the
model the software built on. The objectives of design are to model the system with high quality.
Implementing of high quality system depend on the nature of design created by the designer. If one
wants to change to the system after it has been put in to operation depends on the quality of the system
design. So if the system is design clearly, it will be easy to make changes to it.
Design goals describe the qualities of the system that the developers should consider.
Login
This includes admin, investigative officer and police login. There will be account type, user name and
password to login into the system to use all the facilities.
Manage staff
This module helps the admin to add new user accounts, update and inactive existed account.
This module helps the admin, investigative officers and police to view the details of closed crime cases.
FIR management
This module helps polices to view, identify and organize FIRs and users to add FIRs.
This module helps investigative officers and polices to post wanted persons, and missing persons and
hot news with safety tips respectively. This module also helps users to view posted information’s.
This module helps the investigative officers to register new criminal files and to update progress files if
necessary. Witness information’s, criminal information detail and witness’s information’s are registered
in this module.
Generate report
This module helps the investigative officers to prepare investigation reports and polices to prepare FIR
reports.
View report
This module helps the admin to view both FIR and investigation reports.
3.4 Component diagram
By this Diagram, components of the system will be wired showing that there is relation among
components; management of the system, database and operations performed on databases such security
issue. This in some extent shows which component or objects will be accessed by whom and what type
of security infrastructures it is using Aniekwe Vivian Nkiruka - August, 2012. The component
diagram of Debre Berhan police station crime file management system is displayed below.
manage
staff
generate
chargesh
eet
view
report
Administr manage
ator investigat
ion file
generate
Investiga report
tive
officer retrieve security
closed
file
frontline post
officer wanted
person database
post
missing
user person
manage
fir
view
posted
info
add fir
Figure 3.2: component diagram for Debre Berhan police station crime file management system
3.5 deployment diagram
Deployment diagrams model the physical architecture of a system, and it shows the relationships
between the software and hardware components in the system and the physical distribution of the
processing Aniekwe Vivian Nkiruka - August, 2012.
HTTP Application
request sever SQL
Client Databse
browser User server
controller
Report
Administrator Security
controler
login
controler
Investigative
officer Persistance
progress
file
controler
front line
officer post
controler
User
database
FIR
controler
new case
controler
case
retrival
HTTP controler
response
Figure 3.3: deployment diagram for Debre Berhan police station crime file management system
3.6 user interface prototyping design
Figure 3.5: Class diagram design for Debre Berhan police station crime file management system
3.8 Data base design
Database design is the process of producing a detailed data model of a database. This logical data model
contains all the needed logical and physical design choices and physical storage parameters needed to
generate a design in a Data Definition Language, which can then be used to create a database. A fully
attributed data model contains detailed attributes for each entity. The term database design can be used
to describe many different parts of the design of an overall database system. Principally, and most
correctly, it can be thought of as the logical design of the base data structures used to store the
dataAniekwe Vivian Nkiruka - August, 2012.
Figure 3.6: database design for Debre Berhan police station crime file management system
CHAPTER FOUR
IMPLEMENTATION DELIVERABLE OF THE NEW SYSTEM
4.1Introduction
Implementation is an understanding of a technical specification or algorithm as a program, software
Login page: This form appears on the site in which the system deployed is opened and contains some
links which lead the user to other page according to his/her privilege, and if the user is authorized user or
has an account, he/she will directly go to the page that he/she wants by entering correct category, User
ID and password.
Fig: 4.3: User Interface Design for staff login
+
Fig: 4.3: User Interface Design for user profile edit
Fig: 4.3: User Interface Design for new case
Fig: 4.3: User Interface Design for progress case
Fig: 4.3: User Interface Design for new fir report
Fig: 4.3: User Interface Design for registor staff
Fig: 4.3: User Interface Design for send and view report
Fig: 4.3: User Interface Design for add witness profile
Fig: 4.3: User Interface Design for view missing person
Fig: 4.3: User Interface Design for user profile edit
Fig: 4.1: User Interface Design for post wanted criminals
CHAPTER FIVE
PROTOTYPE DEVELOPMENT
Prototype development can be defined that it is the sample code of the given project. These are some of the
sample codes that we have done it.
<?php
error_reporting(0);
include('config.php')
?>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Members Area</title>
</head>
<body>
<div class="header">
<div>
<ul>
<li>
<ahref="index.php"><span>H</span>ome</a>
</li>
<li>
<ahref="about.php"><span>A</span>bout</a>
</li>
<li>
<ahref="programs.php"><span>P</span>rograms</a>
</li>
<li>
<ahref="blog.php"><span>B</span>log</a>
</li>
<li>
<ahref="staff.php"><span>S</span>taff</a>
</li>
<li>
<ahref="contact.php"><span>C</span>ontact</a>
</li>
</ul>
<div>
<p>
</p>
</div>
</div>
</div>
<div class="body">
<div>
<div>
<div>
<div class="programs">
<div class="first">
<table><tr><td><imgsrc="p.png"></td><td><h3>WELCOME</h3><?php
if(isset($_SESSION['username'])){echo ' '.htmlentities($_SESSION['username'], ENT_QUOTES, 'UTF-8');} ?
></td></tr></table>
<?php
if(isset($_SESSION['username']))
$nb_new_pm = $nb_new_pm['nb_new_pm'];
?>
<ul> <li><li>
<a href="edit_infos.php">PROFILE</a>
</li>
<li>
</li>
<li>
</li><li>
<a href="miss.php">MISSING
PERSONS</a>
</li>
<li>
</li>
</ul>
</div>
<div>
<?php
$ctrl = $_REQUEST['key'];
?>
<table>
<tr>
<th>Id</th>
<th>Username</th>
<th>cases</th>
<th>hold</th>
</tr>
<?php
while($dnn = mysql_fetch_array($req))
?>
<?php
$ende = $dnn['username'];
$dan = mysql_num_rows($hab);
?>
<tr>
</tr>
</table>
<?php
}}
?>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="footer">
<div>
</div>
</body>
</html>
include('config.php')
?>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Members Area</title>
</head>
<body>
<div class="header">
<div>
<ul>
<li>
<ahref="index.php"><span>H</span>ome</a>
</li>
<li>
<ahref="about.php"><span>A</span>bout</a>
</li>
<li>
<ahref="programs.php"><span>P</span>rograms</a>
</li>
<li>
<ahref="blog.php"><span>B</span>log</a>
</li>
<li>
<ahref="staff.php"><span>S</span>taff</a>
</li>
<li>
<ahref="contact.php"><span>C</span>ontact</a>
</li>
</ul>
<div>
<p>
<span>crime</span></p>
</div>
</div>
</div>
<div class="body">
<div>
<div>
<div>
<div class="programs">
<div class="first">
<table><tr><td><imgsrc="p.png"></td><td><h3>WELCOME</h3><?php
if(isset($_SESSION['username'])){echo ' '.htmlentities($_SESSION['username'], ENT_QUOTES, 'UTF-8');} ?
></td></tr></table>
<?php
if(isset($_SESSION['userid']))
$fir = $fir['fir'];
?>
<?php
if(isset($_SESSION['username']))
$nb_new_pm = $nb_new_pm['nb_new_pm'];
?>
<ul> <li><li>
<a href="edit_infos.php">PROFILE</a>
</li>
<li>
</li>
<li>
</li><li>
<a href="viewfir.php">NEW FIR(<?php
echo $fir; ?> )</a>
</li><li>
<a href="miss.php">MISSING
PERSONS</a>
</li>
<li>
</li>
</ul>
</div>
<div>
<?php
$countreg=mysql_num_rows($reg);
echo"<center>";
echo"</center>";
echo"<br><br>";
<tr>
<td>FIR ID<td>
<td>VICTIM NAME</td>
<td>CRIME TIME</td>
<td>CRIME PLACE</td>
<td>View</td>
</tr>";
while($row = mysql_fetch_array($result))
$ctrl = $row['fir_id'];
print ("<tr>");
print ("</tr>");
print( "</table>");
?>
<?php
}}
?>
<table>
<tr>
</tr>
<br><br><br>
<tr>
</tr>
</table>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="footer">
<div>
</div>
</body>
</html>
CHAPTER SIX
6.1 Conclusion
Crime File Management System allows police department to store department’s case details, Complaint
Details, FIR Details, etc. This Software Package allows Police Departments to store all the details
related to the department and use them whenever necessary. This project will also be able to provide
reports of various cases, FIR report, charge sheet report, and progress file report , and also be able to
upload and view wanted criminals, missing persons and hot news. The implementation of the system in
the organization will considerably reduce manual data entry, time and also provide readily calculated
reports.
6.2 Recommendation
The proposed system that we are trying to develop involves only automate investigation/criminal files
that are managed in police station. But there are still areas that may be considered as a further and
important area to improve on, and our suggestion go thus.
There is the need for the magistrate segments and prison record to be automated.
The development of DNA database stores criminal fingerprint
There is a need for human resource management records in police station to be automated
Therefore, others who are interested to develop a new system on police station file management system
or other related systems can get some initial idea about the system. By focusing on the limitation and
functional areas of the system they can also develop a better police station management system that
automates all files managed in police station.
APPENDEX
Symbol Description
Actor
System boundary
Decision
Use case
class
Deployment diagram
Reference
Arbaz Khan, MayankDangand Nikhil Pangarkar - November 17, 2012 - STUDYING CRIME
INCIDENTS FOR SAFETY ANALYSIS - Indian Institute of Technology, Kanpur,India
Sumit R. Farsole, Shreyas B. Kene, Prof. V. V. Bhujade -March 2014- E-POLICE POLICE
RECORD MANAGEMENT SYSTEM -Wardha, India.
SomdevAryA - CRIME FILE PROJECT REPORT - School of Information Technology GGS
Indraprastha University, Delhi, India
Sumi Thomas PainumkaL - March 2009 - CRIME MANAGEMENT AND REPORTING SYSTEM
- Cochin University of Science and Technology