WEB BASED CRIMINAL RECORD SYSTEM

A PROJECT REPORT
Submitted by:

Name of student ID_NO

Melkamu Chemere-------------------------------TER/4676/07
Lakachew Yibeltal--------------------------------TER/4670/07
Yassab Aziz--------------------------------TER/4696/07
Tesfaye Bayih-------------------------------------TER/4691/07

In Partial Fulfilment for the Award of theDegree Of

BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY
Under the guidance of

GizachewuM. (MSC)

-------------------------------------------
ADVISOR SEGNATUR

DEPARTMENT OF INFORMATION TECHNOLOGY

INSTITUTE OF TECHNOLOGY
DEBRE MARKOS UNIVERSITY

Debre Marko’s, Ethiopia

May 2010 E.C
 2010 E.C
Web based criminal Record System

Declaration
We, under signed,declere that thesis our original work, has not been presented for a degree in
this or any other university, and all the source of martial used for the thesis/project have been
acknowledged.

Name Id No Signature

Melkamu Chemere----------------------TER/4676/07 ----------------------

Lakachew Yibeltal------------------------TER/4670/07 ----------------------

Yassab Aziz--------------------------------TER/4696/07 ----------------------

Tesfaye Bayih-------------------------------------TER/4691/07 ----------------------

I
 2010 E.C
Web based criminal Record System

APPROVAL OF ADVISOR AND EXAMINERS

This project has been submitted for examination with our approval as the
project advisor.

Advisor Name ____________________ Signature ____________

This project has been examined with our approval as the project examiner.

Examiner Name:

1. ____________________ signature______________

2. ____________________Signature______________

3. _____________________Signature_____________

II
 2010 E.C
Web based criminal Record System

Acknowledgments
First of all we would like to thanks for our God that keep sour life up to this time
and giving all strength for successful completion of this documentation. Secondly
we would like to thanks for our Advisor Gizachew Melkamu for his great
contribution guidance, support and gives us continuous initiation and
encouragement from the beginning up to the end of the project. We also want to
thank for inspector ayalneh who is Debre Markos city police station manager and
office workers since they provide all the Information about how the current system
works. And we would like to thanks for the department of information technology
that contribute computer laboratory for the success of the project.

III
 2010 E.C
Web based criminal Record System

ABSTRACT
Crime is a human experience and it has to be controlled. Debre Markos city police
station plays a great role to control crime and criminal activities But the way of
managing those criminal and crime activities done manually and this is due to lack
of automated system that supports the station workers to communicate with citizen
to share information and store and retrieve criminal activities. In order to control
crime efficiently we need to develop web based systems.

This project entitled as “Web based criminal record system” that is designed to
develop a web application in which any citizen can report crimes; if anybody wants
to complain against crimes he must enjoy with web based communication to police
station. This project provides to store records of crimes and criminals which have
made disciplinary case and used to make simply retrieve information from the
database. The proposed system is a typical automated crime Record system, based
on client-server architecture.

IV
 2010 E.C
Web based criminal Record System
Contents
Acknowledgments.......................................................................................................................................... I
ABSTRACT................................................................................................................................................. IV
List of Table ................................................................................................................................................ VII
List of Figures ............................................................................................................................................ VIII
Acronyms ..................................................................................................................................................... IX
CHAPTER ONE ........................................................................................................................................... 1
1.1. Introduction ........................................................................................................................................ 1
1.2. Background of the project .................................................................................................................. 2
1.3. Statement of the Problems ................................................................................................................. 2
1.4. Objectives of the project .................................................................................................................... 3
1.4.1. General objective ........................................................................................................................ 3
1.4.2. Specific objective ........................................................................................................................ 3
1.5. Scope of the Project ........................................................................................................................... 3
1.6. Limitation of the project .................................................................................................................... 4
1.7. Significance of the Project ................................................................................................................. 4
1.8. System requirement ........................................................................................................................... 4
1.8.1. Hardware requirement tool ......................................................................................................... 4
1.8.2. Software requirement tool ........................................................................................................... 5
1.8.3. Programming language ............................................................................................................... 5
1.9. Data collection Methodology ............................................................................................................. 6
1.9.1. Data collection ............................................................................................................................ 6
1.10. Feasibility study ............................................................................................................................... 7
1.10.1. Operational Feasibility .............................................................................................................. 7
1.10.2. Economic Feasibility................................................................................................................. 7
1.10.3. Technical Feasibility ................................................................................................................. 8
1.10.4. Legal Feasibility........................................................................................................................ 8
Chapter Two.................................................................................................................................................. 9
2. System analysis ......................................................................................................................................... 9
2.1. Over View of Existing System........................................................................................................... 9
2.1.1. Users of the existing system........................................................................................................ 9

V
 2010 E.C
Web based criminal Record System
2.2. System requirement Specification ................................................................................................... 10
2.2.1. Functional requirement ............................................................................................................. 10
2.2.2. Non-functional requirements: ................................................................................................... 11
2.2.3. Business rule ............................................................................................................................. 12
2.3. System requirement analysis............................................................................................................ 12
2.3.1. Actor and Use case Identification ............................................................................................. 13
2.3.2. UML Sequence Diagrams ......................................................................................................... 24
2.3.3. UML Activity diagram.............................................................................................................. 29
2.3.4. Analysis Class Diagram ............................................................................................................ 32
3. System Design ........................................................................................................................................ 33
3.1. Design Class Diagram.......................................................................................................................... 33
3.1.1. Description of design class diagram ............................................................................................. 34
3.2. Database design /Physical data model ................................................................................................. 36
3.3. User Interface Design .......................................................................................................................... 40
3.4. System Architecture ............................................................................................................................. 44
3.4.1 Deployment Diagram ..................................................................................................................... 44
Reference .................................................................................................................................................... 53

VI
 2010 E.C
Web based criminal Record System

List of Table
Table 1: Use Case Identification ................................................................................................................. 15
Table 2: Register User Use Case Description ............................................................................................. 18
Table 3: Create Account Use Case Description ......................................................................................... 19
Table 4: Login Use Case Description ........................................................................................................ 20
Table 5: Register Accused Use Case Description ....................................................................................... 21
Table 6: Assign Police Use Case Description ............................................................................................. 21
Table 7: Post Missing Criminals Use Case Description ............................................................................. 22
Table 8: send complain Use Case Description............................................................................................ 23
Table 9: Complaint class diagram Description ........................................................................................... 35
Table 10: Crime Class diagram Description ............................................................................................... 35
Table 11: Placement class diagram Description ......................................................................................... 36
Table 12: method of detective Officer ........................................................................................................ 36
Table 13: Accuser Database Table.............................................................................................................. 37
Table 14: Employee Database Table .......................................................................................................... 38
Table 15: Missing Criminal Database Table.............................................................................................. 39

VII
 2010 E.C
Web based criminal Record System

