Debre Berhan Crime File Management System

Debre Berhan crime file management system 2007
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
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
6.1 Conclusion....................................................................................................................................................97
6.2 Recommendation.........................................................................................................................................97
Reference...........................................................................................................................................................97
LIST OF TABLES
Table 1.1: Time Schedule for Our Project …………………………………………………….…6
Table 2.1: Class Responsibility and collaboration ………………………….………….………....12
Table2.2: Main Course of Action about Login….………………………..……………….……..21
Table 2.3:Main Course of Action about register new case….……………...…….…22
Table 2.4: Main Course of Action about update progress cases….............................23
Table 2.5: Main Course of Action about Add New User Account………….….……..24
Table 2.6: Main Course of Action about Update Account …………………………....25
Table 2.7: Main Course of Action about Inactivate Account …………….……….….25
Table 2.8: Main Course of Action about retrieve info ………………………………….26
Table 2.9: Main Course of Action about View Report……………………….……..…..27
Table 2.10: use case about generate report..………………...……………………..……28
Table 2.11: use case description about generate investigation report...……...…… 28
Table 2.12: Main Course of Action about post wanted criminals……………………29
Table 2.13: Main Course of Action about posting missing persons …………...……30
iii
Table 2.14:main course of action about view posted information’s…………...……31
Table 2.15: main course of action about manage FIR...………………………….…… 31
Table 2.16: main course of action about add FIR ………………………………………32
Table 2.17: main course of action about assign investigation team ……..…………33
Table 2.18:main course of action about logout ……………………………………...…34
LIST OF FIGURES
Figure 2.1: usecase diagram for Debre Berhan police station management
system…………………………………………………………………………………20
Figure 2.2: activity diagram for login ……………..……………………………...……..…….35
Figure 2.3: activity diagram for register new case …………………………………..….….36
Figure 2.4: activity diagram for posting safety tips and missing persons ….…….…..37
Figure 2.7: activity diagram for view report ……………….………………………..……….40
Figure 2.8: activity diagram for post wanted criminals …………………………..……….41
Figure 2.9: activity diagram for add new use ……………………………………………….42
Figure 2.10: activity diagram for generate investigation report………….………..….…43
Figure 2.11: activity diagram for manage staff………………………………………...……44
Figure 2.13: activity diagram for retrieve criminal case…………………..……….……...46
Figure 2.14: sequence diagram for login ………………………………..................................48
Figure 2.16: sequence diagram for retrieve crime case …………………….…….……….50
Figure 2.17: sequence diagram for view report ……….…………………………...….…….51
Figure 2.18: sequence diagram for manage FIR…….……………………….…..………....52
iv
Figure 2.19: sequence diagram for register new crime case ………………………..……53
Figure 2.20: sequence diagram for update user………………………………….…………54
Figure 2.21: sequence diagram for update progress file ………………………………….56
Figure 2.22: sequence diagram for add FIR ……………………………………..….……….58
Figure 2.23: sequence diagram for posting …………………………………….…………….60
Figure 2.25sequence diagram for add user………………………………………………….62
Figure 2.26: collaboration diagram for login …………………………………………...……63
Figure 2.27: collaboration diagram for retrieve case……………………………………….64
Figure 2.28:collaboration diagram for add user …………………………………………...65
Figure 2.29: collaboration diagram for view posted information’s………………...……65
Figure 2.30: collaboration diagram for view FIR…….……………………………...……....66
Figure 2.31: collaboration diagram for posting …………………………….………….…....67
Figure 2.32: collaboration diagram for update progress file ……………….…………….68
Figure 2.33: collaboration diagram for register new crime case ………………………...69
Figure 2.34: collaboration diagram for view report ……………………………….……….71
Figure 2.35: collaboration diagram for update user…………………………….…..……..72
Figure 2.36: collaboration diagram for add FIR………......……………………...….……..73
Figure 2.37:State chart diagram for login ……………………………………….…….……74
Figure 2.38: State chart diagram for view report …………………………………………..75
Figure 2.39: State chart diagram for add new user ……………….……………..………75
Figure 2.40: State chart diagram for generate investigation report …......……………..76
v
Figure 2.41: State chart diagram for generate FIR report..…..... …………………….….77
Figure 2.42: State chart diagram for post wanted criminals……............….....................78
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.45: State chart diagram for update progress file….…………..........……………79
Figure 2.46: State chart diagram for view posted information.…......................................80
Figure 2.47: class diagram for Debre Berhan police station crime file
management……………………………………………………………………………….….81
Figure 3.1: system decomposition diagram………………………………………….………….68
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.3: user interface prototyping design ………………………………..……….………………...72
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
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
viii
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
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.2 Background of the organization

In Debre Berhan town there were security departments in order to prevent crimes. In 1934 Debre Berhan
police station was established newly as a police force. Its mission was keeping humans life, there asset
as well as their money from criminals. Debre Berhan police station has been used manual file handling
system since it was established. There were four big departments under the station that were detection
department, prevention department, traffic department and HRM department.
1.3 Problem of the statement

As the existing system uses manual system there are a lot of problems like:
 All criminal information’s are paper based which is cumbersome to maintain

 Time consuming
 Requires lots of manual work
 The existing system doesn’t have system security
 Retrieval of data in a desired way is so difficult
 Data redundancy and inconsistency
 There is a Work load over police departments since investigation reports and investigation files
are manually operated
 Transferring neat investigation files from generation to generation is so difficult because of
improper record
 Difficult to manage the overall system
 The files are vulnerable for some kind of corruption
 Hard to generate report
 Unproductive use of storage space
1.4 Objectives of the project

1.4.1 General objectives
The general objective of this project is to develop crime file management system for Debre Berhan police station.
1.4.2 Specific objective

The specific objectives of the Debre Berhan crime file management system development are:
 Identify the problem in the current system
 Suggest alternative solutions in order to address the current problem
 Understand functional and non-functional requirements of the system
 Design the user interface
 Confirm secure data flow in the station
 Develop a system that make retrieval of data efficient
 Develop a system that facilitates fast report generation
 Develop a system that enable the user to report crimes online
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.
Secondary Techniques: Document Analysis
This technique provides information on how the existing system works .There for we have analyzed
different forms in current manual system.
1.5.2 System Analysis and Design Techniques

