Mettu University: Department of Management Information System

METTU UNIVERSITY Department Of Management Information System Page i
ACKNOWLEDGMENT
This project was started with the high organized team group. We express thanks and
gratitude to our advisor INSTRACTER TIRETE an instructor in Mettu University for his day
to day encouragement, support and guidance in carrying out the project. We would like to
express gratitude and indebtedness to our department staff members for their valuable advice and
guidance. Without them this project would not have seen the light of the day. In addition to this
we would like to tanks mettu town mettu police station police officers, police members and
workers of the station who gave any information concerning about our project and their
politeness during interviews. Finally, we would like to thank our parents for their inspirational
encouragement and moral support throughout our study of higher institute and all the
administration body of Mettu University
METTU UNIVERSITY Department Of Management Information System Page 1

ABSTRACT
Mettu police station is early established police station in Mettu town. It is a
well-organized police station and stands for serving local communities living with
high life freedoms and security of their property as well. For the purpose of
preventing criminal activities, the station works regardless of crime recording,
making judgments over criminals and assign legal punishments towards their
wrong actions. The police station limited on manual works. This has limitation on
controlling the work securely, for declaring the result on time, and has high
consumption on resources. Manual data processing system is not fast and efficient
way to accomplish tasks within short period of time and it is boring. To overcome
this problem we are proposing the new automated system for the station
CHAPTER TWO
1. Introduction
In this chapter overview of the existing system, overview of the proposed system
functional and non functional requirement of the system will be discussed and modeled using
unified modeling language(UML) models.

The proposed system documentation involves the requirement elicitation, where the team
members gather requirements of the system from user, analysis of the requirement that focuses
on the functional, object and dynamic modeling (state diagram), system design, object design
and testing of the system. The project is intended to advocate for the need of Mettu Town police
station to use facilitated computerized police-crime record management system. The project has
got high involvement of users because the approach employed is object oriented paradigm,
which a user based software development activity. As a result the team member believed that the
user will have the expected satisfaction of the service provided by the police station. Therefore,
the team member recommends Mettu Town police station migrate the manual system to the
computerized crime record management system to facilitate their service and benefit of the
station.
2.1 Player of the existing system ( actors)

The major players of the current system are:
 Administrator
 Police members
 User
Role of Administrator:
The following activities are performed under the Administrator of Mettu town police
Station crime manual recording system.
 Maintain crime information
 Administrating the station
 Collecting daily, monthly and manual repots from different
departments
 Producing organizational reports

Role of polices
 Controlling criminal activities.
 Arresting crimes.
 Accepting legal complaints of individuals and directing to Detective
managers.
 Resolving conflicts between individuals with legal punishment and
arbitrate them.
 Searching criminals depending on evidences.
 Finding evidences for searched criminals.
In the current system of Mettu town police station crime record system the following major
activities are performed manually:
 Daily recording of crimes’ information
 Manual preparation of documents
 Controlling of criminal activities
 Detecting of crimes and preventing illegal actions
 Preparation of manual way of crime reports
 Arresting of crimes who did wrong things
 Accepting of formal complaints about individual whose personal rights
are violated
 Serving peoples with legal judgments and negotiating each other
 Solving conflicts with traditional conflict resolution mechanism like by
using arbitration
 Maintain crime documents or files for current and future use
 Making decisions based on the information and passed judgments
2.2 Major function of the Existing System

The main purpose of studying the existing system is to develop a new system which
efficiently performs activities than current one and understanding existing problems. To solve
problems document analysis, form designs, some
In general the reason behind for studied the existing system: constraints and rules
of the existing system in corporated.

 To identify the existing system problems.
 To identify the scope and limitation of the new system.
 To know the business rules and constraints of the department
 To design the new proposed system based on the boundary or the total activity of
the existing system of the department.
 To determine the system user requirement.
 To understand the internal organizational policies, influences & inclination of key
police experts in different subjective, critical incidents in the organizations
history, informal organizational structure.
 To understand organizations strategies & facts, short & long term strategies,
business values & missions.
 To understand how work officially gets done in the organization this include
identifying:-
 Terminologies, abbreviations, and acronyms used
 Policies& guidelines that describe the nature of the business
 Standards, procedural manuals and the work environment.
 It operates the sample business forms and reports
 Job descriptions.
2.3 Work flow of the Existing System