List of Figures
Figure 1: Web based criminal systems Use Case Diagram......................................................................... 17
Figure 2: User Login Sequence Diagram .................................................................................................... 25
Figure 3: Assign police Sequence Diagram ................................................................................................ 26
Figure 4: Give Nomination Sequence Diagram .......................................................................................... 27
Figure 5: Posts Missing Criminal Sequence Diagram ................................................................................ 28
Figure 6: View post criminal Activity Diagram ......................................................................................... 29
Figure 7: Register Accuser Activity Diagram............................................................................................. 30
Figure 8: View Criminal Activity Diagram ................................................................................................ 31
Figure 9: Web based Criminal Record system Analysis Class Diagram .................................................... 32
Figure 10: Online Police Station Criminal System Design Class Diagram ............................................... 33
Figure 11: Preventive Police page user interface ........................................................................................ 40
Figure 12: Preventive Police page user interface ........................................................................................ 41
Figure 13: Police head post missing person user interface ......................................................................... 42
Figure 14: Police head post notice user interface........................................................................................ 43
Figure 15: Deployment Diagram ................................................................................................................ 44
Figure 16: security testing ........................................................................................................................... 52

VIII
 2010 E.C
Web based criminal Record System

Acronyms
 CSS-------------------------------------------Cascading style sheet
 UML------------------------------------------Unified modeling language
 HTML----------------------------------------Hypertext markup language
 MYSQL--------------------------------------My structure query Language
 PHP-------------------------------------------Hypertext pre processer
 ID----------------------------------------------Identification Number
 RAM------------------------------------------Random Access Memory
 CPU-------------------------------------------Central processing unit
 CD---------------------------------------------Compact disk
 UC---------------------------------------------Use case
 BR---------------------------------------------Business Rule
 WAMP----------------------------------------window apache mysqlphp
 HR---------------------------------------------Human Resource
 DMPS-----------------------------------------debre Marko’spolice station

IX
 2010 E.C
Web based criminal Record System

CHAPTER ONE
INTRODUCTION

1.1. Introduction
In this modern world, information technology plays a big role. With the introduction of
computers, the business world was changed forever. Using computers and software, businesses
use information technology to ensure that their departments run successfully. (1)
Now a days Technology is being used in almost every company to accomplish specific
tasks.Many businesses are using various business communication technologies to change the
way their employees interact and communicate while at work. Employees can use various
communication tools to interact or exchange information at work such us developing website for
online communication.
Web application is one parts of information technology in which applications and information’s
are stored on servers and users can access that information or application remotely using web
browsers. “Web based criminal record system” is a web application that provides users interact
with the system without any physical contact. This system helps the police department to
generate fast reports, and to retrieve criminal cases. It also establishing an active and equal
partnership between the Police and the public through which crime and community safety issues
can jointly be discussed and solutions determined and implemented.

1
 2010 E.C
Web based criminal Record System
1.2. Background of the project
In 1913, during the reign of Emperor Minilik II, the Ethiopian police was founded for the first
time in our history. A modern police establishment was newly founded in 1934. Debre Markos
police station was also established newly as a police force at the same time in 1934. It is the
basic unit that looks after the law and order of that area. Debre Markos police station is headed
by a Station House Officer (S.H.O.) who is generally an inspector from the police department.
Under him works a team consisting of a Sub-Inspector, Head Constable and Constables. The
station was organized in to five big departments that were detection department, prevention
department, traffic department, human resource management department and council
community.Still now, the system is working manual (10)

1.3. Statementof the Problems

Criminal record system in DMPS takes place manually with paper; sharing information between
polices and their manager needs physical contact. When complaints and accusers needs to
request their case and to get response they must attained to the station physically. Many
resources like paper will be lost.

All criminal information’s are paper based which is cumbersome to maintain. Even an efficient
officer may not be able to handle more than one case at a time.

Access to the criminal information is not well controlled and there is no clear security on
avoiding possible manipulation of information which results in possible alteration by
unauthorized users. Retrieving information from this type of system can be cumbersome and
time consuming especially when searching for information from former years.

Data redundancy and inconsistency, there is a Work load over police departments since
investigation reports and investigation files are manually operated.

2
 2010 E.C
Web based criminal Record System

1.4. Objectives of the project

1.4.1. General objective

The general objective of this project is to develop a web based criminal record system for Debre
Markos police station.

1.4.2. Specific objectives

The specific objectives of the proposed system are:

 Develop a database system for every criminal information.

 To enable searching for any relevant information about crime quickly that is committed
from anywhere in the city and the required information by using keys and also the main
function of the system is sharing of information to the citizen.
 Develop a system that enabling the user to communicate easily across the station and
complaints to report their case through a web based system.
 Design attractive user interface that the police station worker and customers can easily
interact.
 Confirm secure data flow in the station by Building security and monitoring control to
ensure only authorized personnel have access to the criminal information.
 Develop a system that make retrieval of required data from database with expected time.
 Develop a system that facilitates fast report generation

1.5. Scope of the Project

The scope of a project shows the boundary of the project it will cover. It may be geographical
boundary or functional boundary.
Even though Crime Recorded police station
 Geographical boundary: -Geographically the system is limited to Debre Marko’s city police
station.
 Functional boundary: - the proposed project had functionally limited to the following
activities, register employee by human resource management department, finding
information about missing criminal online system from citizens, allow citizen give
information, give and take the nomination, generating reports, and take backup.

3
 2010 E.C
Web based criminal Record System

1.6. Limitation of the project

The Proposed System may have some Limitations some of them are:

 The system does not support different language.

 Users receive notifications and nominations only with the system; SMS by phone is not
supported in this system.
 Camera deployment is not available

1.7. Significance of the Project

This system has the following significance:
For the organization
 Simplified process for managing crime information
 Facilitates fast and efficient retrieval of data.
 Reduce time consumption
 Reduce resource consumption
For citizen/customer of the system
 Create customer or complaint satisfaction by save time and resource needed to complete
their task.
 It enables citizens to give nomination easily without arriving in the station.
For users/member of the station
 Create satisfaction for police officer and staff members by minimizing workload by
sharing information through online such as: request, response, report and view wanted
information without physical contact.

1.8. System requirement

Hardware and software tools required for the successful completion of the projects are listed
below with their respective significance.

1.8.1. Hardware requirement tool

Computer: -with 4.00 GB RAM, 500 GB hard disk and processor speed above 2.4 GHz.

Flash: -16 and more GB flash is required for data storage and data movement.

4
 2010 E.C
Web based criminal Record System
Disks (CD):-720 MB necessary for the movement of relevant data and for backup and recovery
mechanism.

Internet Connection: -the main information source to develop our system. To extract relevant
information about our project from internet.

Printer: - helps to print documentations

Writing material (pen, paper):- for writing all necessary information associated with the
project during interview or time of data collection

Notebook:-to take notes during data collection and for other documentations

1.8.2. Software requirement tool

Software requirements to develop system are as follows
WAMP server: -32-bit version of wamp server, used to run application.
Microsoft word 2010:- to write on any necessary documents about the project

Microsoft Visio2007: - used to draw diagrams