In this project, our team will use object oriented system development methodology (OOSD) for the
design this technique has several phases some of them are:
I. Object Oriented Analysis (OOA)
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.
II. Object Oriented Design (OOD)
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:-
 To simplify the design and implementation of complex program.

 To make it easier for teams to work in a single software project.
 To enable a high degree of reusability of designs.
 To decrease the cost of software maintenance.
 Reduce maintenance burden.
 Increased consistency among analysis, design and programming activities.
 Improved communication among users, analysis, design and programming.
1.5.3 Tools used
Different hardware’s were used to develop our project.
Hardware requirements:
 Computer: we used a computer which was operating system of Window7.
 Flashdisk: we usedflash disk when we move our data from one machine to another.
 Mouse, key board and monitor: was used for inputting and outputting of data.
 External hard disk: was used to store our project data.
Software requirements:
 Database: Microsoft SQL server 2008
 MS word 2010: was used to type our project work.
 Rational Rose ,Visual paradigm, Edrow: was used for UML standard design:
 Front end: HTML
 Back end:
My SQL:- we used this software to create the database of the project.
NOTEPAD++, Dreamweaver: - we used this software to write our PHP and HTML
codes.
JavaScript: - we used this software to validate our data.
1.6 Feasibility study

1.6.1. Technical feasibility
We have enough capability and technical knowledge about:
 PHP to write the code or implementation with XAMPP.
 MySQL to build the database to store the data.
 Requirement analysis to know the stockholders constraint for their satisfaction
 Unified Modeling Language (UML) model to do analyzing and designing in good
manner.So the system will be technically feasible.
1.6.2. Economic Feasibility

 Economic analysis is the most frequently used method for comparing the cost with the benefit or
income that is expected from developed system.
 In the existing system, many people are involved in the process but in the proposed system,
number of persons involved be reduced drastically. So the proposed system is economic.
 In the existing system, there is a person whose responsibility is to manage closed criminals files.
In proposed system, this occupation is not necessary since criminal information’s are recorded to
and retrieved from database.
 In the existing system, storage of all criminal file records should be arranged in a large space and
security should be provided for the records. In the proposed system, separate security
arrangement and physical storage space is not needed since the new system uses database and
provides security.
1.6.3 Operational Feasibility

It determines how the proposed system will satisfy the organizations need and it also offers Secure,
accurate and efficient system to the organization.
The system in which we are developing is also compatible to all operating systems and web browsers.
So our proposed system is operational feasible.
1.6.4 Political feasibility

The proposed system will implement as one of governmental institutions, the system to be developed is
not conflict with any government directives, rules and regulations. So, the government is profitable and
the system will be politically feasible.
1.6.5 Behavioral feasibility

The project would be beneficial because it satisfies the objectives when Developed and installed. All
behavioral aspects are considered carefully and conclude that the project is behaviorally feasible.
1.6.6 Schedule Feasibility

We have identified the activities of the project in order to accomplish the project objective within the
time duration which is on the table below.
Table 1.1: Time schedule for our Project

1.
7 scope of the project
The proposed system focused on Debre Berhan police station and covers only the management of crime
files in the station.
1.8 Significance of the project

The significance of the new system includes:
1.8.1 Benefits to police station

 Avoiding improper resource consumption like paper, pen, ledger…
 Avoiding data loss because of improper data storage
 Neat investigation files in the station can be transfers from generation to generation
 Enhance security mechanisms to protect crime records
1.8.2 Benefits to Citizens

 Multiple channels to access services from police
 Simplified process for registering and tracking FIRs
 Simplified process for registering grievances against police
 Can view posted information’s by the station anywhere at any time
 Faster and assured response from police to any emergency calls for assistance
1.8.3 Benefits to Police Department

 Enhanced tools for investigation
 Facilitates fast and efficient retrieval of data
 Can post wanted criminals, missing persons and safety tips anywhere at any time
 Centralized crime and criminal information repository
 Reduced workload of the police station back-office activities such as preparation of regularand
ad-hoc reports and station records management
 Simplified process for tracking the progress of the case during trials
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.
2.2 Existing system description

In the existing system of Debre Berhan police station, the police department accepts FIRs in three ways
that are by phone, by letter and by face to face. For these purpose there are polices placed at the station
for 24 hours. After accepting FIRs, the police identifies whether the FIR is crime or not. If it is crime,
the FIR will send to the police officer and investigation team will be organized. This investigation team
list announces to investigative officers with FIRs, and then the investigation process starts. After
completed investigation process, the progress files closed and recorded by the person who is hired for
this purpose. Debre Berhan police station manages all FIRs and investigation files by writing all
information on ledge. In case of this manual system Debre Berhan police station cant accomplished its
mission in a manner of efficiency.
2.2.1 Drawbacks of Existing System

 The existing system is time consuming and not very user friendly.
 The existing system Consumes large volume of paper work
 The existing system doesn’t have system security
 Because of the large number of serious crimes, minor FIRs may be ignored.
 Retrieval of data in a desired way is difficult
 The existing system has work load for police department
 The existing system does not maintain most wanted criminals with respect to area wise and
age wise also.
 In the existing system generation of report is bulky activity
 The existing system does not support online case registrations
To avoid all these limitations and make the working more accurately the systems needs to be
computerized.
2.2.2 Explanation of the business rule of the organization
A business rule of existing system is successfully an operating standard or policies that will explain for
existing system of Debre Berhan police station.
The existing system has many business rules or principles some of them are:
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
Br3: FIR crimes should be investigated by investigation officer.
Br4: The crime should be happened in Debre Berhan city or around the city, in order to start
investigation process.
Br5: accused persons have been taken to court within 48 hours.
Br6: Victims had right to report any crime
Br7: Police staff cannot arrest by suspect without court’s permission
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
2.2.3 CRC (class responsibility and collaboration)

CRC modeling techniques are used to model the existing system that helps to build the proposed class
diagram by observing how the existing systems are collaborate with each activity. A class represents a
collection of similar objects, a responsibility is something that a class knows or does, and a collaborator
is another class that a class interacts with to fulfill its responsibilities Sumi Thomas PainumkaL -
March 2009.
Table 2.1: class responsibility and collaboration
2.3 Proposed system description