In any business documents and forms are the fundamental for the existence of different process. The
existing Mettu Crime Management System uses the following forms and documents.
GucaajechaHimataa (Midhamaa) ittinfudhamu
Maqaaguutu------------------------------------------------------
Umuriiwaggaa------------------------ salaa-----------------------
Holii------------------------ sad/barumsaa--------------------------
HaalaMaatii-----------amantaa---------------------------------

Lammumaa-------------- sabmmaa------------------------------
TessooNanoo---------------- Godinaa-------------------------
Aanaa--------------------- Gandaa----------------------------------
Lakka/Mana--------------Lakka Bilbilaa-----------------------
Ani maqaa fi tessoo Koo armaanolittiKanibsamehara’aguyyaa / /
ganama/Guyya/keessaasa’aatiyommmuta’ukutaagareeqorannaayakkaattidhiyaadhejechahimata Koo
armangadittifufee nan kenna.
Jechinarmaanolittikennejechaahimaatakoodhugaata’uuisaadubbisee (naafdubbifamee)
mallattookootiin nan miirkaneessa.
2.4 Problem of the Existing System

Manual processing such as storing, retrieving of data and information, the current system has
the following problems:
 Performance problem
The current system unable to perform tasks and activities with efficient and required time .It is
tedious and not fast, accurate communication among each departments.
 Information Problem
-Lose of data may occur.
-Due to manually collecting of data there is a redundant record and inconsistency problems.
-In accuracy of data and information may produced
-Incorrect information leads to poor decision making
-Poor flow of information between departments
 Data storage problem
-Lack of a well organized database system
-Data are not easily accessible due to its integration and placed in different location
- Difficult to change and edit
-Data redundancy that leads to inconsistency
 Efficiency Problem
The efficiency of the existing system not optimal, because
-Storing, locating of data takes much more time
-Redundancy flow of information, data can be inputted, processed and produced as redundantly

as demands much time.
 Security and control problem
The current system can be accessed by unauthorized person, since it doesn’t have any
authentication and authorization system.
2.5 Alternative Solution to solve the existing system Problems

After analyzing the problems in the existing system, our project team identified and evaluated
the following alternative solutions:
 C.R.I.M.S particularly within the Station of sub-department

 Automating the system using computer software application
 Changing the manual system into Automated system.
2.6 Overview of the proposed system

As previously mentioned in statement of the problem, there are a lot of problems associated
with the current system of the crime record system. The main aim of the proposed system is to
implement crime recording which allows users to use in simple way, check the availability of
police records and overcome to those problems. The proposed system accompanied on the
simple application of crime data management and database control mechanisms. The system
addresses problems which were incorporated in the existing system.
2.7 Requirement description

A requirement is a feature that the system must have or a constraint that it must satisfy to be
accepted by the station. This stage determines the needs of everyone who will be the user of the
proposed in this system.
Importance of requirement phase is:
Different users have different expectations forms system requirement
specification document
 Users, customers
 Software developers, Testers, User manual writers
 Management(developer side)
Poor requirement definition leads to several problems.
Frequent “change” to requirement

More customer/developer disputes ,like communication problems
More iteration due to improper documentation
Fault decision making and incorrect results
Generally the requirement of the new system can be viewed as:
Functional and
Non functional requirements
2.7.1.Functional requirements
The Functional requirement is concerned with actual performance of the system that is going to
be developed. Functional requirements describe the functionality or service provided by the new
system:
Recording of crimes to the database was the main process for the system.
Reduce redundancy, inconsistency and integrity problem of data and information
maintaining detail of crimes data usual error like record duplication will be prevented by
the proposed system
The high effort that is required in maintaining the file controlling section is made
Easy, because the system is easily maintained and not complicated
The system is capable of reducing the time that spent the existing crime record
management in practice.
The tedious process that is observed in transferring crime’s records manually be avoided
by the system
Validates data entry for correctness.
Updates itself when it gets new data.
Provision for query analysis.
Presence of centralized database and organized records.
Facilitate timely management decision making because the system should not take much
time to retrieve crime information.
The system allows enabling to make report

2.7.2 Nonfunctional requirements
This are most critical than the functional requirements of the system. In order to identify the
non-functional requirements of the proposed system the following categories are used as
framework.
2.7.2.1 Performance
The system shall be available all time of the working day. The system shall respond in a very
minimal duration of response time.
2.7.2.2 Hard ware consideration
 The system is not able to run on the operating system like UNIX, Linux,