Adobe Photoshop CS4: -to edit images.

Notepad++:- editor’s that helps to write a php implementation code

Microsoft Power Point 2010:- helps to prepare presentation of the project.

Edraws Max8:-For designing UML diagrams associated with the project. E.g. Activity
Diagram, Class Diagram, Sequence Diagram and Use case Diagram.

1.8.3. System Implementation and database tools

Frontend Programming language: Is programming language that you see and interact with on
your browser. Also referred to as “client-side”.
 HTML - the fundamental coding language that creates and organizes web content so it
can be displayed by a browser.
 JavaScript: to create interactive webpages.

5
 2010 E.C
Web based criminal Record System
 Css: a language that accompanies HTML, and defines the style of a website’s
content, such as layout, colors, fonts, etc.
Backend programming language: also known as “server-side” is the portion of the website you
don’t see. It’s responsible for storing and organizing data, and ensuring everything on the client-
side actually works. Such as php, Perl, Python, MYSQL, ruby Etc. But we are interesting to do
with Php because
 It is OS independent or compatible on all operating systems.
 Simple and easy to learn for developer: - When compared with other scripting
languages.
 allows data base integration with wide variety of application
Database tool: - MYSQL
 Open –source
 Secure
 Easy connection to programming to indicated

1.9. Data collection Methodology

Different fact finding techniques were used to gather information about the current system. It is
the fundamental activity for the development of the system.

1.9.1. Data collection

Data collection is the most important part of our project to find the main required information to
system and to understand how the system works. We used the following methods to collect
relevant data required to our project.

 Primary data collection methods

 Interview: - the project team gathered necessary information about how the
organization works and current flow of work by interviewing Debre Markos city
police head, staff member and society. During Interviewing the team got various
necessary information from the station and the team asking different question about
the organization how to work and the overall structure.
 Observation: - the project team gather some additional information by observe the
actual work being done in police station
 Secondary data collection methods

6
 2010 E.C
Web based criminal Record System
Document analysis: - we reviewed other relevant documents that help to know about the existing
system.

1.10. Feasibility study

A feasibility study is a test of system proposal according to its workability, impact on the
organization, ability to meet user needs and effective use of resources.
A feasibility study looks at the viability of an idea with an emphasis on identifying potential
problems. Project managers use feasibility studies to determine potential positive and negative
outcomes of a project before investing a considerable amount of time and money into it.

1.10.1. Operational Feasibility

Operational feasibility is a measure of how well a proposed system solves the problems. Most of
the business needs from the proposed system are searching information’s from citizen and
gathering information about missing criminal, Citizens giving nomination online, getting
nomination and generating report. With great cooperation of the project team the site had provide
all functions of the business need listed above so the proposed system is operational feasible.

 Due to most users of the system are educated those users need less training.
 The interface of the system directs the user how to use it.
 the technology it can be easily maintained and repaired; accomplished with the available
technology, technically, the system will be powerful to be applied by low skilled users as
much as possible and easily accessible by the people who can easily understand natural
languages The team proposed system is technically feasible.

1.10.2. Economic Feasibility

Our proposed system is economically feasible to the organization because when we compare the
cost that we need to develop and implement the proposed system less expense than the existing
manual system or not require much more cost and material to implement the system. Here we
have stated the costs related to the project and the benefits that are going to be gained after the
completion of the project by performing a cost-benefit analysis.

Tangible benefits

7
 2010 E.C
Web based criminal Record System
Tangible benefits are something that has a physical existence. Cost reduction and avoidance,
increase the income of the organization, improving response time, producing error free out put
such as report generating, and no redundancy, increased management planning and control

 Intangible benefits

Increase information processing efficiency, faster decision making, increase accuracy, right
information at the right time, Customer satisfaction. Intangible costs are not always foreseen.

The cost needed to search one criminal is comparatively equal to the cost needed to develop the
System, so it was economically feasible.

1.10.3. Technical Feasibility

Technically, the system is powerful to be applied by low skilled users as much as possible.

There is no need for the developer involvement in almost all implementation of the entire
system. It is easily accessible by the people who can easily understand natural languages

1.10.4. Legal Feasibility

The system to be developed is not contrary with any government directives, and with any
cultural aspects or norms, because it gives services for Debre Markos police station workers, all
the Debre Markos police workers also agreed before the system developed. So the government
and peoples are profitable and the system will be legally feasible.

8
 2010 E.C
Web based criminal Record System

Chapter Two

2. System analysis
System analysis is a process of gathering and interpreting facts, diagnosing problems and the
information to recommend improvements on the system. It is a problem solving activity that
requires intensive communication between the system users and system developers. System
analysis or study is an important phase of any system development process. (2)

2.1. Over View of Existing System

Currently in Debre Markos city there is no any automated system for sharing of information
between the police and the citizens. Almost all activities in the current system take much time
cost and need labor works. The existing system needs spadework when police wants to retrieve
criminal information that can be search from large document files. Police want to detect or
search detail information about some criminal action the police went long distances from place to
place with transport or with their foot (areas that does not have transport access).In the existing
system complaint went to police station to report their aggrivance, and anonymous events like
thefts, murder, missing citizens, dead bodies and other miscellaneous events, at this time the
complaint spend their time, lose money for transport, faced an accident and sacrifice energy.

Generally the system works manually in the above process of these takes long period of time to
respond user’s service request and also it consumes high human power.

2.1.1. Users of the existing system

Users are entities that interact with the system. User those involved in the existing system are: -

 Police Head
 Criminal preventive police
 Complaint
 Administrator
 Detective Officer
 HR manager
 Customer

9
 2010 E.C
Web based criminal Record System

2.2. System requirement Specification

A project requirement is an objective that must be meet. Project requirements provide an obvious
tool for evaluating the quality of a project, because a final review should examine whether each
requirement has been met. This project is concerned in the functional requirements and non-
functional requirements.

2.2.1. Functional requirement

The functional requirements describe the core tasks of the system or it is the intended behaviors
of the system. The new proposed system of criminal record system focus mainly those tasks,
services or functions that the system is required to perform. The team project supposed to have
the following three main process functional requirements.

Input data: - this is the functionality that the system will allow the user to enter input data using
forms for processing.

 The system should allow System users to retrieve relevant data.

 The system should allow system administrator create account.
 The system should allow preventive police to record criminal and complaints.
 The system should allow detective officer register accuser, accused and witness
 The system should allow Human resource manager to register new employee
 The system should allow system administrator to post laws of the government.
 The system should allow preventive police to post missing criminals
 The system should allow citizen to give nomination to missing criminals
Process data: -This is the other functionality that the system provides to process the data or
inputs that the user submits using forms. The system provides those data processing functionality
listed below.

 The system should allow validating the input data.

 The system should allow system take backup
 The system should allow sharing information between Employees of the station
 The system should allow system administrator update user status
 The system should allow police head update missing criminal

10
 2010 E.C