The proposed crime file management system was designed in order to reduce the problems of the
existing system. In this proposed system, police officer will register as an admin and has a full control
over the system. So that he/she will create accounts for different polices based on their user type and
announce them there user name, password and privilege
Totally there will be three types of privilege on the system with administrator those are investigative
polices, and polices and also communities (users) are actors to the system.
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:
Introduction: manage FIR
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
Input: Username, password
Processing: After entering the required information the various validation checks are performed. On
submission of the information the updating are made to the database.
Administrator must enter the correct user name and password
Output: The updated information is reflected in the stored database.
Functional Requirement 3:
Introduction: Viewing posted information’s
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.
The data displayed is updated and accurate information.
Introduction: manage investigation file
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
 mandatory fields should not be kept blank

 whether the filled information is error free
Output: if the entered information is correct, successful information’s will be displayed.
Introduction: Retrieve criminal files
Input: Case No, criminal name
Processing: validation checks are performed on the database
Output: if the entered information is correct, the required information will be displayed.
2.3.3 Nonfunctional requirements

Availability: the system should be available at any time, if by any means the system fails, the system
should store a backup database.
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.
2.4 System models and the artifacts

2.4.1 Use case diagram
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
 Manage investigation files
 View report
 Manage FIRs
 Post wanted criminals

 Post missing persons
 Add FIR
 View posted information’s
 Retrieve criminal cases
 View assigned team
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.
2.4.1.1 Business rule for proposed system

The business rules of the Debre Berhan police station crime file management system are listed as follow:-
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
Br3: FIR crimes should be investigated by investigation officer.
Br4: The crime should be happened in Debre Berhan city or around the city, in order to start
investigation process.
Br5: accused persons have been taken to court within 48 hours.
Br6: Victims had right to report any crime
Br7: Police staff cannot arrest by suspect without court’s permission
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
retrieve crime case

generate
investigation
report delete
include
view post missing

update person
case
manage FIR
investiga
tive manage include assign investigative
include Login officers front line
officer investigation
officer admin
file
add new
user
delete
register new
case
include
post wanted manage staff

criminals
view report
Figure 2.1: use case diagram for Debre Berhan police station management system
2.4.1.2 Use case description

It is a sequence event that describes what the proposed system will develop and how it interacts with the
environment mainly. This section describes the most important activates that the actors of DEBRE
BERHAN POLICE STATION CRIME FILE MANAGEMENT SYSTEM do experience to make use of
the 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.
Main course of action:
Table 2.2: Main Course of Action about Login
Actor action System response

Step1: Administrator, investigative officer Step2: The System responses by
or front line officer has to activate the displaying the login interface and allow the
system. user for the user name and password.
Step3: they select account type and fill his Step5: System verifies username and
or her username and password. Password.
Step4: he/she select login button. Step7: System displays its main window.
Step6: the User get authentication and Step8: Use case ends.
access the system.
Alternative course of action

If user enters wrong username and / or password
7.1: System displays “please reenter your correct user name and password”.
7.2: system display empty login form
7.3: use case ends.
Name: Manage investigation file

UC_ID: UC_02
Actor: investigative officer
Description: This use case is done by investigative officer while the investigation process
Preconditions: the investigative officer should have to login to the system.
Post conditions: If the use case was successful, the user information is added in the investigation file
database. Otherwise, the system state is unchanged.
About registering new cases
The investigative officer wants to register criminal info for the record in database
Table 2.3: Main Course of Action about register new case

Step1: the investigative officer clicks on register step2:The system will request to add case id
button step4:The system check the case id
Step3:The investigative officer add case id in the step5: the system opens criminals registration
txt field and click submit button form
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
About updating the progress case:
Table 2.4: Main Course of Action about update progress cases

Step1:the investigative officer open step2: The system will display search
step3: the investigative officer add the box
case id
step4: click on search button step5: The system will check the case id
step7: The investigative officer edits the step6: The system will display searched
form. result
step8: The user clicks on Update button.
step11: the investigative officer selects step9: The system checks the entered
the yes option information
step14: end of use case step10: The system sends message”
does u want to update?”
step12: The system updates the

information
step13: the system displays successful
message of updating
Alternate course action:

6.1: displays “try again” message.
6.2: the system will display empty search box
11.1: if the investigative officer select the no option, the system displays ‘updating aborted’
message.
11.2: use case ends

Name: Manage staff
UC_ID: UC_03
Actor: Administrator
Description: This use case is done by the Administrator when they need to add, updateand inactive the
user account.
Preconditions: The Administrator have to login to the system to manage staff.
Post conditions: The user information will be managed by administrator.
About adding new user account
The Administrator wants to add new user to the system
Table 2.5: Main Course of Action about Add New User Account

Step1: the administrator clicks on add user button step2:the system displays the form
Step3: the Administrator enters the new user name, Step5: the system validates the new user detail.
account type, Password and reenter password to the Step6: the system save the user detail to the
system database.
Step 4: the Administrator submits the new user step7:the system displays successful message
information. of adding new user
Step7:the Administrator tells the category, user name Step8:the system ends
and password to the user
3.1: If the Administrator does not enter the username or the password or he/she entered which does not
match correctly, the system displays a message “please enters the user name and password correctly”.
5.1: if not correct the system doesn’t save the entered information to the database.
6.1: the system displays a fill again message and allow him/her to fill again.
6.2: use case ends
About updating an account:

Table 2.6: Main Course of Action about Update Account

Step1: the Administrator wants to update an Step4: the system checks the new account
account and he/she login to the system. information with the existing account in the
Step2: the Administrator inserts account _type, database.
username, password, and other user Step5: the system save the new account to the
information. database.
Step3: the administrator submits the data. Step6: the updating process ends
Alternate course action:
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:
Table 2.7: Main Course of Action about Inactivate Account

Step1: the administrator wants to inactivate the step3:The system display a form
account and he/she login to the system. Step5: the system checks the entered
Step2: the administrator selects the inactivate information with the existing account in the
button. database
Step4:the administrator enters the account type Step6: the system sends message “Do you
and username of the user want to inactive?” to the administrator
Step7: the administrator selects the yes option. Step8: the system inactivated the account from
the system.
Step 9 the use case ends
Alternate course of action:
5.1: the system displays try again message.