because it will be developed on WIN- 7 application.
 The entire user interface of the system will be windows based.
 The system is not able to have backup and recovery of file.
 The application of the proposed system is limited only to fit for stand
alone setup or one computer and not for a network connection setup.
 The design and application of the proposed system shall be limited only to
present set up of the HBPCRS.
 The proposed system does not include maintenance service.
 The proposed system does not include training.
2.7.2.3 Security
 The system will promote username and password to login into the system.
2.7.2.4 Maintainability
 The system prevents damage of data from simultaneous change and system
failure.
 The system shall restore the system to its last consistent state.
2.7.2.5 Quality
 The system shall store the data in the relation format.
 The system will protect the data against unauthorized disclosure of information.

Chapter Three
Analysis
3.1 Introduction
The proposed system contains different functions performed in the police office. This
chapter describes the use case diagram, use case documentation and sequence diagram for each
use case, activity diagram, analysis level class diagram, user interface prototype and
supplementary specification about the proposed system.
The project team used sources for the analysis such as written requirements statement, a
formal vision document, and interviews with manager and employee. The system may be divided
into multiple domains, representing different business, technological, or other areas of interest,
each of which are analyzed separately.
3.2 Actor identification

Police: - The police are primarily responsible for the maintenance of public order, prevention
and detection of crimes in the Kombolcha Town. Polices are responsible when the crime prevail;
the manager informs where the crime is taken place and polices are going to that place and attack
the criminal.
Administrator:-control the whole systems and administer according to the users information to
transfer the information to the managers. Admin also receive different data’s from the people and
forecast and process these data’s.
Users:-users are that informs the crime to see or the injured. They also interacting the system
externally.
3.3 Use case identification

 Login
 Record new crime
 View record
 Manage profile
 View police sation
 Update
 Delete
 About Us

 photogallery
3.4 Use case diagram

CRIME RECORD INFORMATION AND MANAGEMENT SYSTEM (C.R.I.M.S)
Lo g in
>
R e c o rd ne w c>
c rime in
<<
Crime re c o rd
A d mini >> c
in
P o lic e
<<
s tira to r
V ie w re c o rd
>
nc >
>>
inc
<<i
D e le te << re p o rt g e ne ra te
>>
ud e
l
<inc
Use r
Ab o utU s
U p d a te
V ie w p o lic e
s ta tio n
<<
inc
>>l
P ho to g a lle ry
Ma na g e
p ro file s
Fig.3.1. use case diagram
3.5 Develop use case documentation
usecase documentation on view police station
Title View police station

Requirement ID UC.8
Actors User

Description The purpose of this use case is to view the police station details to report the
crime by using the site contact domain or to get information about station.
precondition 1. User should know the site domain to report criminal action.
2. Selection of police station.
Post condition The user reports an crime by filling the proper personal detail.
course of action Actor action Systems action

Step 1. Users view the page. Step 2. The system doesn’t
Step 3.The page displays display if user do not enter
Step 4. Then fill compliant detail and crime correct domain name of
information properly. police station site.
Step 5. If user doesn’t fill the
necessary accident
information error message
will displayed.
Alternate course If there is a problem to enter the domain name the page does not display and
of action access.
3.6 Class diagram

 Introduction for class diagram
Class diagram shows the static structure of data and the operations that act on the data, i.e. it
shows the static structure of an object-oriented model the object class, their internal structure,
and the relationships in which they participate.
Class diagram represents a detailed view of a single use case, shows the classes that participate
in the use case, and documents the relation ship among the classes. It is a logical model, which
evolves into a physical model & finally becomes functioning information system. Class diagram
evolve into code modules, data objects, & other system components.
Class diagrams describe the structure of the system in terms of classes and objects. Classes are
abstractions that specify the attributes and behavior of a set of objects. Objects are entities that

encapsulate state and behavior.
 Draw Class diagram
Class Modelig
digram
* *
*
compliant _detial
-C_ID: int crime_record
-C_Complainant: -id: int
varchar -name: varchar
-C_Crime_Type: varchar -address: varchar
1
-C_Date: int * -crime_type: varchar
-C_Contact: int 1 -crime_registration:
-C_Age: int admin varchar
-C_Suspect_Name: -admin_id :tinyint -period: int
varchar -username : varchar -details: int
-C_Address: varchar -password: varchar -
-date: varchar
-rport detail() -set _crimeDetail()