Web based criminal Record System
 The system should allow detective police update status of accused criminals
 The system should allow detective police manage complaint
 The system should allow Human resource manager update employee status
 The system should allow system police head assign police to their job placement

Data output: This is the functionality that the system provides several data’s as an output. Those
functionalities are

 The system should allow detective police view registered criminal

 The system should allow preventive police view complaints
 The system should allow system police head view report
 The system should allow police head View comment
 The system should allow citizens View missing criminal
 The system should allow citizens give nomination
 The system should allow citizens send complain request

2.2.2. Non-functional requirements:

Nonfunctional Requirements (also known as system qualities) define system attributes such as
security, reliability, performance, maintainability, scalability, and usability. They serve as
constraints or restrictions on the design of the system across the different backlogs. In general
this system ensures the usability, efficiency and effectiveness of the entire system. (3)

 Availability: The system is available in 24 hours a day and seven days a week
 Efficiency: This system must ensure allocation and use of services being requested for
the users by using minimum memory storage, cost, and time.
 Security: The user accesses the system using valid user name and password. The system
use md5 encryption security mechanism to secure password.
 Error handling: When a user interacts with the system errors may occur. To control this
kind of inaccuracies our system will generate different user friendly messages.
 Scalability: the system adding new features and new user without any problem

11
 2010 E.C
Web based criminal Record System
 User Interface: The interface will be user friendly and can properly guide the user how to
use the system and perform operations easily since every link name in the system similar
to the task performed.

2.2.3. Business rule

The system has different business rules that the organization to follow. These business rules are
obligations that the Employee of the system must fulfill in order to the system will function
properly and effectively.
These rules considered as in the system because any member of the department not beyond these
state. The most common business rules with the police station are:

BR 1: the police station department head should manage other members in the station.
BR 2: Members of the station shall obey all laws and ordinances.
BR 3: Members of the Department shall not express any prejudice concerning race, sex, religion,
national origin, life-style, or similar personal characteristics
BR 4: All employees of the Department shall report their places of residence and their telephone
number to the Commanding Officer or supervisor of the Bureau.
Business rules of the new team proposed system:
BR1: To access the system the users must be registered in the system and must have account.
BR2: User of the system must be login to the system to access the service provided by the system
BR3: User access the system based on their privilege given by system administrator

2.3. System requirement analysis

Systems Requirement Analysis gives the professional systems understanding the tools to set up a
proper and effective analysis of the resources, schedules and parts that will be needed in order to
successfully undertake and complete any large, complex project. The text offers the reader the
methodology for rationally breaking a large project down into a series of stepwise questions so
that a schedule can be determined and a plan can be established for what needs to be procured,
how it should be obtained, and what the likely costs in dollars, manpower and equipment will be
in order to complete the project at hand.(4)

12
 2010 E.C
Web based criminal Record System

2.3.1. Actor and Use case Identification

 Actors: - use in the system to represent user that interact with the system
 Use case: -A use case describes a sequence of actions that provide a measurable value to an
actor.

Actor Identification

1. Police Head
2. System administrator
3. Criminal preventive police
4. Detective Officer
5. Human resource manager
6. Compliant

Police Head: - have the following activities

Assign placement for preventive Police

View Employee
View Comment
View Nomination
Post Missing Criminals
View missing criminal
View Criminal Report

System administrator: -have the following activities

Create Account
View User Account
Update User Account
View Employee
View user activities
Take backup
Restore backup

13
 2010 E.C
Web based criminal Record System
Criminal preventive police: - have the following activities

View their Placement assigned by police head

Register Criminal
Register Complaint
Register crime
View complaint request
View Nomination
View Notice
Send nomination
View Order

Detective Officer: - have the following activities

View Criminal
Order Preventive police
Register witness
Register Accused
Register Accuser
View witness
View Accused
View Accuser
Generate first information Record

Human resource manager: - have the following activities

Register Employee
View Employee
Update Employee

Customer: - have the following activities

 View Missing Criminal

 Give Nomination

14
 2010 E.C
Web based criminal Record System
 Give Comment
Complaint: - have the following activities
Send Request
View response
 Use case identification:
Use case is an activities that accomplished by actors. Use case describes a sequence of actions
that provide a measurable value to an actor. In the following table we try to list use case id, use
case name and its description
Table 1: Use Case Identification
Use case ID Use case Name Include/
Uc1 Create Account Login
Uc2 View User Account Login
Uc3 Update Account Login
Uc4 View User Activities Login
Uc5 Take Backup Login
Uc6 Restore backup Login
Uc7 Assign placement for Police Login
Uc8 View Employee Login
Uc9 View Comment Login
Uc10 View Nomination Login
Uc11 Post Missing Criminals Login
Uc12 Post Notice Login
Uc13 View Criminal Report Login
Uc14 View Placement Login

Uc15 Register Criminal Login

Uc16 View Nomination Login
Uc17 Send Account Request for Complaint Login
Uc18 View Order Login
Uc19 View Complaint Request Login

15
 2010 E.C
Web based criminal Record System
Uc20 View Criminal Login
Uc21 Register Complaint Login
Uc22 Order Preventive police Login
Uc23 Register witness Login
Uc24 Register Accused Login
Uc25 Register Accuser Login
Uc26 Register First Information Record Login
Uc27 Order Preventive Police Login
Uc28 Register Employee Login
Uc29 Update Employee Login
Uc30 View Employee Login
Uc31 Send Complain Login

Uc32 View Complain Response Login

Uc33 View Missing Criminal -----------

Uc34 Give Nomination -----------
Uc35 Give comment -----------
Uc36 Login -----------
Uc37 Logout Login

UML Use Case Diagrams

A UML use case diagram shows the relationships among actors and use cases within a system.
A use case diagram is a graphic representation of the interactions among the elements of a
system. (5)

 A use case diagram contains the following sub-components:-

 System boundary: - which defines the system of interest in relation to the world around it.
 The actors: - usually individuals involved with the system defined according to their roles.
 The use cases: - which the specific roles are played by the actors within and around the
system.
 The relationships between and among the actors and the use cases

16
 2010 E.C
Web based criminal Record System

Web Based Criminal Recored System

Send Complian Create Account

View Response Update Account

Compliant

Post Notice View user Activity

<<include>> <<include>> Administrator

Assign Placment View USer
<<include>> <<include>>

View Employee <<include>> View missing

<<include>> criminal
<<include>>
<<include>>
View Criminal
Report <<include>> Give comment

<<include>> Customer
View Missing
Criminal <<include>>
Police head Give nomination
Login
View compliant <<include>> <<include>>

<<include>>
Update Employee
<<include>>
View Placment <<include>>
<<include>>
<<include>>

Registor Employee
<<include>> <<include>>
Registor Criminal

<<include>> <<Extended>> <<include>>

View Employee
View Report <<include>> HR manager
<<include>>
<<include>>
<<include>>
Registor Crime Update Criminal
<<include>> <<include>> Status
<<include>>
<<include>>
<<include>>
Preventive Police View Order
Logout Registor FIR