5.2:the system displays empty form
7.1: the system ends if he/she selects no.
Name: retrieve crime case

UC_ID: UC_04
Actor: Administrator, investigative officer and front line officers
Description: This use case is done by the Administrator, investigative officer and front line officer
when they need to retrieve criminal cases.
Preconditions: The Administrator login to the system to manage staff.
Post conditions: The user information will be managed.
Table 2.8: Main Course of Action about retrieve info

Step 1: Administrator /investigative officer Step3:The system requests the user to enter
/front line officers Criminal name or/and address and/or gender
Want to retrieve criminal cases and he/she
login to the system. Step 6: the system checks whether the file
Step2:the user on retrieve case button exist in the database
Step4: the user provides the requested Step7: the system displays the needed
information criminal info.
Step5: the user clicks on search button Step 9: the process end
Step 8: the user will see the displayed
information.
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
Name: View Report

UC_ID: UC_05
Actor: Administrator, front line officer and investigative officer
Description: This use case is seen by administrator; front line officer and investigative officer when
he/she want to view about the progress file report, and fir/complement report.
Preconditions: The administrator has to login to the system and the reports have already been in
database.
Post conditions: the administrator views a report.
Table 2.9: Main Course of Action about View Report

Step 1: the administrator wants to view the
report and clicks on view reports menu Step3: the system displays the selected report
Step2: The administrator selects a report type automatically.
on menu item. Step 4: the report process end
Alternative course action:

3.1: the system does not display the report.
3.2: the report process ends
Name: generate investigation report

UC_ID: UC_07
Description: This use case Generates investigation report
Preconditions: The investigative officer have to login to the system.
Post conditions: investigative officer generate report.
Table 2.10: use case description about generate investigation report

Step 1: the investigative officer clicks on step2: The system display report form
generate report button that contain the following :-
Step3:investigative officer fills the form  Date of report
 Type of report
step4:investigative officer clicks on
 For whom the report is prepares
generate report button
 Report information’s
step5:The system checks the filled form
Step 8: the report process ends
step6: The system generated the report
to the selected user.
step7:the system displays successful

message

5.1: If the investigative officer enters invalid information then the system will generate an error message
in order to fill again the information properly.
5.2: use case ends
Name: post wanted criminals

UC_ID: UC_07
Description: in this use case investigative officer can post wanted criminals.
Preconditions:
Step 1: investigative officer should have to enter a valid user name and password to upload wanted
criminals information.
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.
Table 2.11: Main Course of Action about post wanted criminals

Step 1:investigative officer wants to post the Step2: the system displays the wanted
information and clicks on post button criminals form
Step3:the police fill the needed information Step5: The system checks the filled form
Step6: the system stored the posted
Step8: the posting process end information on the database
Step7: the system displays successful message

7.1:the system display an error message
7.2: posting process ends
Name: post missing persons

UC_ID: UC_07
Actor: front line officer
Description: in this use case the front line officer can post missing persons.
Preconditions:
Step 1: front line officer should have to enter a valid user name and password to upload missing
persons.
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.
Table 2.12: Main Course of Action about posting missing persons

Step 1: the Police officer wants to post missing Step2: the system displays the missing person
persons and clicks on post button form
Step3: Police officer fills the needed Step4: The system checks the filled form
information Step5: the system stored the posted
information on the database
Step7: the report process ends Step6: the system displays successful message

6.1: the system display an error message
6.2: the report process ends
Name: view posted information’s

UC_ID: UC_08
Actor: user
Description: this use case allows the user to see posted information’s
Preconditions: there should be posted information’s
Post conditions: the user views posted information’s
Table 2.13: main course of action about view posted information’s
Step 1:the user wants to view the posted
information’s Step4:The system displays posted
step2:the user gets access to the system information’s
Step3:clicks on view post info button
step5: the user view posted
information’s
Step 6: the report process ends
Name: manage FIR

UC_ID: UC_09
Actor: front line officer
Description: this use case allows the front line officer to view and identify
Preconditions: the FIR should be registered in the data base and the police should be login to the system
Post conditions: the police views and identifies crime FIRs.
Table 2.14: main course of action about manage FIR

Step 1:the front line officer want to
manage the FIR Step3: The system displays the FIR
Step2: the front line officer clicks FIR page
button Step6: the system posts the crime case on
step4: the front line officer view the FIR
and identify which is a crime the admin page
step5:the police select and organize new Step7: displays the successful message
crime cases and sends to the admin Step8: the use case ends
Step4: if there is no crime report, the use case ends
Name: add FIR
UC_ID: UC_10
Actor: user, front line officer, investigative officer, administrator
Description: this use case allows the user to add FIR on the system
Preconditions: the user should have to get access to the system
Post conditions: the user adds FIRS to the system.
Table2.15: main course of action about add FIR

Step 1:user, front line officer, investigative
officer, administrator Step3: The system displays the FIR
Step2:the user clicks on FIR button page
Step4: the user clicks on add button Step5: the system displays the FIR form
Step6: the user fill the form with FIR No
Step7: the user clicks submit button Step8: the system posts the FIR and
displays the successful message
Step9: the use case ends
7.1: if the user clicks cancel button, the use case ends
Name: assign investigative officer
UC_ID: UC_11
Actor: administrator
Description: this use case allow the admin to assign investigation team
Preconditions: the administrator should be login to the system and there should be crime cases
Post conditions: the administrator assigns investigation team for crime FIRs.
Table 2.16: main course of action about assign investigation team

Step 1:the administrator view the reported
FIR Step3: The system displays a page with
Step2: he/she clicks on assign group the name of detective polices
button Step5: the system posts the information
Step4:the admin select the detective that the detective police can see
polices and send the selected information Step7: the system displays the successful
with the crime report message
Step8: the use case ends
7.1: if there is an error, the system displays an error message
7.2: the use case ends
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.
Table 2.17: main course of action about logout

Step 1:The user click logout button
Step2: The system returns to login page
Step3: end use case
2.4.2Dynamic models
2.4.2.1 Activity diagram