-view_profile() -set_crime()
-send detail() -get_ detail()
-exit() -send_message()
-Update_file() -record_detail()
-add_file() -exit()
-delete_()
-exit()
*
*
police_office
-id: int *
-name: varchar
-address: text
-contact_no:: varchar *
-birthdate: date
-sex: varchar
-rank: varchar
-view_office()
-generate_report()
3.7 Sequence diagram
 Introduction for sequance diagram

Asequece diagram is an interaction diagram that emphasizes the time ordering of
messages.Build for each usecase but if you think that some usecase are clear to understand you
my not need to develop asequence diagram. But you need to explain this explicity
Fig.3.2.Login sequence diagram

Fig.3.3.View record sequence diagram

Administrator Add Form Add Controller Error Message Police Database
Record Form
Record New
crime
Request detail
Enter detail
Validation
Store detail
Confirm Message
Invalid Input
Request detail
Invalidate
Re-regster

3.8 Activity diagram
Activity diagram discribe the work flow of behavior of a system. They are typically used for
business process modeling. For modeling the logic captured by asingle usecase model

admin login
New crime
Register activity
New record form display
Admin fillregistration form
[correct] [incorrect]
Validate input info
[correct] [incorrect]
Send success data User file error
Fig.3.9. New crime record activity diagram

Chapter Four
System design
4.1 Introduction
This section consists of the design goals and proposed system model. Functional requirements
are grouped in such a way that they could be constructed as sub systems and the non functional
requirements defined in the analysis are transformed into design goals.

 System design is the evaluation of alternative solution and specifications and also
construction of a detail computer based solution. System design is also called physical
design as it deals with implementation issues
Object oriented design is best suited to projects that will implement system using emerging
objects technologies to construct, manage, and assemble those objects in to useful computer
application.
4.2 Design goal
The new system is considered to be successful if it meets the following sets of criteria’s.
 User Interface: The user interface of the system should be easy to use by each user of
the system with little training.
 Documentation: System administrators and other users are provided with proper
documentation about the software’s features.
 Hardware Consideration: system should be able to work on Pentium IV computers.
 Performance: The system should be able to serve a number of users which are
expected to access it concurrently.
 Error Handling and Extreme conditions: The system should be robust enough to
handle error conditions and continue with normal operations.
 Availability: The system availability should be availale most of the time since it is
handling emergency situations.
 Security: The system should prevent the sensitive data from unauthorized access.
 Modifiable: The system should be designed in Object Oriented language so that
modification to some part of the system could not affect other parts.
4.3 Class type architecture

Layering is the concept of organizing our system design into layers or collection of classes that
fulfill a common purpose such as implementing our user interface or the business logic of our
system. Class type architecture provides strategy for layering the class of our system to distribute
the functionality of our system among classes.

Fig.4.1.Class type architecture diagram
4.4 Class Diagram


encapsulate state and behavior. Each object has an identity
 Databa Base Design Class Diagram
Class diagram

Chapter five
Implementation
5.1.Introduction
In this phase, the physical design specifications are turned into working computer code, and
then the code is tested until most of the errors have been detected and corrected. The error free
system is then installed to manage the intended activities. The detailed process involved in this
phase like coding, testing, and installation are explained below.
5.2 Component Diagram
 Introduction for component diagram

Component modeling is one part of object oriented design used to represent a software
module with a well-defined interface it can include both source code libraries and run time files.
Why the need?
Component diagram are implementation type diagram and are used graphically depict
the physical architecture of the software of the system. They can be used to show how
programming code is divided into modules or components and depict the dependencies
between those components.
It is basically used to implement to distribute the class in a system into larger scale,
cohesive components.
We have used a single component diagram to represent the components in our system.
The representation consists of.
 User interface classes.
 Entity and control classes and dependencies between them.

componet application
diagram server
clinte
server store
data
database
administrator
maintain server
«application»
profile
security
«infrastructure
»
crime
user
registrati
«application»
on
persistence
«infrastructure
»
mysql
police
«application»
view
record
police office BD
«database»
view
police
station
Fig.4.14.Component modelling diagram
5.3 DEPLOYMENT DIAGRA

Introduction for class diagram

encapsulate state and behavior. Each object has an identity
fig.4.2. Database design diagram

5.3 Deployment Diagram
Deployment diagram is implementation type diagrams that describe the physical
architecture of the hardware and software of the system. They depict the software
component, processors, and the device that make up the system’s architecture.
Why the need?
Deployment modeling is concerned with the physical operation of the application. This
includes issue such as the network lay out & location of the components on the network.
Deployment diagram is implementation type diagrams that describe the physical
architecture of the hardware and software the system. They represent the software
component, processors, and the device that make up the system’s architecture