View Notice
View Criminal

Registor Compliant
Manage Accused

View Criminal Order Police

Send Account Registor Witness Manage Accuser Detective Police

Request

Figure 1: Web based criminal systems Use Case Diagram

17
 2010 E.C
Web based criminal Record System
 Use Case description
A use case description is a business analysis presentation of the steps defining the
interactions between a user (called an actor) and a system (usually a computer system). It
details the interactions and sets the expectations of how the user will work within the
system.(6).

Table 2: Register User Use Case Description

Use Case Name Register Employee
Use Case ID Uc28
Include Login
Actor Human resource manager
Description Human resource manager accepts the user and register to the database in
the system.
precondition The users should be worker of police station
Basic course of Actor action System response
action 1. HR manager open the system 2. The System open to user page
3. HR manager click on Register 4. System displays user registration
Employee Link form
5.Fill each individual fields 6. If the user correctly fill each required
and press register button field the system display “you are
Successfully registered” message
7. Use case end.

Alternative course of If the HR manager enters wrong username or password, the system display
action “Incorrect input” and the process turn again from step 5.

Post condition Employee are legal Users of the station

18
 2010 E.C
Web based criminal Record System

Table 3: Create Account Use Case Description

Use Case Name Create Account
Use Case ID Uc1
Include Login
Actor Administrator
Description Administrator create account for already registered users
precondition Administrator must login and should get list of users’ information From
Registered User.
Basic course of Actor action System response
action 1. Administrator Login to the 2.The System open to Administrator
system page
3. click on Create Account Link 4. System displays Create Account
5. The Administrator fill the form
field including user name and 6. If the entered data is valid the
password then Click on Create system display “you are Successfully
Account button create account” message.
7. Use case end.

Alternative course of If the user enters wrong username or password, the system display invalid
action input message and process turn again from step 4.

Post condition Users can login to the system with their account

19
 2010 E.C
Web based criminal Record System

Table 4: Login Use Case Description

Use Case Name Login
Use Case ID Uc36
Include -----
Actor Police Head, Preventive Police, Detective Officer, Human Resource
manager, Administrator, Complaint.
Description This use case is used to ensure security for system usage. Only legal users
can access the system.
precondition The user must have a valid user name and password from Administrator.
Basic course of Actor action System response
action 1. the user open the system 2. The System display Home Page
3. User Click Login Menu 4. The System display login form
5. User fills form and clicks 6. System displays user page
login button
7. Use case end.

Alternative course of User may input wrong user name and password the system display wrong
action message.
The process turn back to step 5
Post condition Users perform its own task on the system

20
 2010 E.C
Web based criminal Record System

Table 5: Register Accused Use Case Description

Use Case Name Register Accused
Use Case ID Uc24
Include Login
Actor Detective Officer
Description Detective Officer can Register the accused criminal to give decision.
precondition The Detective Officer must have a valid user name and password to Register
the accused criminal.
Basic course of Actor action System response
action 1. the user login to system 2. The user input correct value system
3. Detective Officer click display Detective Officer Page
Register accused Criminal link 4. System displays accused Criminal
5.Fill the form and click Register register form
button 6. System display successful message
7. Use case end.
Alternative course of User may input wrong user name and password the system show incorrect
action message.
The process turn back to step 1
Post condition Logout from the system.

Table 6: Assign Police Use Case Description

Use Case Name Assign placement for police
Use Case ID Uc7
Include Login
Actor Police Head
Description Police Head Assign police to their working Place
precondition The Police Head must have a valid user name and password to Assign police
to their task.

21
 2010 E.C
Web based criminal Record System
Basic course of Actor action System response
action 1. the police head login to 2. System directs to police head page
system 4. The system opens the form.
3. the user click Assign Link 6. system display successfully message
5. then Fill the Form and click 7. Use case end.
Assign button
Alternative course of A1.Police head may input wrong user name and password the system show
action incorrect message.
The process turn back to step 1
A2. Police head may fill wrong input the system show incorrect message.
The process turn back to step 5
Post condition User’s logout from the system.

Table 7: Post Missing Criminals Use Case Description

Use Case Post Missing Criminals
Name
Use Case ID Uc11
Include Login
Actor Police Head
Description Police Head post missing criminal on to the home page to get nomination
from the citizen.
precondition There must have missing criminal nominated From the people and
The Police Head must have a valid user name and password to post.

22
 2010 E.C
Web based criminal Record System
Basic course of Actor action System response
action 1. The police head login to system. 2. System directs to police head page.
3. The police head click on Post 4. The system displays Missing
missing criminal link person from
5. The police head fill the form and 6. The system displays “the missing
click post button. criminal successfully posted”
7. Use case end. message.

Alternative A1. If the user enters the wrong username or password, the system notifies
course of “the wrong input” and the process continues from step 1.
action

Post condition User’s logout from the system.

Table 8: send complain Use Case Description

Use Case Name Send complain
Use Case ID Uc31
Include login
Actor Complaint
Description Complaint send their complains for preventive police and preventive police
examine it and send response to the Complaint.
precondition Complaint must have user name and password.

23
 2010 E.C
Web based criminal Record System
Basic course of Actor action System response
action 1. The Complaint login to system. 2. System directs to complaint page.
3. The Complaint click on Send 4. The system displays the form
complain form 6. The system displays “successfully”
5. The Complaint fill the form and message.
send request
7. Use case end.

Alternative course A1. If the user enters the wrong username or password, the system notifies “the
of action wrong input” and the process continues from step 1.

Post condition User’s logout from the system.

2.3.2. UML Sequence Diagrams

UML sequence diagrams model the flow of logic within your system in a visual manner,
enabling you both to document and validate your logic, and are commonly used for both analysis
and design purposes. Sequence diagrams are the most popular UML artifact for dynamic
modeling, which focuses on identifying the behavior within your system.(7)

UML Sequence Diagrams Description

 capture the interaction between objects in the context of a collaboration

 show object instances that play the roles defined in a collaboration
 show the order of the interaction visually by using the vertical axis of the diagram to
represent time what messages are sent and when
 show elements as they interact over time, showing interactions or interaction instances

24
 2010 E.C
Web based criminal Record System

Figure 2: User Login Sequence Diagram

25
 2010 E.C
Web based criminal Record System

Figure 3: Assign police Sequence Diagram

26
 2010 E.C
Web based criminal Record System

Figure 4: Give Nomination Sequence Diagram

27
 2010 E.C
Web based criminal Record System

Figure 5: Posts Missing Criminal Sequence Diagram

28
 2010 E.C
Web based criminal Record System

2.3.3. UML Activity diagram

Activity diagram is basically a flowchart to represent the flow from one activity to another
activity. The activity can be described as an operation of the system.

The control flow is drawn from one operation to another. This flow can be sequential, branched,
or concurrent. Activity diagrams deal with all type of flow control by using different elements
such as fork, join. (8)

Figure 6: View post criminal Activity Diagram

29
 2010 E.C
Web based criminal Record System