Activity diagram is another important diagram in UML to describe dynamic aspects of the system.
Activity diagram is basically a flow chart to represent the flow form one activity to another
activity. The activity can be described as an operation of the system. So the control flow is drawn
from one operation to another. This flow can be sequential, branched or concurrent. Activity
diagrams deals with all type of flow control by using different elements like fork, join etc. The
purposes of activity diagram can be described as:
 Draw the activity flow of a system.
 Describe the sequence from one activity to another.
 Describe the parallel, branched and concurrent flow of the system.

Figure 2.2: activity diagram for login
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
select type
of user
fill username &
browse homepage password
click on
login button
invalid
valid
display
investigative
officer page
clicks on fill wanted click post

post criminal form button
incorrect
correct display
successfull
message
Figure 2.7: activity diagram for post wanted criminals
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.
2.4.2.2 Sequence diagram
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:actors activate 2: click on login link

user interface ()
2: actors click on 3: Display login form()
login link()
3: the system
Display login form()
4: select account type and fill username & pasword()
4: an acter select
his/her account
type and fill 5: click submit button()
username &
pasword()
6: send message()
5: ac actor clicks
on submit button()
6: the system 7: validate()
transfer message
from login form to
login controler() 8:display try again message()
7: the sytstem
validates account 9: Login to the system()
information by
login controller
8: if it is invalid,
try again message 10: check()
display()
9: if it is valid,
Login to the 11: response to login form()
system()
10: check()
11: response to
login form()
Figure 2.12: sequence diagram for login

Retrive
crime case View retrive Search case retrival Databas
UC# 04 case link page controller e
officer/ police
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()
Figure 2.13: sequence diagram for retrieve crime case

View report
UC# 05 View report Report type Report Database
:
link controller
adminstrator
1:select view report link()
1:the
administrator
selects view report 2: send message()
link()
2:the system send
message() 3:display report type()
3:the system
displays report
type()
4: the 4: select report type()
administrator
select report type()
5: the
administrator 5: click on view button()
clicks on view
button()
6:the system send 6:send message()
message to report
controller()
7:the system
fetchs the report 7:fetch()
from the database
()
8: the system
displays reports()
8: display reports()
Figure 2.13: sequence diagram for view report

Manage FIR
UC# 09 View FIR FIR page Administr Database Database
: Police
link ator page controler
1:select FIR link()
2:send message()
1:the police select FIR
link
2:the system send 3:display FIR page()
message to FIR page
3:the system displays
FIR page 4:view and identify FIR()
4:the police view FIR
and identify wheather it
is a crime
5:he/she organize crime 5: organize crime FIRs()
FIRs 6: send message()
6: the system send
message to database
controller
7:the system checks 7:check()
the data
8: if it is not
correct,system displays
8: not successful message()
not successful
message 9: add to database()
9: if it is correct, the
system adds the data to
database 10: check()
10: the system check
data in database()
11: the system sends 11: send message to admin page()
message to
administrator page()
12: the system displays 12: display successful message()
successful message()
Figure 2.14: sequence diagram for manage FIR

Update user
UC# 03 Update Update user Update User Database
: user link form controller
administrator
1: click update user link ()

1: administrator
select on update user
2: send message ()
link ()
2: send message to
update user form ()
3: the system display
update user form () 3: Display update user form ()
4: administrator fills
user information ()
5:an administrator 4: Edit user detail ()
Clicks on update
button ()
6: update user form
transfers the filled 5: Click update button ()
form into update user
controller() 6: send message ()
7: the system validate
the data ()
8: if it is not correct
it displays not 7: validate ()
succesful message ()
9: if he/she fills
correctly the system
updates a database () 8: display not successful message ()
10: the system checks
the data wheather it 9: update data ()
is updated correctly ()
11: the system
display response ()
10: check ()
11: display response ()
Figure 2.15: sequence diagram for update user

Update
progress file View update Search Progress Progress file Database
: Investigative
UC# 02 link box file controller
officer
1: select update link()
1: the investigative
officer select update 2: send message()
link()
2: the system send
3: display search box()
message to search
box()
3: the system display 4:fill case No()
search box()
4:investigative
officer fill case No() 5: click on search button()
5: he/she clicks on
search button()
6: send message()
6: the system send
case no to progress
file controler()
7: the system search 7: search from database()
from database()
8:the system check it
from database()
9:if the case no not 8:check()
exist, the system
displays not found
message()
10:if it is found, the 9:display not found message()
system send message
to progress file()
11:the system
display progress file() 10:send message()
12:investigative
officer Edits progress
file()
13:investigative
officer clicks on 11: display progress file()
update button()
14:the system
validate edited
information() 12:Edit progress file()
15:if it is invalid, the
system display not
sucessful message()
16:if it is valid the
system updates the 13:click update button()
database()
17:check()
18:check()
18:the system
displays succesful 13:send message()
message()
14:validate()
15:display not sucessful message()
16:update database()
17:check()
18:display succesful message()
Figure 2.16: sequence diagram for update progress file

Add FIR
UC# 10 View FIR FIR page FIR form FIR Database
: User
link controller
1:select FIR link()
1:the user select FIR 2: send message()

link()
2: the system send
message to FIR page()
3:the system display 3:Display FIR page()
FIR page()
4:the user click on add
FIR button() 4:click on add FIR button()
5:the system send
message to FIR form()
6:the system display 5:send message()
FIR form()
7: the user fills all the
neccessary
informations on the 6:Display FIR form()
form()
8:the user clicks on
add button() 7: fill all the neccessary informations()
9:the system transfers
information from FIR
form to FIR controler
10: the system check
8: click on add button()
the filled 9:send message()
informations()
11: if it is incorrect,
the system display fill
again message() 10:cheak()
12: if it is correct, the
information adds to
database()
13:check() 11:display fill again message()
14:the system displays
responce() 12: add to database()
13:check()
14:Display response()
Figure 2.17: sequence diagram for add FIR