deployment
diagram application
server
store
data
client database
server server
maintain
profile
administrator
«application»
security
crime
«infrastructure
registrati
»
on
user
«application»
persistence
«infrastructure
»
sql
my
view
police
record
«application»
view police office BD

police
station «database »
Fig.4.15.Deployment modelling diagram
Conclusions and Recommendation

7.1Conclusion and future work
As we have completed the project, we are sure the problems in the existing system will be
overcome by our system. The “METTU POLICE STATION CRIME RECORD INFORMATION AND
MANAGEMENT SYSTEM” process is specifically made computerized in order to reduce human
errors and to increase the efficiency. The main focus of this project is to lessen human efforts.
The maintenance of the records is made efficient, as all the records are stored in the database,
through which data can be retrieved easily. The navigation control is provided in all the forms to
navigate through the large amount of records. If the numbers of records are very large then the

admin can just type in the search string and perform different action on the searched profile. The
editing is also made simpler. The user just have to type in the required fields like type of crime,
place, and his own personal information and press the submit button.
The problems, which existed in the earlier system, have been removed to a large extent.
And it is expected that this project will go a long way in satisfying user’s requirements. The
computerization of the crime recording & profile management will not only improves the
efficiency but will also reduce human stress thereby indirectly improving human recourses.

Mettu University: Department of Management Information System

Uploaded by

Document Information

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

Mettu University: Department of Management Information System

Uploaded by

Copyright:

Available Formats

METTU UNIVERSITY Department Of Management Information System Page i

administration body of Mettu University

METTU UNIVERSITY Department Of Management Information System Page 1

Mettu police station is early established police station in Mettu town. It is a

preventing criminal activities, the station works regardless of crime recording,

unified modeling language(UML) models.

METTU UNIVERSITY Department Of Management Information System Page 2

2.1 Player of the existing system ( actors)

METTU UNIVERSITY Department Of Management Information System Page 3

2.2 Major function of the Existing System

METTU UNIVERSITY Department Of Management Information System Page 4

2.3 Work flow of the Existing System

GucaajechaHimataa (Midhamaa) ittinfudhamu

METTU UNIVERSITY Department Of Management Information System Page 5

2.4 Problem of the Existing System

METTU UNIVERSITY Department Of Management Information System Page 6

2.5 Alternative Solution to solve the existing system Problems

 C.R.I.M.S particularly within the Station of sub-department

2.6 Overview of the proposed system

2.7 Requirement description

METTU UNIVERSITY Department Of Management Information System Page 7

METTU UNIVERSITY Department Of Management Information System Page 8

2.7.2.2 Hard ware consideration

METTU UNIVERSITY Department Of Management Information System Page 9

3.2 Actor identification

3.3 Use case identification

METTU UNIVERSITY Department Of Management Information System Page 10

3.4 Use case diagram

Fig.3.1. use case diagram

3.5 Develop use case documentation

usecase documentation on view police station

Title View police station

METTU UNIVERSITY Department Of Management Information System Page 11

course of action Actor action Systems action

3.6 Class diagram

METTU UNIVERSITY Department Of Management Information System Page 12

 Draw Class diagram

-rport detail() -set _crimeDetail()

3.7 Sequence diagram

 Introduction for sequance diagram

METTU UNIVERSITY Department Of Management Information System Page 13

Fig.3.2.Login sequence diagram

METTU UNIVERSITY Department Of Management Information System Page 14

METTU UNIVERSITY Department Of Management Information System Page 15

METTU UNIVERSITY Department Of Management Information System Page 16

METTU UNIVERSITY Department Of Management Information System Page 17

New record form display

Admin fillregistration form

Validate input info

Send success data User file error

Fig.3.9. New crime record activity diagram

METTU UNIVERSITY Department Of Management Information System Page 18

METTU UNIVERSITY Department Of Management Information System Page 19

4.2 Design goal

4.3 Class type architecture

METTU UNIVERSITY Department Of Management Information System Page 20

4.4 Class Diagram

METTU UNIVERSITY Department Of Management Information System Page 21

 Databa Base Design Class Diagram

METTU UNIVERSITY Department Of Management Information System Page 22

5.2 Component Diagram

 Introduction for component diagram

Why the need?