Figure 7: Register Accuser Activity Diagram

30
 2010 E.C
Web based criminal Record System

Figure 8: View Criminal Activity Diagram

31
 2010 E.C
Web based criminal Record System

2.3.4. Analysis Class Diagram

Class diagrams are one of the most useful types of diagrams in UML in order to clearly map out
the structure of a particular system by modeling its classes, attributes, operations, and
relationships between objects.(9)

Web Based Criminal Record System Analysis Class Diagram

Missing Ciminal HR Manager Adminstrator

* 1
-MID Police Head
-Photo
-Lost Date
Post +Regster Employe() +create Account()
1 +View User()
-Post Date +Update Employee() +view account()
+View Comment()
Inh

* +view employee() +Update account()

-woreda +Assign placement()
er

-Description 1 +View User()

ite

w
1

Inherite
1
vie *

manage
1

manage
1 1
gn

* 1
Assi

has
Post

Employee
View

ie
ew

* 1 *
w

* -ID
Vi

-FName

View
Placement -Mname Account
* Notice
-Lname
-Placement ID -title * * 1 -User_ID
-sex has 1
-Police_ID -User_Name
V

-Date -Office_No
ie

Comment -Date -Password

w

-sender -User_Type
-Email -firstname -file -Email -User_Type
-Date -fathername -Phone_N
ite

-Status
-Description -gfathername -Age
er

Vie -Photo
Inh

-sex
* w 1
-phoneno *
-Kebele
View

1 1 Account Request Crime

-sendeid -CID
* 1 send -complaintid -Crime_Type
1
Inh
Give

-case -Crime_Level
er

* -Date
View

* Preventive Police
ite

Register -Kebele
* -village
Customer +View Nomination() 1 -month
-CID 1 +view Criminal() -photo
V

-Fname +Register Criminal()

ie

-description
w

-Mname +View Placement()

-Lname +view complain() 1

View
-Sex *
-City * Order
*
manage

-Kebele -orderid *
rd

Detective Officer
-Phone_ No
er
ew

-Crime_Type
-Age *
Vi

-Crimelevel
ew

-Education_Level 1 +manage accused() 1

-crimecommiteddate
Vi

-Job -appointmentdate +Manage accuser ()

-Birth_date -descrpition +manage witness()
1
Re

-Village 1
+order police()
1
gis

+Give Comment() Inhe

rite
te

+View post Criminal() 1

Regi

r *
r
Register

+send Nomination() te
gis
+Give Complaint() Re 1 Witness
ster

Inhe *
rite -WID:varchar(30)
Inhe

* 1 -Fname
Inhe

Accused
-Lname
rite
send

-Photo -Phone_No
rite

Accuser -Crime_Type
* -sex
-Description -Description -age
*
In

1
h

* -kebele
er

Nomination
it

Complain -Description
e

-Type FIR
-Case
-Description Complaint -accuserid
-Date Send
-Date -accusedid
request +Send Request() -witnessid
* +View Response() -crimetype
1 -crimelevel
-crime_commited_date

Figure 9: Web based Criminal Record system Analysis Class Diagram

32
 2010 E.C
Web based criminal Record System

CHAPTER THREE

3. System Design
Introduction
The term design describes a final system and the process by which it is developed it refers to the
technical specification that will be applied in implementing the proposed system. It also include
the construction of program and design of output, input, code, database and process of the system

System design is the transformation of the analysis model into a system design model. Up to now
we were in the problem domain. System design is the first part to get into the solution domain in
a software development.
The main purpose of system design is to determine how the system is going to build and to
obtain the information needed to direct the actual implementation of the system. It focuses on
understanding the model how the software will be built.

3.1. Design Class Diagram

Class diagram in the Unified Modeling Language (UML) is a type of static structure diagram
that describes the structure of a system by showing the system's classes,
 Their attributes,
 Operations (methods)
 And the relationships among the classes.
A class diagram is an illustration of the relationships and source code dependencies among
classes in the Unified Modeling Language (UML). It provides an overview of the target system
by describing the objects and classes inside the system and the relationships between them.

33
 2010 E.C
Web based criminal Record System

Web Based Criminal Record System Design Class Diagram

Missing Ciminal *
-MID varchar(50) 1 HR Manager Adminstrator
-lostdate date Police Head
Post
-postdated date
-woreda varchar(50)
+Regster Employe() +create Account()
+View User()
+Update Employee() +view account()

Inh
-Description text +View Comment()
1 +view employee() +Update account()
-photo blob

eri
+Assign placement()
+View User()

te

man
Inherite
1 * 1

vie
1 1
1

manage
1 1

age
*
gn

V
ie

has
*
Assi

w
Post
View

* * 1 *
Inherite

** Employee
Vie

-ID varchar(50)

View
* Placement Notice -FName varchar(50) Account

V
ie
-Police_ID varchar(50) -title varchar(50) -Mname varchar(50)
1 -User_ID varchar(50)

w
-Lname varchar(50) has 1
Comment -Kebele varchar(50) -Date date -User_Name varchar(50)
-sex varchar(50)
-Date date -sender varchar(50) -Office_No varchar(50) -Password varchar(100)
-Email varchar(50) -firstname varchar(50) -file text -User_Type varchar(50) -User_Type varchar(50)
-Date date -fathername varchar(50) -Email varchar(50)
-Description text -Status varchar(50)
-gfathername varchar(50) -Phone_No int
-sex varchar(50) * Vie 1
-phoneno int w*
te

1 1
eri

Account Request
View

Crime
Give

Inh

-sendeid varchar(50) -CID varchar(50)

1 -complaintid varchar(50) -Crime_Type varchar(50)
* 1 send
-case text -Crime_Leve varchar(50)l
View

*
-Date date
* Preventive Police
Register -Kebele varchar(50)
* -village varchar(50)
Customer +View Nomination() 1 -month varchar(50)
V

Inh
+view Criminal() ie
-photo blob
-CID varchar(50) 1 w

eri
V

-Fname varchar(50) +Register Criminal() -description text

ie

te
w

-Mname varchar(50) +View Placement()

+view complain() 1
-Lname varchar(50)
-Sex varchar(50) * *

View
w

Order *
Vie

-City varchar(50) *
manage

or

-Kebele varchar(50) -orderid varchar(50) Detective Officer

de

-Phone_ No int -Crime_Type varchar(50)

w

r
Vie

-Crimelevel varchar(50)
-Age int 1* +manage accused() 1
-Education_ Level varchar(50) -crimecommiteddate varchar(50)
-crimecommiteddate date +Manage accuser ()
-Job varchar(50)
-Birth_date date -appointmentdate date +manage witness()
1
-descrpition text +order police()

Re
-Village varchar(50)
1 Inhe 1

gis
+Give Comment() rite 1
e r ter 1

te
+View post Criminal()
ist gis
Regi

r
+send Nomination() eg R e
R *
+Give Complaint()
ster

Witness
Inh 1
eri * Accused -WID:varchar(50)
te
Inhe