Posting
Uc# 07 Post Post post Database
: Investigative View
post link type form contro...
officer/ police
1: select post link ()
1: he/she select post
link () 2: send message ()
2:the system send
message()
3: the system
Displays post type () 3: Display post type ()
4: he/ she select post
type() 4: select post type ()
5: the system send
message to post form 5: send message ()
()
6: the system 6: display form ()
displays form ()
7: he/she fill the
form () 7: fill the form ()
8: he/she clicks on
post button()
9: the system 8: click post button ()
transfers message ()
10: check ()
11: if it is incorrect 9: send message ()
display not
successful message()
12: if it is correct
,add to database () 10: check ()
13: check ()
14: the system
Displays response () 11: display not successful message ()
12: add to database ()
13: check ()
14: Display response ()
Figure 2.18: sequence diagram for posting

Add new user
UC# 03
Add user New user User Database
:
link form controller
administrator
1: click add user ()

1: administrator clicks on
add user button ()
2: the system displays add 2: display add new user form ()
new user form ()
3: the administrator Fill new
user information ()
4: administrator click on
add user button () 3: Fill new user information ()
5: the system send the
form information ()
6: the system validates
4: click on add user button ()
enterd data on the form ()
7: if it is invalid, the system
displays fill again message 5: send message ()
()
8:the system add the new
account to database ()
9: check () 6: validate ()
10:thesystem Displays
response ()
7: fill again message()
8: add to database ()
9: check ()
10: Display response to administrator ()
Figure 2.19: sequence diagram for add new user

2.4.2.3 Collaboration diagram
A collaboration diagram describes interactions among objects in terms of sequenced messages.
Collaboration diagrams represent a combination of information taken from class, sequence, and use case
diagrams describing both the static structure and dynamic behavior of a system.
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).
1:User Visit home page () 2: Select Login Link()

Home Login Link
Page
: User
9: Check()
3:Display The Login Form() 5: Submit()

Database
8:Continue()
4: Fill The Username and Password() 6:
Validate()
10: Display The Target Page()

Login Validator
Form
7: Try again()
Figure 2.20: collaboration diagram for login

case retrival
controller
officer/ police
4: 4: Enter requested informatio...
5: 5: Click search button()
6: 6: send message()
3: 3: display search page() 10: 10: Display not found message()
Search 7: 7: cheak to database()

page
1: 1: select retrival case link() 9: 9: send message()
2: 2: Send message()
11: 11: Display requested information()
8: 8: check()
Data
base
View retrive
case link
Figure 2.21: collaboration diagram for retrieve case
3: 3: Fill new user information ()

4: 4: click on add user button () New user
form
2: 2: display add new user form ()
:
administrator
1: 1: click add user ()
10: 10: Display response to administrator ()

7: 7: fill again message()
Add user 5: 5: send message ()
link
6: 6: validate () 9: 9: check ()
8: 8: add to database () Data

User
controller base
Figure2.22: collaboration diagram for add user

8: 8: view informations()
Posted info
page
: User 7: 7:display posted information()
1: 1:select posted info link() 2: 2: send message()
View posted
info link
6: 6: send message()
3: 3:transfer message()
5: 5:check()
4: 4:request from database() Databa

Posted info se
controller
Figure 2.23: collaboration diagram for view posted information’s

View post 2: 2: send message ()
link Post
type
1: 1: select post link () 4: 4: select post type ()
3: 3: Display post type ()
: Investigative
officer/ police
14: 14: Display response ()
11: 11: display not successful message ()

7: 7: fill the form...
8: 8: click post button () 13: 13: check ()
5: 5: send message ()
6: 6: display form ()
Data
base
12: 12: add to database ()

10: 10: check ()
9: 9: send message () post

Post controller
form
Figure 2.24: collaboration diagram for posting

View report 2: 2: send message ()
link
Report
type
1: 1: select report link() 4: 4: select report type ()
3: 3: Display report type ()

: Investigative
officer/ police
14: 14: Display response ()
7: 7: fill display report form () 11: 11: display fill again message ()
8: 8: click report button ()
6: 6: Display report form ()

13: 13: check ()
Datab
ase
12: 12: add to database ()
10: 10: check ()

Report
form
Report
controller
Figure 2.25: collaboration diagram for generate report

4: 4: select report type()
5: 5: click on view button()
Report
: 3: 3:display report type() type
adminstrator
1: 1:select view report link() 2: 2: send message()
View report 8: 8: display reports()

link 6: 6:send message()
7: 7:fetch() Data
Report
controller base
Figure 2.26: collaboration diagram for view report

Update user
4: 4: Edit user detail ()
5: 5: Click update button () form
3: 3: Display update user form ()
:
administrator
1: 1: click update user link ()

11: 11: display successful message ()
8: 8: display not successful message ()
Update
user link
7: 7: validate () 10: 10: check ()
9: 9: update data ()
Update User Data
controller base
Figure 2.27: collaboration diagram for update user
2.4.3 State chart diagram

State chart diagram describes the flow of control of the Debre Berhan police station criminal file
management proposed system from one state to another state to describe the system dynamically. States
are defined as a condition in which an object exists and it changes when some event is triggered. So the
most important purpose of State chart diagram is to model life time of an object from creation to
termination.
Figure 2.28: State chart diagram for login
Figure 2.29: State chart diagram for view report
Figure 2.30: State chart diagram for add new user

Figure 2.31: State chart diagram for generate FIR report
Figure 2.32: State chart diagram for post wanted criminals
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
Figure 2.35: State chart diagram for update progress file

Figure 2.36: State chart diagram for view posted information
2.4.4 UML class diagram

UML class diagram represents the static view of an application. Not only used for visualizing,
describing and documenting different aspects of a system but also for constructing executable code of
the software application Sumi Thomas PainumkaL - March 2009.
Figure 2.37: class diagram for Debre Berhan police station crime file management system
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.
3.2Design goals and objectives

The objectives of design are to model the system with high quality. The design goals are derived from
non-functional requirements that means non-functional requirement is the description of the feature
characteristics and attribute of the system as well as any constraints that may limit the boundary of the
proposed solution.
Design goals describe the qualities of the system that the developers should consider.
 Reliability: the proposed system should be reliable.

 Fault Tolerance: Debre birhan police station crime file management system should be fault
tolerant to loss of connectivity with the service.
 Security: the proposed system should be secured, i.e., not allow other users or unauthorized users