-Fname varchar(50)
-Photo blob
send

Accuser -Lname varchar(50)

rite

-Crime_Type varchar(50) -Phone_No int

-Description text -Description text -sex varchar(50)
*
1 -age int
In
he

Nomination -kebele varchar(50)

r

FIR
ite

-Type varchar(50) * * -Description text

-Description text -accuserid varchar(50)
-Date date -accusedid varchar(50)
Complain Send Complaint -witnessid varchar(50)
-Case varchar(50)
request -crimetype varchar(50)
-Date date +Send Request() -crimelevel varchar(50)
+View Response() -crime_commited_date date
* 1

Figure 10: Web Based Criminal System Design Class Diagram

34
 2010 E.C
Web based criminal Record System

3.1.1. Description of design class diagram

Table 9: Complaint class diagram Description
Attribute Purpose Data type
CID Represent as complaint unique identifier Varchar(50)
Fname Represent the name of the complaint itself Varchar(50)
Lname Represent the complaint father name Varchar(50)
Sex Represent the sex of the complaint Varchar(50)
Education status Represent Education Level of the complaint Varchar(50)
kebele kebele the complaint lived Varchar(50)
Phone_no Represent the complaint phone address int
Job Represent the compliant occupation Varchar(50)
photo Represent the compliant identification image Varchar(50)
email Represent the compliant email address Varchar(50)
Work place The reason the complaint want to complain Varchar(50)
date Represents thedate that complaint send their request date
description The detail explanation of the case. text
Table 10: Crime Class diagram Description
Attribute Purpose Data type
Criminal ID Represent ID of crime committed person Varchar(50)

Crime Type Represent which type of crime the criminal Varchar(50)

committed
Crime Level Represent the level of the crime Varchar(50)
Crime committed date Represent the date the crime occurred date
Photo Describe crime Represent to Describe the crime by image Varchar(50)
kebele kebele the crime occurred Varchar(50)
Crime committed month Represent which month the crime occurred Varchar()
description The detail explanation of the case. text

35
 2010 E.C
Web based criminal Record System

Table 11: Placement class diagram Description

Attribute Purpose Data type
PID Represent as preventive Police Id describes full information Varchar(30)
about the police that assigned to the given place
kebele kebele the preventive police assigned Varchar(30)
date Represents the date that the police head assign placement date
Table 12: method of detective Officer

Method/operation Function
View Criminal () Used to view criminals send from preventive police
Register accuser() Used to record the accuser
register accused() Used to register the accused
Order preventive police() Used to order preventive police.
Register witness() User to record the witness information

3.2. Database design /Physical data model

The purpose of physical design is to translate logical description of data into technical
specification for storing and retrieving data the goal is to create design for storing data that will
provide adequate performance and data integrity, security and recovery.

Physical data model represents how the model built in the database. A physical database model
shows all table structures, including column name, column data type, column constraints,
primary key, foreign key, and relationships between tables. In our system sample database
structure is the following.

36
 2010 E.C
Web based criminal Record System

Table 13: Accuser Database Table

37
 2010 E.C
Web based criminal Record System

Table 14: Employee Database Table

38
 2010 E.C
Web based criminal Record System

Table 15: Missing Criminal Database Table

39
 2010 E.C
Web based criminal Record System

3.3. User Interface Design

User interface design is the design of System with the focus on the user's experience and
interaction. The main target of user interface design is to make the user's interaction as simple
and efficient as possible.

In this system users will communicate with the system through the following user interface links,
button, forms and pictures that described under the system.The following some interface design
describe the logical characteristics of some interfaces between the system and the users.

Figure 11: Preventive Police page user interface

40
 2010 E.C
Web based criminal Record System

Figure 12: Preventive Police page user interface

41
 2010 E.C
Web based criminal Record System

Figure 13: Police head post missing person user interface

42
 2010 E.C
Web based criminal Record System

Figure 14: Police head post notice user interface

43
 2010 E.C
Web based criminal Record System

3.4. System Architecture

3.4.1 Deployment Diagram

Deployment diagram shows execution architecture of systems that represent the assignment
(deployment) of software artifacts to deployment targets (usually nodes). Nodes represent either
hardware devices or software execution environments.

Deployment diagrams are used to model the hardware that will be used to implement the system
the link between different item of hardware and the deployment of software on to that hardware.

Through deployment diagram we are able to model

 Where hardware is located

 Where software is located
 What is the communication path between various hardware parts

Figure 15: Deployment Diagram

44
 2010 E.C
Web based criminal Record System

CHAPTER FOUR

IMPLEMENTATION
Introduction
Systems implementation is the final stage of system development process that used to converting
logical design in to application using selected programming languages. To develop this project
the team project uses the following programming languages PHP, HTML, JavaScript and CSS.

4.1. Overview of the programming language used

PHP is a server side scripting language that is embedded in HTML. It is used to manage dynamic
content, databases, session tracking, even build entire e-commerce sites.

It is integrated with a number of popular databases, including MySQL, Postgre SQL, Oracle,
Sybase, Informix, and Microsoft SQL Server.

PHP works well for a database-driven Web site. PHP scripts in the Web site can store data in and
retrieve data from any supported database. PHP also can interact with supported databases
outside a Web environment.

4.2. Algorithms Used

1. Register Employee
Logged page
Click on register Employee link
Registration form is displayed
Fill Employee profile data
Click on register button
If (valid)
Display successful message.
Else display invalid input message

45
 2010 E.C
Web based criminal Record System
2. Update account
Logged page
Click on manage account link
List of account is displayed
Click on Edit link
Form displayed
Fill new information for the user
Click on update button
If (valid)
Display successful message.
Else display invalid input message

4.3. Sample Codes

Sample code for Login

<?php
include("connection.php");
?>
<html>
<head>
<title>
Login Page
</title>
</head>
<body>
<table>
<form action="" method="post">
<tr><th><h1>Login <h1></th></tr>

46
 2010 E.C
Web based criminal Record System

<tr><td><label>User Name:</label></td></tr>
<tr><td><input type="text" name ="un" placeholder="Enter User Name"
required style="height:30px; width:180px;"></td></tr>
<tr><td><label>Password:</label> <input type="password" name ="pass"
required placeholder="*********" required
style="height:30px; width:180px;"></td></tr>
<tr><td><input type="submit"name="login"value="login" style="height:30px;
width:80px;background-color:#c0cbcd">&nbsp;&nbsp;&nbsp;&nbsp;
<input type="reset"value ="Reset" style="height:30px; width:80px;background-
color:#c0cbcd"></td></tr>
<tr><td><p>Forget<a href="#">Password?</p></td></tr>
</form>
</table>
<?php
function encryptpassword($password )
{
$cryptKey='qJB0rGtIn5UB1xG03efyCp';
$passwordEncoded= base64_encode( mcrypt_encrypt(
MCRYPT_RIJNDAEL_256, md5( $cryptKey ), $password,
MCRYPT_MODE_CBC, md5( md5( $cryptKey ) ) ) );
return( $passwordEncoded );
}
if(isset($_POST['login']))
{
$un=$_POST["un"];
$pass=$_POST["pass"];
$plaintext_password=$pass;

47
 2010 E.C
Web based criminal Record System

$password=encryptpassword($plaintext_password);
if($con)
{
$sql="select * from account where username='$un' and
password='$password'";
$matchfound=mysql_query($sql,$con);
$userexist=mysql_num_rows($matchfound);
if($userexist>0)
{
while($row=mysql_fetch_assoc($matchfound))
{
//$username=$row['UName'];
$userid=$row["userid"];
$un=$row["username"];
$pw=$row["password"];
$role=$row["role"];
$status=$row["status"];
$pw_status=$row["password_status"];
}
if($pw_status=="unchanged")
{
$_SESSION['userid']=$userid;
$_SESSION['oldpassword']=$pass;
header("location:change_password.php");
}

48
 2010 E.C
Web based criminal Record System

else
{
$sqll="select * from employee where emp_id='$userid'";
$matchfound1=mysql_query($sqll,$con);
$row1=mysql_fetch_assoc($matchfound1);
//session
$eid=$row["emp_id"];
$firstname=$row["firstname"];
$fathername=$row["fathername"];
$gfathername=$row["gfathername"];
$photo=$row["photo"];
$email=$row["email"];
$fullname=$firstname." ".$fathername;
$_SESSION['fullname']=$fullname;
$_SESSION['sun']=$un;
$_SESSION['spw']=$pw;
$_SESSION['srole']=$role;
$_SESSION['seid']=$eid;
$_SESSION['sphoto']=$photo;
$login_time = date("h:i:s");
$_SESSION['login_time']=$login_time;
if($role=="Adminstrator" && $status=="Active")
header("location:Adminstrator.php");
else if($role=="PoliceHead" && $status=="Active")

49
 2010 E.C
Web based criminal Record System

header("location:PoliceHead.php");
else if($role=="DetectiveOfficer" && $status=="Active")
header("location:DetectiveOfficer.php");
else if($role=="PreventivePolice" && $status=="Active")
header("location:PreventivePolice.php");
else if($role=="HRManager" && $status=="Active")
header("location:HRManager.php");
else if($role=="Complaint" && $status=="Active")
header("location:Complaint.php");
}
}
else
{
$x='<script type="text/javascript">alert("Please Enter Correct Username and
Password!");
window.location=\'index.php\';</script>';
echo $x;
}
}
else
echo "<div id=error>Connection Failed!!";
}
?>
</body>
</html>

50
 2010 E.C
Web based criminal Record System

CHAPTER FIVE

5.1. Testing
Testing is a process to show the correctness of the program and designed to analyze the logic
used in the implementation of the System.
Testing by Requirements: - The requirements that are tested by the group member during the
implementation are correctness, performance, accuracy, security and others.
Testing the correctness: - correctness determines how users can interact with the software and
how the software should behave when it is used correctly. Users can easily interact with the
application since it has easily understandable interface and the application responds correctly.
Performance testing: The team members measures the system parameters in terms of System
responsiveness with related to time avail ability, and scalability.

Security Testing: The team members insure the security of the system that authenticates when
user login to the correct user name and password. The system allows only authorized users to
login users that have previously created account through user name and password. The system
also uses session management, time management, and change password if he/she is login for the
first time.

51
 2010 E.C
Web based criminal Record System

Figure 16: Security Testing

52
 2010 E.C
Web based criminal Record System

Chapter six (6)

6. Conclusion and Recommendations

6.1. Conclusion

As a central part of this study, a detailed analysis and design was held to develop automated
criminal records system for Debre Markos police station. The project is aimed at developing a
simple and user friendly automated criminal records system for Debre Markos police station. The
project made is almost simple, interactive and time saving system and this project initiates us to
think wide and hopefully. Before this time it is thought that developing projects in different
programming languages is a very match difficult work. But at this time it becomes easy to
understand and develop such systems.

6.2 Recommendations
The system that we develop is a web based criminal record system for Debre Markos city police
station. While doing this system the team members has faced different challenges. But by the
cooperation of all the group members the team is now able to reach to the final result. I.e. all the
group members strongly fight these challenge and take the turn to the front. We strongly
recommend for everyone involved in criminal record system; our new system has provided a
better service than the existing system by forming better interaction among them. Our
recommendation to other system developers is that to develop an android part for the system.

6.3 Future Enhancement

 The system will be developed by using android in a way to support mobile users.
 For the future, technology user can send sms message for police to nominate criminal
case.
 The system will be including Amharic language for uneducated person.

53
 2010 E.C
Web based criminal Record System

Appendix

Action-An action is the fundamental unit of behavior specification and represents

some transformation or processing in the modeled system, such as invoking a
method of a class or a sub activity.
Activity diagram-a diagram that describes procedural logic, business process and
work flow supporting parallelism.
Activity -carrying out behavior in a State machine diagram.
Actor -a role that a user takes when invoking a use case. Also see actor modeling.
Class-the primary declarative construct of Object-Oriented Programming; a
cohesive unit of Attributes and Operations; a compile-time template for an Object
Class diagram- a type of static structure diagram that describes the structure of a
system by showing the system's classes, their attributes, and the relationships
between the classes.
Sequence diagram-describes the Messages sent between a numbers of
participating.

54
 2010 E.C
Web based criminal Record System

Reference
[1]. “introduction about impact of information technology," 23: December 2010. [Online].

[2]. "about System Requirement Analysis," 14 December 2010. [Online]. Available:

http://techpedia.sristi.org/parojects/online-crime-management-system/185558

[3]. "about Non-Functional System Requirement Analysis," 14 December 2010. [Online].

Available:

http://www.scaledagileframework.com/nonfunctional-requirements/

[4]. "about System Requirement Analysis," 14 December 2010. [Online]. Available:

https://books.google.com.et/books/about/System_Requirements_Analysis.html?id=FkpqAnHUN
LYC&redir_esc=y

[5]. “UML Use Case Diagrams," 21 December 2010. [Online]. Available:

http://agilemodeling.com/style/useCaseDiagram.htm

[6]. “Use Case Description," 21 December 2010. [Online]. Available:

http://www.dummies.com/business/business-strategy/how-to-create-use-case-description-for-
your-business-analysis-report/

[7]. “about Sequence Diagram,” Accessed 28 December 2010.

[Online]. Available: http://www.agilemodeling.com/artifacts/sequenceDiagram.htm

[8]. “about UML Activity Diagram,” Accessed 28 December 2010.

https://www.tutorialspoint.com/uml/uml_activity_diagram.htm

[9]. “aboutUMLAnalysis class Diagram,” Accessed 30 December 2010.

[Online]. Available: https://www.lucidchart.com/pages/uml-class-diagram

[10]. “about establishment of police in Ethiopia,” Accessed 19 may 2010.

http://www.federalpolice.gov.et/web/guest/background-information

55