to access data that has no the right to access it.
 Modifiability: the proposed system should be modifiable for further modification and
enhancement of the application.
 Performance: Debre birhan police station crime file managementsystemshould respond fast with
high throughput, i.e. It should perform retrieving crime case, registering progress crime case,
updating progress files and generating report as quickly as possible.
 End User Criteria: The proposed system should have simple and understandable graphical user
Interface such as forms and buttons, which have descriptive names. It should give reliable response
for each request at least before the session expires.
 Dependability: The system should be robust (forceful) i.e. it should be able to carry on invalid
user inputs, fault tolerant, reliable and available. The system shouldn’t allow non-authorized users
to access progress investigation files.
 Cost: The system should be developed, deployed, administered and maintained with minimum cost
possible.
 Usability: Usability is the extent to which a product can be used by specified users to achieve
specified goals with effectiveness, efficiency and satisfaction in a specified context of use. From the
end users’ perspective the proposed system should be designed in such a way that it is easy to learn
and use, efficient and having few errors if any.
3.3 System decomposition

The proposed Debre Berhan police station crime file management system has modules: login, FIR
management, retrieves closed files, posted management, manage progress files, generate report, and
manage staff.
Figure 3.1: system decomposition diagram
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.
Retrieve closed files
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.
Posted information’s management
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.
Manage progress files
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.4: user interface prototyping design
3.7 design of class diagram (class mapping)

The class diagram is a static diagram. It represents the static view of an application. Class diagram is not
only used for visualizing, describing and documenting different aspects of a system but also for
constructing executable code of the software application. The class diagram describes the attributes and
operations of a class and also the constraints imposed on the system. The classes diagrams are widely
used in the modeling of object oriented systems because they are the only UML diagrams which can be
mapped directly with object oriented languages. The class diagram shows a collection of classes,
interfaces, associations, collaborations and constraints. It is also known as a structural
diagramAniekwe Vivian Nkiruka - August, 2012.
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
component, or other computer system through computer programming and deployment(Aniekwe

Vivian Nkiruka - August, 2012). In our project, implementation exist for a given specification or
standard. So the team is in a position of converting all documents gathered and designed into the code so
that the system will be implemented for the user to be used for the purpose it developed. To implement
it, the organization must have a server on which the system will be hosted because this system can run
on intranet site with connection available or on internet connection.
4.2 User Interface

In this system, users will interact with the system through the following user interfaces.
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.
//Sample code for placement
<?php
error_reporting(0);
include('config.php')
?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="stylesheet" href="css/style.css" type="text/css">
<title>Members Area</title>
</head>
<body>
<div class="header">
<div>
<a href="index.html" id="logo"><imgsrc="images/logo.png" alt="logo"></a>
<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>C</span>amp <span>S</span>tarts <span>I</span>n:

<span><span>228</span></span><span>D</span>ays
</p>
</div>
</div>
</div>
<div class="body">
<div>
<div>
<div>
<div class="programs">
<h2>WeLCOME TO YOUR PAGE</h2>
<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 = mysql_fetch_array(mysql_query('select count(*) as nb_new_pm from pm where ((user1="'.

$_SESSION['userid'].'" and user1read="no") or (user2="'.$_SESSION['userid'].'" and user2read="no")) and
id2="1"'));
$nb_new_pm = $nb_new_pm['nb_new_pm'];
?>
<ul> <li><li>
<a href="edit_infos.php">PROFILE</a>
</li>
<li>
<a href="users.php">STAFF LIST</a>
</li>
<li>
<a href="list_pm.php">NEW REPORT(<?

php echo $nb_new_pm; ?> )</a>
</li><li>
<a href="viewfir.php">NEW FIR</a>

</li><li>
<a href="miss.php">MISSING
PERSONS</a>
</li>
<li>
<a href="connexion.php">LOG OUT</a>
</li>
</ul>
</div>
<div>
<a href="<?php echo $url_home; ?>"><imgsrc="<?php echo $design; ?>/images/logo.png" alt="Members

Area" /></a>
<?php
$ctrl = $_REQUEST['key'];
?>
<table>
<tr>
<th>Id</th>
<th>Username</th>
<th>cases</th>
<th>hold</th>
</tr>
<?php
$req = mysql_query('SELECT id, username from users');
while($dnn = mysql_fetch_array($req))
?>
<?php
$ende = $dnn['username'];
$hab = mysql_query("SELECT * FROM fir WHERE username ='$ende'");
$dan = mysql_num_rows($hab);
?>
<tr>
<td><?php echo $dnn['id']; ?></td>
<td><?php echo htmlentities($ende, ENT_QUOTES, 'UTF-8'); ?></td>
<td><?php echo $dan;?></td>
<td><?php print("<a href = 'setofficer.php?key=".$ende." & id=".$ctrl."'><imgsrc =

'image/views.png'></img></a>"); ?></td>
</tr>
</table>
<?php
}}
?>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="footer">
<div>
</div>
</body>
</html>
//Sample code for view FIR

<?php
include('config.php')
?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="stylesheet" href="css/style.css" type="text/css">
<title>Members Area</title>
</head>
<body>
<div class="header">
<div>
<a href="index.html" id="logo"><imgsrc="images/logo.png" alt="logo"></a>
<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">
<h2>WeLCOME TO YOUR PAGE</h2>
<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 = mysql_fetch_array(mysql_query('SELECT count(*) as fir from fir where view="no"'));
$fir = $fir['fir'];
?>
<?php
if(isset($_SESSION['username']))
$nb_new_pm = mysql_fetch_array(mysql_query('select count(*) as nb_new_pm from pm where ((user1="'.

$_SESSION['userid'].'" and user1read="no") or (user2="'.$_SESSION['userid'].'" and user2read="no")) and
id2="1"'));
$nb_new_pm = $nb_new_pm['nb_new_pm'];
?>
<ul> <li><li>
<a href="edit_infos.php">PROFILE</a>
</li>
<li>
<a href="users.php">STAFF LIST</a>
</li>
<li>
<a href="list_pm.php">NEW REPORT(<?

php echo $nb_new_pm; ?> )</a>
</li><li>
<a href="viewfir.php">NEW FIR(<?php
echo $fir; ?> )</a>
</li><li>
<a href="miss.php">MISSING
PERSONS</a>
</li>
<li>
<a href="connexion.php">LOG OUT</a>
</li>
</ul>
</div>
<div>
<a href="<?php echo $url_home; ?>"><imgsrc="<?php echo $design; ?>/images/logo.png" alt="Members

Area" /></a>
<?php
$reg=mysql_query("select * from fir ");
$countreg=mysql_num_rows($reg);
echo"<center>";
echo '<font size="2"><br><br><h2><u>Information:</u></h2><br><br> There are '.

$countreg. ' fir Are registered';
echo"</center>";
echo"<br><br>";
$result = mysql_query("SELECT * FROM fir WHERE view='no'");

echo "<table width='350px' align='center'>
<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 ("<td>" . $row['fir_id'] . "</td>");
print ("<td>" . $row['first_name'] . "</td>");
print ("<td>" . $row['crime_time'] . "</td>");
print ("<td>" . $row['crime_place'] . "</td>");
print ("<td><a href = 'viewinfo.php?key=".$ctrl."'><imgsrc = 'view.png'></img></a></td>");
print ("</tr>");
print( "</table>");
?>
<?php
}}
?>
<table>
<tr>
<td><a href="unasigned.php">UNASIGNED CASES</a></td>
</tr>
<br><br><br>
<tr>
<td align="left"><a href="oldcases.php">VIEW OLD CASES</a></td>
</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
Object life line
Deployment diagram
Message line extends from the lifeline of one

object to the lifeline of another object.
Include, relates to the include use case to
indicate inserted behavior
Create Return Message
Starting point of activity/state diagram
Ending point of activity/state 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
Aniekwe Vivian Nkiruka - August, 2012 - COMPUTERIZED CRIME TRACKING

INFORMATION SYSTEM - Caritas University, Nigeria
Delhi PoliceGovernment of Delhi - CRIME AND CRIMINAL TRACKING NETWORK &SYSTEMS

- Delhi, India
Sumi Thomas PainumkaL - March 2009 - CRIME MANAGEMENT AND REPORTING SYSTEM
- Cochin University of Science and Technology
S. Sumalatha (Asst. Proff.) - CRIME RECORD AUTOMATION - Aryabhata Institute of

Technology & Science, India

Debre Berhan Crime File Management System

Uploaded by

Copyright:

Available Formats

Debre Berhan Crime File Management System

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Debre Berhan Crime File Management System

Uploaded by

Copyright:

Available Formats

What are the objectives of the project?

What are the objectives of the project?

What methodology is used in the project?

What methodology is used in the project?

Debre Berhan crime file management system 2007

Table 2.1: Class Responsibility and collaboration ………………………….………….………....12

Table2.2: Main Course of Action about Login….………………………..……………….……..21

Table 2.3:Main Course of Action about register new case….……………...…….…22

Table 2.4: Main Course of Action about update progress cases….............................23

Table 2.6: Main Course of Action about Update Account …………………………....25

Table 2.7: Main Course of Action about Inactivate Account …………….……….….25

Table 2.8: Main Course of Action about retrieve info ………………………………….26

Table 2.9: Main Course of Action about View Report……………………….……..…..27

Table 2.10: use case about generate report..………………...……………………..……28

Table 2.11: use case description about generate investigation report...……...…… 28

Table 2.12: Main Course of Action about post wanted criminals……………………29

Table 2.15: main course of action about manage FIR...………………………….…… 31

Table 2.16: main course of action about add FIR ………………………………………32

Table 2.18:main course of action about logout ……………………………………...…34

Figure 2.2: activity diagram for login ……………..……………………………...……..…….35

Figure 2.3: activity diagram for register new case …………………………………..….….36

Figure 2.7: activity diagram for view report ……………….………………………..……….40

Figure 2.8: activity diagram for post wanted criminals …………………………..……….41

Figure 2.9: activity diagram for add new use ……………………………………………….42

Figure 2.10: activity diagram for generate investigation report………….………..….…43

Figure 2.11: activity diagram for manage staff………………………………………...……44

Figure 2.13: activity diagram for retrieve criminal case…………………..……….……...46

Figure 2.14: sequence diagram for login ………………………………..................................48

Figure 2.16: sequence diagram for retrieve crime case …………………….…….……….50

Figure 2.17: sequence diagram for view report ……….…………………………...….…….51

Figure 2.18: sequence diagram for manage FIR…….……………………….…..………....52

Figure 2.20: sequence diagram for update user………………………………….…………54

Figure 2.21: sequence diagram for update progress file ………………………………….56

Figure 2.22: sequence diagram for add FIR ……………………………………..….……….58

Figure 2.23: sequence diagram for posting …………………………………….…………….60

Figure 2.25sequence diagram for add user………………………………………………….62

Figure 2.26: collaboration diagram for login …………………………………………...……63

Figure 2.27: collaboration diagram for retrieve case……………………………………….64

Figure 2.28:collaboration diagram for add user …………………………………………...65

Figure 2.29: collaboration diagram for view posted information’s………………...……65

Figure 2.30: collaboration diagram for view FIR…….……………………………...……....66

Figure 2.31: collaboration diagram for posting …………………………….………….…....67

Figure 2.32: collaboration diagram for update progress file ……………….…………….68

Figure 2.34: collaboration diagram for view report ……………………………….……….71

Figure 2.35: collaboration diagram for update user…………………………….…..……..72

Figure 2.36: collaboration diagram for add FIR………......……………………...….……..73

Figure 2.37:State chart diagram for login ……………………………………….…….……74

Figure 2.38: State chart diagram for view report …………………………………………..75

Figure 2.42: State chart diagram for post wanted criminals……............….....................78

Figure 2.45: State chart diagram for update progress file….…………..........……………79

Figure 2.46: State chart diagram for view posted information.…......................................80

Figure 3.1: system decomposition diagram………………………………………….………….68

Figure 3.3: user interface prototyping design ………………………………..……….………………...72

1.2 Background of the organization

1.3 Problem of the statement

 All criminal information’s are paper based which is cumbersome to maintain

1.4 Objectives of the project

1.4.2 Specific objective