PCRS in Wollo

Wollo University
Kombolcha institute of technology

Faculty of informatics
Department of information system
Automated Police crime record management system

For Kombolcha town Hasseb Ber police station
Submitted to the School of Graduate Studies of Wollo

University in Partial Fulfillment for the Degree of Bachelor
Science in information
system
Developed and submitted by:
Name Id no
1, Aragie wube 052/01
2, masresha gessese 075/01
3, simachew Addis 089/01
4, mola sintayehu 082/01
5, Elsa moges 062/01
Advisor, Demeke Shumeye (Msc)
June, 2012
ACKNOWLEDGMENT
This project was started with the high organized team group. We express thanks and
gratitude to our advisor Demeke Shumeye (MSC) an instructor in Wollo University for
his day to day encouraging, 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 tank Kombolcha town Hasseb Ber 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 wollo
university Kombolcha campus.
ABSTRACT
Wollo Universit KIOT student clinic established in KIOT. It is a well organized clinic
and stands for serving students living with high life freedoms and security of their life as
well and For the purpose of preventing different diseases .
It works regardless of patient information recording, making treatments over different
diseases and it gives refer for patients to another clinic or hospital for additional
treatments.
The clinic is 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 clinic. To alleviate the existing system problems we are using
programming tools like wamp server for interfacing and coding, MYSQLfor database
application, rational roses and Microsoft visio for designing different artifacts of the
project. Finally the overall activity of this project work is about design and
implementation of automated patient record management system for KIOT student
clinic.
Chapter one
Tables page
Table 1, Task breakdown activities and deliverables-………………………….……….4
Table 1.1 Cost estimation of materials and other expenses……………………………..10
List of charts
Chart1. Schedule of the project……………………………………………………..9
Chapter two
List of diagrams or figures
Fig 2.0 use case diagram ………………………………………………………………...21
Fig 2.1 User interface prototype for crime registration…………………………………25
Fig 2.2 User interface prototype for record crime information…………………………26
Fig 2.3 User interface prototype for generate report……………………………………26
Tables
Table 2.0 Class responsibility collaborator card for Detective team………………......25
Table 2.1 Class responsibility collaborator for Administrator…………………………25
Table 2.2 Class responsibility collaborator for information Desk……………………..26
Table 2.3 Class responsibility collaborator for crime class…………………………….26
Table 2.4 Class responsibility collaborator for Accused class………………………....26
Table 2.5 Class responsibility collaborator for Exhibit class…………………………..26
Table 2.6 Class responsibility collaborator for Witness class…………………………..27
Table 2.7 Class responsibility collaborator for Plaintiff class…………………………...27
Table 2.8 Class responsibility collaborator for Update information………………….27
Table 2.9 Class responsibility collaborator for Generate report………………………..27
Chapter three
List of diagrams or figures
Fig 3.0 Use case diagram for the system………………………………………………...30
Fig 3.1 A UML sequence diagram for Security login…………………………………...37
Fig 3.2 A UML sequence diagram for new crime registration..…………………………38
Fig 3.3 A UML sequence diagram for update crime registration ………………..……..39
Fig 3.4 A UML sequence diagram for generate registration report……..………………39
Fig 3.5 A UML sequence diagram for record crime information……………………….40
Fig 3.6 A UML sequence diagram for update crime information……………………….40
Fig 3.7 A UML sequence diagram for generate record report…………………………..41
Fig 3.8 A UML sequence diagram for generate Administration report…………………41
Fig 3.9 Conceptual class diagram for main component of the proposed system………..49
Fig 3.10 User interface prototype for login screen………………………………………42
Fig 3.11 User interface prototype for main menu screen……………………………….43
Fig 3.12 User interface prototype for Detective screen………………………………….43
Fig 3.13 User interface prototype for Information Desk screen…………………………44
Fig 3.14 User interface prototype for Administrator screen……………………………..45
Fig 3.15 User interface prototype for crime registration screen…………………………46
Fig 3.16 User interface prototype for Accused registration screen…………………….47
Fig 3.17 User interface prototype for Plaintiff registration screen………………………48
Fig 3.18 User interface prototype for Witness registration screen………………………49
Fig 3.19 User interface prototype for Exhibit registration screen……………………….49
Fig 3.20 User interface prototype for user account screen………………………………50
Fig 3.21 User interface prototype for change user account screen………………………51
Chapter four
List of Tables
Table 4, Description of crime class attributes……………………………………………59
Table 4.1, Description of Accused person class attributes………………………………59
Table 4.2 Description of Exhibit class attributes………………………………….……60
Table 4.3 Description of Witness class attributes………………………………………61
Table 4.4, Description of Plaintiff person class attribute…………………………….…62
Table 4.5Crime registration table for police crime record management system……..84
Table 4.6 Plaintiff table for police crime record management system……………….85
Table 4.7 Accused table for police crime record management system………………85
Table 4.8 Exhibit table for police crime record management system………………..86
Table 4.9 Witness table for police crime record management system……………….86
Table 4.10 Relationship table of Detective main form table for police
crime record management system ……………………………………………………87
Table 4.11 Administrator table for police crime record management system……….88
List of diagram or figuers

Fig 4.2, A UML state chart diagram for crime during crime registration. ……………63
Fig 4.3 A UML state chart diagram for Update crime registration during
Crime Registration……………………………………………………………………….63
Fig 4.4, A UML state chart diagram for generate registration report during report
Generate………………………………………………………………………………….64
Fig 4.5, A UML state chart diagram for record crime information during
information Recorded……………………………………………………….………….64
Fig 4.6, A UML state chart for update record information during crime
information updated………………………………………………………………….65
Fig 4.7, A UML state chart diagram for Generate administration
report during Administration report generated……………………………………….65
Fig 4.8, A UML collaboration diagram for Detective security login Basic
course of Action…………………………………………………………………….…66
Fig 4.9, A UML collaboration diagram for Detective security login Alternative
course of action……………………………………………………………………….67
Fig 4.10, A UML collaboration diagram for Information Desk security login ……...67
Basic Course of action. ……………………………………………………………….67
Fig 4.11, A UML collaboration diagram for Information Desk security
Login Alternative course of action. …………………………………………………..68
Fig 4.12, A UML collaboration diagram for Administrator security login
Basic course of action…………………………………………………………………68
Fig 4.13, A UML collaboration diagram for Administrator security

login Alternative Course of action………………………………………………………68
Fig 4.14, A UML collaboration diagram for new crime registration
Basic course of Action………………………………………………………………….69
Fig 4.15, A UML collaboration diagram for Register New crime
Alternative course of action……………………………………………………………..69
Fig 4.16 , A UML collaboration diagram for Update crime registration
Basic course of action. ………………………………………………………………….70
Fig 4.17, A UML collaboration diagram for Update crime registration
Alternative course of action…………………………………………………………..….70
Fig 4.18, A UML collaboration diagram for Generate registration report
Basic course of action……………………………………………………………………71
Fig 4.19, A UML collaboration diagram for Generate registration report
Alternative course of action……………………………………………..……………….71
Fig 4.20, A UML collaboration diagram for Record crime information
Basic course of action………………………………………………………..………….71
Fig 4.21, A UML collaboration diagram for Record crime information
Alternative course of action. …………………………………………………………... 72
Fig 4.22, A UML collaboration diagram for Update record information
Basic course of action. …………………………………………………………………. 72
Fig 4.23, A UML collaboration diagram for Update record information
Alternative course of action…………………………………………………………. 72
Fig 4.24, A UML collaboration diagram for Generate record report
Basic course of action …………………………………………………………………..73
Fig 4.25, A UML collaboration diagram for Generate record report
Alternative course of action. …………………………………………………………... 73
Fig 4.26, A UML collaboration diagram for Generate Admin report
Basic course of action. …………………………………………………………………. 74
Fig 4.27, A UML collaboration diagram for Generate Admin report
Alternative course of action. …………………………………………………………… 74
Fig 4.29, A UML Deployment diagram for Hasseb Ber police Crime record
Management system ……………………………………………………………………..75
Fig 4.30 object modeling diagram ………………………………………………………76
FIG 4.31 User interface hierarchy……………………………………………………….76
Fig 4.32 Splash Screen For HBPCRMS …..…………………………………..……...78
Fig 4.33, login form for police crime record management system……………………79
Fig 4.34, Main form of police crime record management system……………………79
Fig 4.35, Detective main form of police crime record management system……….80
Fig 4.36, Crime registration form for police crime record management system………80
Fig 4.37, Plaintiff form for police crime record management system………………..81
Fig 4.38, Accused form for police crime record management system…………….…81
Fig 4.39, Exhibit form for police crime record management system………………..82
Fig 4.40, Crime registration form for police crime record management system…….82
Fig 4.41, Account create form for police crime record management system……….83
Fig 4.42, information desk form for police crime record management system………83
Fig 4.43, Admin form for police crime record management system…………………84
Abbreviations
HBPCRS: Hasseb Ber Police Crime Record System
MS: Microsoft
UML: Unified Modeling Language
VB: visual Basic
UI: User Interface
SQL: structural query language
UC: Use Case
GUI: Graphical user interface
ID: identity
SD: Sequence Diagram
PCRS: Police Crime Record System
Fig: figure
TABLE CONTENT
CHAPTER ONE
INTRODUCTION
1.1 BACKGROUND.................................................................................................................1
1.2 STATEMENT OF THE PROBLEM........................................................................................2
1.3 OBJECTIVES OF THE PROJECT..........................................................................................2
1.3.1 GENERAL OBJECTIVE.............................................................................................2
1.3.2 SPECIFIC OBJECTIVES..............................................................................................2
1.4 FEASIBILITY STUDY........................................................................................................2
1.4.1 OPERATIONAL FEASIBILITY.....................................................................................2
1.4.2 TECHNICAL FEASIBILITY.........................................................................................3
1.4.3 ECONOMICAL FEASIBILITY......................................................................................3
1.4.3.1 TANGIBLE BENEFITS.....................................................................................3
1.4.3.2 INTANGIBLE BENEFITS..................................................................................3
1.4.4 SCHEDULE FEASIBILITY...........................................................................................3
1.5 PROJECT PLAN ACTIVITIES..............................................................................................4
1.6 SIGNIFICANCE OF THE PROJECT......................................................................................4
1.7 SCOPE OF THE PROJECT...................................................................................................5
1.8 METHODOLOGIES............................................................................................................6
1.8.1 DATA COLLECTION METHODS.................................................................................6
1.8.2 FACT FINDING TECHNIQUES....................................................................................6
1.8.3 SYSTEM ANALYSIS AND DESIGN METHODOLOGIES...............................................6
1.8.4 SYSTEM DEVELOPMENT AND IMPLEMENTATION TOOLS.......................................7
1.9 SCHEDULE.......................................................................................................................9
1.10 BUDGET........................................................................................................................9
CHAPTER TWO
BUSINESS AREA ANALYSIS
2.1 GENERAL DESCRIPTION OF THE EXISTING SYSTEM.................................................................10
2.2 PROBLEM OF THE EXISTING SYSTEM.............................................................................15
2.3 REQUIREMENT DESCRIPTION.........................................................................................17
2.3.1 FUNCTIONAL REQUIREMENTS...............................................................................17
2.3.2 ESSENTIAL USE CASE MODELING.........................................................................18
2.3.3 ESSENTIAL USER INTERFACE PROTOTYPE............................................................22
2.3.4 CLASS RESPONSIBILITY CLLABORATOR (CRC) CARD.....................................................25
2.4 NONFUNCTIONAL REQUIREMENTS................................................................................28
2.4.1, PERFORMANCE.....................................................................................................28
2.4.2, USER INTERFACE..................................................................................................28
2.4.3, COMPUTER SECURITY AND ACCESS.....................................................................28
CHAPTER THREE
OBJECT ORIENTED ANALYSIS
3.1 SYSTEM MODELS..........................................................................................................29
3.1.1 SYSTEM USE CASE MODEL FOR THE NEW SYSTEM................................................30
3.1.2 DOCUMENTING USE CASES....................................................................................31
3.2 SEQUENCE DIAGRAM....................................................................................................37
3.3 CONCEPTUAL CLASS MODELING...................................................................................42
3.4 USER INTERFACE PROTOTYPING FOR THE NEW SYSTEM..............................................43
3.5 SUPPLEMENTARY SPECIFICATION................................................................................52
3.5.1 BUSINESS RULES OF THE NEW SYSTEM.................................................................52
3.5.2 CONSTRAINTS........................................................................................................53
3.5.3 CHANGE CASES......................................................................................................53
CHAPTER FOUR
SYSTEM DESIGN/USING OBJECT ORIENTED MODELING
4.1INTRODUCTION..........................................................................................................54
4.2 CLASS TYPE ARCHITECTURE....................................................................................54
4.3 DESIGN GOALS.........................................................................................................56
4.4 CLASS DIAGRAM.......................................................................................................57
4.5 CLASS MODELING.....................................................................................................57
4.6 DOCUMENTING CLASS DIAGRAM..............................................................................58
4.7 STATE CHART MODELING.........................................................................................62
4.8 COLLABORATION MODELING(USING COLLABORATION DIAGRAM)..........................66
4.9 COMPONENT MODELING (USING COMPONENT DIAGRAM).......................................74
4.10 DEPLOYMENT MODELING (USING DEPLOYMENT DIAGRAM)...................................75
4.11 OBJECT MODEL (USING OBJECT DIAGRAM)............................................................76
4.12 USER INTERFACE HIERARCHY...............................................................................76
4.13 USER INTERFACE DESIGN……...………………….……….…………………….78
CHAPTER FIVE
SYSTEM CONSTRACTION/IMPLEMENTATION
5.1 INTRODUCTION…………………………………………………………………………..88
5.2 CODING (CODING AS ANNEX) .......................................................................................88
5.2.1. ALGORITHM DEVELOPMENT……………………………………………….…..92
5.3 HARDWARE AND SOFTWARE ACQUISITIONS…………………………….……..…99
5.2.2 FLOW CHART DESIGN……………………………………………………………101
5.3.2 SOFTWARE ACQUISITIONS …………………………………………………… 101
5.4 DATA PREPARATION AND INSTALLATION………………………………………101
5.5 TESTING ………………………………………………………………………………….102
5.6. START-UP STRATEGIES……………………………………………………………….103
CHAPTER SIX
RECOMMENDATION AND CONCLUSION
CONCLUSION …………………………………………………………………………….…...104
RECOMMENDATION …………………………………………………………………….…..106
REFERENCE…………………………………………………………………………………....107
Chapter one
INTRODUCTION
1.1 Background
Kombolcha town found in the north western parts of Addis Ababa at 376 kilometers
from the capital city Ethiopia and 25km far apart from Dessie town. The town has early
civilization like other early towns of Ethiopia. It is the main industry center in Amhara
region and has its own administration structure to organize, control and manage the local
communities. In Kombolcha town there are governmental and non-governmental
organizations which facilitate the development of the town and provide services to the
community. From those governmental institution police stations are one part which
serves that will be peaceful security among the people and their property prevalence.
There are six police stations found in Kombolcha town .From those police stations
Kombolcha town Hasseb Ber police center is one of the police station. It was established
since 1989 E.C for the purpose of protecting local communities from criminal activities.
Hasseb Ber police center found in the Eastern part from the administration office of
Kombolcha town .Like to other governmental institutions, the police station has its own
vision and mission. Creating the country that have peaceful relationship and stable rule of
law which prevents the right of the community and freedom of their life is set as a
vision ,and By actively participating the local community, the police station should have
the duty to create strong information chain between them set as a mission of the police
station. At the first phase there were small number of police members with Commanders,
Inspectors and Constables. But recently there are 110 police members found, from those
90 of them are males and 20 of them are females with different responsibilities and
authorities. It is a well organized police station that serves crime prevention; detection
and convection of criminals depend on a highly responsive manner. But the efficiency of
the policing function and the effectiveness with which it tackles crime depend on what
quality of information it can drive from its existing record and how fast it can have access
to it is not qualified. The station has responsible for reporting and storing the nature of
the crime, the location details, the sequence of the crime information on victims.[1] The
crime record system of the station currently investigated with the problem of recording,
storing, retrieving and updating of crime information to generate reports and decision
making purpose. Currently the police station processes tasks in the form of document
based applications or traditional file systems. The current system of Hasseb Ber police
station recording personal information of crimes on traditional document formats has
been depicted at the back of the page.
On the other hand processing of the crime record can be automated by Hasseb Ber crime
record management system, which is newly implemented. The proposed system can be
taken as to automate processing tasks with less efforts and resources (like ,reducing
accessing times and material requirements ).
1
1.2 Statement of the problem
The police station applies manual way of recording crimes and processing of tasks. Due
to this reason the existing manual processing has the following problems.
 It takes much efforts and time to retrieve crime information
 Difficulty of updating information timely in each departments of the office
 File control mechanism is very tedious, Complicated and not secured.
 High material resource wastage (written materials) and much cost is expanded for
handling records.
 Difficulty in conducting consistent reports.
 The same detail of crime information is recorded in multiple places (documents),
this indicates redundancy.
Thus to address those problems there is a need of developing automated crime record
management system of Kombolcha town Hasseb Ber police station. Thus,will
Reducing time and effort in the case of retrieving information
Changes traditional data processing and handling mechanism into desktop
application and database system respectively.
Reduce file duplications, such that the system user deletes the information which
is dead files.
1.3 Objectives of the Project
The general and specific objectives of the project are described bellow.
1.3.1 General objective
The general objective of this project is to develop automated crime record management
system of Kombolcha town Hasseb Ber police station.
1.3.2 Specific Objectives
To achieve the general objectives of the project, the proposed system consists of the
following specific objectives:
 Collect data, analyze the system requirements and identify problems of the
existing system
 Design the artifacts of the proposed system for the overall view of the structure
 Implementing the system
 Finally testing the system
1.4 Feasibility study
Feasibility study is used to investigate the proposed system in multiple dimensions. It
used to indicate whether the system feasible or not. The proposed system can be seen
according to the following literals.
1.4.1 Operational feasibility
The new system can be easily operated and accessed by the users who interact to the
system. It contains user friendly commands which leads users interact to the system
interfaces.
2
1.4.2 Technical feasibility
It is the process of accessing the developed system by the organization. Technical
feasibility is the measure of practicality of the specific technical solution and the
availability of technical resources and expertise. The proposed system can be easly
maintained and repaired without requiring high Experts or technical assistants, because
the system was developed by familiar programming language (environment).
1.4.3 Economical feasibility
Economic feasibility is the process of identifying the financial benefits and costs
associated with the project being developed.
1.4.3.1 Tangible Benefits
The systems provided tangible benefit like increasing employee’s interest in their work
which had a great role for the development of the database of Wollo univerisiy kiot
student clinic patient recored mgt system minimizes the work load of the employee.
1.4.3.2 Intangible Benefits
The intangible benefits we have pointed out the system development are the following:-
 Easily access patient information throughout the clinic.
 Increased flexibility
 Increase speed of activity
 Improves the confidence of the system users.
1.4.4 Schedule Feasibility

Schedule feasibility is making sure whether the potential time frames and Completion
date can be met or not .The project team members expected the Project to be completed
on time with out any delay.
3
1.5 Project plan Activities
Phases Activities and tasks deliverables

Project planning Information gathering, Team Title approved, team
organizing, choose project title composed
Proposal writing Gathering information Proposal
about the title project
Requirement planning Finding requirements for the new Requirement specification
system, grouping the requirements in
similar features
Requirement Deeply understanding current system Requirement analysis and
Definition/Determination problems and choose alternative documentation
solutions to overcome the problem,
identifying functional and non
functional requirements to address
current system problems, Designing
different artifacts of the new system
using object oriented modeling tools
Business area analysis Studying the business rule of the Business rule
station, communicate with official understanding and
leaders of the organization to get documentation
information, eliciting the
requirements from the users
perspective of the station
Object oriented analysis Generally analyzing of the system Object oriented
according to object oriented documentation/preliminary
approach, design of different use design
case
System design Detail design of the new system Detail design of the system
based on the system objects and documentation
Implementation Algorithm analysis, flow chart Implementation
modeling, testing strategies
Table 1, Task break down activities and deliverables
1.6 Significance of the project

Kombolcha town Hasseb Ber police station crime record management system is not
using computerized data processing System; hence it is a serious problem in time
management and to perform their work efficiently. So making the system automated will
investigate the technological problems and to find ways and means to enable the station
computerized working system that could help to work efficiently furtherer more this
project is significant in that it enables the system.
 Time consuming activities(tasks) will be reduced
 Reduce man power & material budget allocations
4
 Avoid document missing and material wastage
 Avoid tiredness to separate the dead file from the no dead files.
 It ensures fast & efficient sharing of critical information within the police station.
Benefiaries of the Project

Office workers of the station:-
 Can access patients’ data easily
 Save their time
 Reduce workers load
 Decrease errors in information access of the manual system
Clients of the system:-
 Saving their time and work loads
 Reduce complexity
 Easily access patient’ information from organized
database.
 Control patient records and reduce data redundancy
Group members Beneffiary:
 The project has initiated our team to get knowledge of how
to develop the required system application.
 While struggling with some difficulties, the team got a lot
of experiences of solving problems.
1.7 Scope of the project

The proposed system is only applicable on:
 With less effort and cost, the system is able to maintain and store crime
information.
 Accurate way of recording or processing crimes’ information and set records into
organized database system for reference.
 Presence of centralized database and organized records.
 Produce reports for only crime records.
The proposed system is limited on recording, storing, updating and retrieving crime’s
information. However, it will not include:
Making the system networked and web based application
Other stations to be automated and networked.
Since, during the development time of our project the following limitations are facing:
 Shortage of hours to use computer in the computer laboratory room
5
 Time line for final year project allocated
1.8 Methodologies
In developing Hasseb Ber police crime record system, the following development
methodologies and tools will be applied.
1.8.1 Data collection methods

Data collection was one of the important tasks to analyze how activities done in
existing system and developed the new system .Data for developing this system
obtained from different sources. These data sources were system users (personnel office
clerks, personnel office manager, and Detective managers), different forms and
documents used in the office, procedure manuals, and reports of the office.
1.8.2 Fact Finding Techniques
Since the data was the basic component (requirement) to achieve the target aimed by the
Project, it would be collected from different data sources described under source.
This would be committed through:
A) Interview: - was used to gather required data for the project by contacting different
employees of the organization.
B) Observation:-was used to gather additional data by observing the actual work being
done by the staff and consolidated with what was obtained through Interview.
C) Document Analysis (Document & literature review):- consulted and analyzed written
materials that describe the operations conducted in the station to further strengthen and
support the information that applied the above technique
1.8.3 System Analysis and Design Methodologies
System Analysis: is the process of breakdown an entire system into module,
analyzing each module separately, and determining the relationship between them. In
system development process we use system modeling i.e. creating model of the system.
System modeling is the process of creating a model of system by analyzing and
organizing the system elements. This is the phase where deeply understanding of the
existing system problems and finding alternative solution.
System design: - to design the system the project team has choose Object
Oriented Modeling techniques and Unified modeling language tools.
Reason of choosing:
 It enables us to comprehensively model a system before we develop
it
6
 Modification of the object implementation is easy because objects
are loosely coupled.
 Understanding of the structure is easy because object oriented
modeling and tools used to represent real world entities.
 Direct manipulation of architectural components is possible because
several object oriented programming languages exist.
1.8.4 System development and implementation tools
For the successful completion of Hasseb Ber police crime record system different tools
and techniques would be put for different purposes & tasks .This includes:
Microsoft-Access:-for database purpose (back-end).since, Microsoft Access
is the most widely used desktop database system in the world, this helps
system users easily interaction. Microsoft Access is part of Microsoft Office
so there is a common interface and lots of developers and support options
available. For building desktop database systems our team members choose
Microsoft Access forms, reports, queries. This supports our proposed system
development based on desktop and will be standalone system. Microsoft
Access 2007 is free database software during runtime but MY-SQL is not.[2]
Microsoft Access is significantly less expensive than either SQL Server or
Oracle. Typical development times for custom databases using a qualified
consultant of Access are essential during system change when the system
requires Rapid application development. Doing development of the system
using tools such as .net or building an automated or a web-based system with
access is so simple and easily intractable. Third party support for Microsoft
Access databases is very common, example: interfaces to external databases. If
you need a database that serves your needs and Microsoft Access is a viable option,
it is probably the fastest and least expensive way to get your goals
accomplished. [3]
Visual Basic.NET:-for interface designing &programming the process Logic

(front end).Since, VB.NET have a number of features that makes it
preferable to be this integrated development environment.VB.NET boosts
performance and scalability by offering access to compiled languages. In
VB.NET, code is compiled. When invoke the request a page for the first
time, in it environment run time compiles the code and the page itself, and
holds copy of the compiled result. When we request the page the second
time, the stored copy is used. This results in greatly increased performance
because, after this first request, the code can run from the much faster
compiled version and the content on the page does not need to be parsed
again. [4]
7
VB.NET provides several server controls that simplify the task of creating pages.
These server controls encapsulate common tasks that range from displaying calendars
and tables to validating user input. They automatically maintain their selection states and
expose properties, methods, and events for server-side code, thereby providing a clean
programming model. In addition VB.NET, have a good user interface for designing and
implementing different form applications to the User. It have many user interactive
commands that helps users to operate in simple way and use it.VB.NET also provides a
true language-neutral execution framework for automated and it supports multiple Back-
End tools (like MS- SQL, MS-Access). [5]
Rationale rose:-for drawing the different artifacts of the requirement analysis

and design. Since,
Rational Rose is an object oriented-Unified Modeling Language (UML) software
design tool intended for visual modeling and component construction of enterprise-level
software applications.
First, let us explore why we should want to use Rational Rose. The most immediate
advantages are that it:
Facilitates team development: Rose provides complete team support, allowing users
(like, developers and analysts) to work their own version of the model.
Rational rose used throughout the software development process: From defining the
user requirements to implementation, everyone working on the project understands a
universal language. You can use Rose at any stage in the life-cycle process. It helps you
uncover and prevent potentially serious mistakes downstream.
Rational rose makes easier to manage model changes: Any change you make to a
Rational Rose model you make available to others by using a configuration management
and version control (CMVC) system. This lets you integrate changes into the model, no
matter where you are in the development stage. Rose typically uses add-in tools, such as
Rationale’s Clear Case and Microsoft’s Visual SourceSafe, for this purpose.
Saves on creating additional project documentation: An advantage here is that you
simply use the models created in Rose as a basis for design and development. I’ve seen
many projects fail because of poor documentation practices.
Addresses bad legacy software: You should consider using Rose when facing software
that doesn’t fit users’ needs; since Rose lets you go back and correct flaws within the
legacy application. [6]
In addition to this software designer uses Rational Rose
 To visually create (model) the framework for an application by blocking out
classes with actors (stick figures), use case elements (ovals), objects (rectangles)
and messages/relationships (arrows) in a sequence diagram using drag-and-Drop.
 Rational Rose allows designers to take advantage of iterative development
(sometimes called evolutionary development) because the new application can be
created in stages.
 Rational Rose uses a GUI that includes a browser, a diagram window, a document
window, a standard toolbar and a diagram toolbar.[7]
Microsoft word:-for documentation of each phase.
8
1.9 Schedule
Nov 2011 Dec 2011 Jan 2012 Feb 2012 Mar 2012 Apr 2012 May 2012 Jun 2012
ID Task Name Start Finish Duration
11/20 11/27 12/4 12/11 12/18 12/25 1/1 1/8 1/15 1/22 1/29 2/5 2/12 2/19 2/26 3/4 3/11 3/18 3/25 4/1 4/8 4/15 4/22 4/29 5/6 5/13 5/20 5/27 6/3
1 Information gathering 11/18/2011 11/22/2011 3d
2 Planning phase 11/25/2011 12/29/2011 5w
3 Analysis phase 12/30/2011 1/27/2012 4w 1d
4 Design phase 1/27/2012 2/23/2012 4w
5 implementation 2/24/2012 4/23/2012 8w 2d
6 testing 4/24/2012 5/10/2012 2w 3d
Chart1.1 Schedule of the project
1.10 Budget
Item Quantity Unit Price Total Price

(Birr) (Birr)
Stationery 60.00 60.00
materials
CD ROM Disks 7 10.00 70.00
Flash Diskette 1 (2GB) 400.00 400.00
Printer cost 300 pages 1.00 300.00
Scanner cost 20 0.50 10.00
Photographing 10 photos 5.00 50.00
cost
Photo copy cost 300 pages 0.15 45.00
Transport Total trip - 500.00
Other Unspecified costs - 1000.00
Total 2435.00
Table1.1. Cost estimation of materials and other expenses
9
Chapter Two
Business Area Analysis
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 Kombolcha 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 Kombolcha Town Hasseb Ber police station migrate the manual
system to the computerized crime record management system to facilitate their service
and benefit of the station.
2.1 General description 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 constraints and rules of the
existing system incorporated.
In general the reason behind for studied the existing system:
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.
10
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.
Major players of the Existing system
The major players of the current system are:
 Detective managers
 Administrator
 Information Desk
 Personal clerks
 Police members
Role of Detective managers
The main role of Detective managers in Hasseb Ber police station is:
Recording daily information about crimes
Updating crimes’ information
Generating reports
Delivering reports
Role of Administrator:
The following activities are performed under the Administrator of Hasseb Ber police
station crime manual recording system.
 Maintain crime information
 Administrating the station
 Collecting daily, monthly and manual repots from different
departments
 Producing organizational reports
11
Role of Information Desk teams
 Daily Recording and accessing of crime information’s
 Communicating individuals who has an issue to different office
managers and give directions about the Administration
hierarchies to whom they complained.
 Generating reports and distributing to the Administrator body
Role of personal clerks

 Typing crime documents
 Preparing manual documents with multiples of copies
 Preparing reports recommended by their Bosses
 Separating crime files
 Distributing reports to departments after judgment approved
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 Kombolcha town Hasseb Ber 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
12
 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
Input
 Crime register
Process
 Get manual form which provide to handle crime data
 There should be suffered person(accuser) who victimized by the
accident and his/her legal complaint towards the station
 Get crime data from police departments with legal evidence
 Register crime data
Output
 Crime registered
 Produce crime report
 Make decision or judgment
 Stored in a manual document as a file
Input
 Criminal record(accused)
Process
 Get criminal data to start process
 See legal evidence that criminal person does did or didn’t made a
crime
 Record criminal
Output
 Criminal recorded
 Criminal reported
Input
 Produce report
Process
 Check crime data in manual crime documents
 Check the date, month and year information that crime file was recorded
and stored
 Select information which needed for current report
13
 Print and distribute report
Output
 Report produced
 Put report document as a hard copy
Business rule
Business rule are the guidelines that an organization and stakeholders follow to
perform their tasks to be assigned. Every organization should have business rules and
formal procedures to manage and control organization resources properly. The following
business rules are investigated within Kombolcha Town Hasseb Ber police station.
 Any individuals who suffered by the victim has the right to forward formal
complaint towards the station depending on full evidence.
 Any customer who enters to the station should have an identity card.
 Customers should not hold materials like gun, stick, knife etc which is not
allowed by the station.
 No one moves without the allowed destination when he/she is arrested who
suspected as a criminal, and stay within the allowed room until he/she gets
legal judgments from the court.
 An individual who is arrested by the police and stay in prison should have
legal rights and not be torched as well.
 Any person who did a crime and arrested under the law should get legal
judgment within 48 hours.
 If the arrested person does not do the crime he/she who were previously
suspected by the law, has the rights to release after all evidences are
investigated with legal protection.
 Any employees within the station should not post any notice on the board
without the legal seal of the department offices.
No one enters to the station for any case without getting legal permissions from police
guards etc. [8]
2.2 Problem of the Existing system
14
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.
Alternative Solution to solve the existing system Problems
15
After analyzing the problems in the existing system, our project team identified and
evaluated the following alternative solutions:
 Automating the HBPCRS particularly within the Station of sub-

department
 Automating the system using computer software application
 Changing the manual system into desktop application.
Option analysis and the proposed new system
Option analysis is means of evaluating the alternative solutions in terms of their

advantages and disadvantages.
Advantage:
 The new system can be implemented without changing the organization

policy.
 Loss costly and easy to install.
 The new system does not require more human labor.
 Processing data with high speed and short hand form.

 Data redundancy problem will be avoided with the proposed system.
Disadvantage:
 Have some features that will not be used and happened frequently such as
demotion, termination, manual tasks.
 Requires technical person to handle and manage the system.
 It does not address all the basic problems of the station rather focus on the
station sub department that means the new system implemented only for
crime information processing
 The proposed new system based on the option analysis described above, we
select the first option that is developing an applications to be used by the
station sub department staff’s and crime record of the station with the stand
alone system.
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 stand alone 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
16
and database control mechanisms. The system addresses problems which were
incorporated in the existing system.
2.3 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. [9] 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.3.1 Functional requirements
The Functional requirement is concerned with actual performance of the system that is
going to be developed. [10] 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
17
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.3.2 Essential Use case modeling
Essential use cases
Essential use cases are of primary importance early in a project’s analysis phase. Their
purpose is to document the business process that the Application must support without
bias to technology and implementation. The narrative in the Essential use case is to be
expressed in the language of the application domain and of users. Essential Use cases
should achieve the following goals:
− Serve as an effective communication tool between users and technologists.
− Be scoped to a specific business goal as well as identify and document the business
logic and actions.
− Is diagrammed using the standards documents.
− Be documented in text format using the standard "Essential Use case Specification
Template".
Essential use case modeling is a simplified abstract, generalized use case that captures
the intentions of the user in a technology and implementation independent manner. [11] It
identifiers use case and actors of the existing system.
18
Crime Re gister
Detective Administrator
Record crime information
Information Desk
Generate report
fig 2.0 Essential use case diagram
Essential use case description

Name: crime registration
Identifier: UC01
Actor: Detective
Pre- condition: The Detective starts the process of new crime registration.
Post- condition: Crime registered successfully and data stored to the database.
Basic course of Actions

1. Detective wants to register new crime
2. The system will display registration form.
3. Detective enters all required information for registration via the crime form
4. The Detective submits the information.
5. The system validates the filled information.
6 The system accepts Crime data and stored to related table.
7. Use case ends.
Alternative course of Action: filled information is not valid
A.1. Detective should enters the crime data again
A.2.The Detective fills the information correctly
Name: record crime information
Identifier:UC02
19
Actor: Information desk
Precondition: Information desk should have crime information.
Post condition: crime information recorded successfully
Basic course of Action:
1. Information desk wants to record crime information.
2. The Information Desk should have crime form for record the data.
3. Information Desk filled the information on the form
5. Check filled data and its correctness
4. Store the data to the related record
6. Use case ends.
Alternative course of Action: for invalid data entry.
A.1 Information Desk should display the form and record again.
A.2 Delete the recorded data from the table which is not correct
A.3 At each step information Desk should do step 5 of the above basic course of action
Detective report generation
Name: Generate report
Identifier: UC03
Actors: Detective
Precondition: the Detective should have stored crime record there.
Post condition: generate report.
Basic course of action:
1. Detective wants to generate crime reports.
2. Detective search the file from the data base what he/she want for report
3. Select crimes information/report which can be generated for the purpose of decision
making
4. Detective produce report
5. Check reports before going on to decision making
6. Use case end
Generate report Information Desk
Name: Generate report
Actor: Information desk.
20
Precondition: There should be crime’s data in the database.
Post condition: Administrator generates report.
1. Information desk wants to generate report.
2. The system displays report form
3. Information desk click on search to generate report
4. Available information generated.
5. Check and view report
6. Use case end
Generate report Administrator
Name: Generate Administration report
Actor: Administrator
1. Administrator wants to generate report.
2. The system displays report form
3. Administrator collects report from Detective and Information Desk
4. Check and view report.
5. Use case end
User interface
It describes how the new system interacts with the user:-
 
The user interface is user friendly of graphical user interface. There is an

explication of all user input functions, users will take an average of the
five minutes to become familiar with the user interface and system
functions. For experienced computer users, the average will be one minute
to learn the user interface. Experienced users are these who have
previously interacted with the GUI and are comfortable using a standard
keyboard, mouse, and monitor.
21

It functions with the latest operating system

It handles error corrections and prompts users for correction

Hardware Interface
The hardware interface for the system will be standard keyboard, mouse, and monitor.
Terminal control will be a screen –oriented. The system will also require a printer which
has a good printing rate. All the systems running HBPCRS should have mechanisms to
over come power failures.
Software Interfaces
The System on which HBPCRS for running should have the following components
 Microsoft OLDEB Data control object 6.0

 Microsoft data grid control 6.0
 Basic support for Visual Basic.NET components
System or product function
 Authentication
This function is to identify the user to the system so that all the access level and
privileges are detrained
 Administrator
Responsible for maintaining database and also preparing organizational reports
Major duty is to give reports for what ever criteria specified by the user
 Search
The function is to retrieve the required information base on the constraints specified
by the user
 Managing data base
This function is to create, update, retrieve and delete record from the database
2.3.3 Essential user interface prototype
22
Which describe the user interface requirements for the new system users with
technological alternatives. The following user interface prototype shows Hasseb Ber
police station crime record system in some part, but they are modified more in system use
case interface prototypes.
Crime registration
Crime form Crime Address
Input field: new crime Input field include: crime
registration location, region, Zone, woreda
Crime information
Input field include: crime Button: submit Button: clear
type, crime date, crime Id Action click: the data Action click: clear
added to the database the filled data from
the form
Button: search
Action click: search crime Button: exit
data from the table Action click: exit
crime form
Fig 2.1, user interface prototype for crime registration
Crime information Additional information

Input field include: date, Input field: Reserved ID of
hour, accident location, types Information desk, first and last
of accident, description name of information desk
Button: search Button: clear

Button: submit Action click: find crime Action click: clear text
Action click: data added to information from related from textboxes
related table table
Button: exit
Action click: end task
23
Fig 2.2 user interface prototype for record crime information
Generate crime report
Report
Input field include: crime data (crime
Type, crimeID, Crimedate, Crime
address)
Button: search Button: print

Action click: retrieve crime Action click: print the report as
information automatically from a hard copy document
the table and display for view
Fig 2.3 user interface prototype for generate report
User characteristics for system interaction
The subsequent facts are the general characteristics of the intended users:-
 No prior experience/expertise required because the system has user friendly
commands

 The medium of language for communication is English for operating the
system

 The user need to understand the information so easily better UI and simple
English
Assumptions and dependencies
This section must include any assumptions if not true, would require changes to the
requirements
 The system depends on the software components and operating systems
which are needed for its development.
 The hardware used to interact with the PCRMS will be standard keyboard as
required
24
 The users know how to start the program from the GUI, and can interact with
a user interface using a standard keyboard, mouse, and monitor.
2.3.4 Domain modeling with class Responsibility Collaborator
(CRC) card
A Class Responsibility Collaborator (CRC) model is a collection of standard index
Cards that have been divided into three sections, this is class name, responsibility and
collaborator. A class represents a collection of similar objects, a responsibility is
something that a class knows or does, and a collaborator is another class that a class
interacts with to fulfill its responsibilities. [12] Those can be shown in the following
table.
Class name
Responsibility Collaborator
Detective manager<<Actor>>
Register crimes Accused
Update crime information Witness
Record exhibit information Plaintiff
Hold information about the person who sees criminal
action happened(Witness’s information)
Document information about Defendant
person(plaintiff’s information)
Change account
Generate crime report
Table 2. Class responsibility collaborator card for Detective manager
Administrator<<Actor>>
Maintain crime information Detective department
Update database Information Desk
Collect report department
Change account
Generate admin report
Table 2.1 Class responsibility collaborator card for Administrator
Information Desk<<Actor>>
25
Record crime information Detective departments
Update information Crime registration documents
Produce report
Table 2.2 Class responsibility collaborator card for Information Desk
Crime
Crime date Plaintiff person
Crime ID Accused person
Name
Sex
Age
Address
Religion
Region
Zone
Woreda
Kebele
Crime registration<<UI>>
Information recorded about crimes crime
Get evidence about the crime for recoding
fill personal information about crime
Add information into database
Table 2.3 Class responsibility collaborator card for crime class

Accused
Accused ID Crime
Accused date Plaintiff
Charging date Witness
Sex
Age
Education level
Nationality
Region
Accused <<UI>>
investigate evidence information Detective
accept Accused person information
Table 2.4 Class responsibility collaborator card for Accused class
Exhibit
Exhibit ID Crime
Item name
Item ID
Amount
Exhibit information<<UI>>
See exhibit information Detective
Accept exhibit information
Table 2.5 Class responsibility collaborator card for Exhibit class
26
Witness
Witness ID Crime
Name Accused
Plaintiff
Sex
Age
Nationality
Region
Zone
Kebele
Woreda
Witness person<<UI>>
See crime evidence information Detective
Accept Witness information
Table 2.6 Class responsibility collaborator card for Witness class

Plaintiff
Age Plaintiff
Plaintiff ID Accused
Name Crime
Sex
Date
Plaintiff person<<UI>>
See all information about the plaintiff Crime
Accept plaintiff personal information
Table 2.7 Class responsibility collaborator card for plaintiff class
Update information
New information crime
Change information
Update <<UI>>
Search related information for updating Crime(Historical information of crimes)
New information stored
Table 2.8 Class responsibility collaborator card for update information
Generate report
**select prototype** Crime(Crimes’ information)
Select report type and related records
Display report
27
Table 2.9 Class responsibility collaborator card for generate report
2.4 Nonfunctional requirements

This are most critical than the functional requirements of the system. [13] In order to
identify the non-functional requirements of the proposed system the following categories
are used as framework.
2.4.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.4.2, User interface
 The system is not able to run on the operating system like UNIX,
Linux, because it will be developed on WIN- XP 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.4.3, Computer Security and Access
 The system will promote username and password to login into the
system.
 The system must encrypt with the stored password which are not
readable
2.4.4, Backup and Recovery
 The system prevents damage of data from simultaneous change and
system failure.
 The system shall restore the system to its last consistent state.
2.4.5, Data
 The system shall store the data in the relation format.
28
 The system will protect the data against unauthorized disclosure of
information.
 The system shall authorize the users to produce ad-hoc quires and
report
Chapter Three
Object Oriented Analysis

In this chapter includes general analysis of Kombolcha Hasseb Ber police crime
record management System in object oriented approach. This analysis phase used for
description of new system using, system use case, and sequence diagrams.
Object oriented analysis (OOA) is concerned with developing software requirements
and specifications expressed as a system’s object model (composed of a population of
Interacting objects) , as opposed to the traditional data or functional views of system.
[14]
3.1 System use case
Use cases
Use case identifies processes or activities that can be done within the system
The following use case have been identified from the system specification
 Security login
 New crime registration
 Update crime registration
 Generate registration report
 Record crime information
 Update record information
 Generate record report
 Generate Administration report
Identified actors that will be participating in the system are:
 Detective team
 Information Desk
 Administration
29
3.1.1 System Use case model for the new system
During analysis, the main goal is to involve essential use cases into System use
cases. In system use case, we include high-level Implementation decisions. For example,
a system use case refers to specific user interface-components such as screens, or reports.
System use case model is composed of a use case diagram and the accompanying
documentation describing the use cases, actors, and associations. Which a collection of
use cases, actor, their associations a system boundary box (optional), and packages
(optional). A use case describes a sequence of actions that provide a measurable value to
an actor and is drawn as stick figures. [15]
Use case diagrams graphically depict system behavior (use cases). These diagrams
present a high level view of how the system is used as viewed from an outside’s (actor’s)
perspective. From the identified use cases and actors the use case diagram of the system
is shown in Fig 3.1
30
Fig3. Use case diagram for the system
3.1.2 Documenting use cases

Documenting use case is use to clarify the idea of use case and makes the process
that under goes in each use case easily understandable. Below are the lists of the use
cases that are identified for HBPCRS.
There are eight use cases:
Use case 01: Security login
Use case 02: New crime registration
Use case 03: Update crime registration
Use case 04: Generate registration report
31
Use case 05: Record crime information
Use case 06: Update record information
Use case 07: Generate record report
Use case 08: Generate Administration report
Security login
Name: security login
Identifier: UC 01
Description: allow user to login into HBPCRS.
Actor: Administrator of the police station
Precondition: An Administrator should have valid user name and password.
Post condition: The Administrator will login in to HBPCRS.
Extends: _____________
Include: UC 02, UC 03 UC 04, UC 05, UC 06, UC 07, and UC 08.
1. Detective/information Desk/Admin want to login into crime record
System.
2. The system will display user interface (security login UI01) and window request to
enter.
3. The Detective/information Desk/Admin enter password and user name via “UI01” &
submit the form.
4. The system checks validation of user name and password according to the” BR1”.
5. Detective/information Desk/Admin login into the system.
6. Use case end.
Alternative course Actions: inputted user name and password not valid.
A.1 The system verifies user name and password are not valid.
A.2 The system will continue at step 3 of the above basic course of action.
New crime registration
Name: New crime registration.
Identifier: UC02
Description: allow Detective to register new crime.
32
Actor: Detective
Precondition: Detective manager should be login in to the system first.
Post condition: The crime will be registered.
Extends: -------------
Include: UC01.
1. Detective wants to register new crime
2. The system will display “UI02 register new crime”.
3. Detective enters all required information for registration via “UI02 register new crime”
before starting register new crimes.
4. The Detective submits the information.
5. The system validates the crime information.
6 the system displays that the crime is successfully registered.
7. Use case ends.
Alternative course of Action: invalid data entry
A.1 The system displays an error message to the user.
A.2 The system indicates to retry.
A.3 Use case continues at step 3 and step 6 of the above basic course of action.
Update crime Registration

Name: Update crime registration
Identifier: UC03
Description: The system allows Detective manager to update crime registration
Actor: Detective
Precondition: Before starting to update crime information Detective manager should be
login into the system.
Post condition: Update crime registration
Extends: __________
33
Include: UC01
Basic course of Action
1. The Detective logs to his account from the home page of the HBPCRS
2. The Detective clicks on the Search crime button
3. The System displays search options (crime type, crime ID)
4. The Detective search using one search method
5. The system displays the searched result
6. The Detective clicks on the update button to modify the record
7. Use case end
Alternative course of Action: If the data there is a mistake in the data entry
A.1 The system displays error message and allow making correction
Generate crime registration report
Name: generate crime registration report.
Identifier: UC04
Description: allow Detective to generate crime registration report to an
Administrator.
Actor: Detective
Precondition: Detective should get data from HBPCRS
Post condition: The system generates the crime registration via Detective to
administrator.
Extends: ________
Include UC01
1 Detective wants generate crime registration an administrator.
2. The system display user interface UI04 “crime registration “.
3. Detective will enter all required information about the crime registration.
4. The system Validate for the availability of the information entered.
5. The system will display crime registration via “UI08 generate crime registration”.
6. Detective make crime registration letter to be printed.
7. Use case ends.
Alternative course A: input information is not valid.
A.1The system determines that the information is not available.
A.2 The system displays crime registration with the previous information
34
A.3 Use case continues at step 3 of the basic course of action.
Name: record crime information
Identifier: UC05
Description: The system allows Information desk to record crime information
Actor: Information desk
Precondition: Information desk should have valid user name and password to enter to
the system.
Post condition: record crime information
Extends: ___________
Include: UC01
Basic course of Action:
1. Information desk wants to record crime information.
2. The system displays the record form via“UI05 crime information record”.
3. Information desk enters the required information via “UI05 crime information record”
4. Information desk submits the recorded information.
5 the system display that crime record is successfully stored.
6. Use case ends.
Alternative course of Action: system display that the entered information is invalid.
A.1 The system determines that the information is invalid.
Update record information

Name: update record information
Identifier: UC06
Description: allow information desk to update crime information
Precondition: Information desk should have valid user name and password to update
information.
Post condition: update information.
Extends: ___________
35
Include: UC01
1.The Information desk logs to his account from the home page of the
HBPCRS
2. The Information desk clicks on the Search crime button
3. The System displays search options (crime type, crime ID)
4. The Information desk search using one search method
5. The system displays the searched result
6. The Information desk clicks on the update button to modify the record
7. Use case end
Alternative course of Action: If the data there is a mistake in the data entry
A.1 The system displays error message and allow making correction
Generate record information report
Name: generate record information report.
Identifier: UC07
Description: allow Information desk to generate crime information report to an
Administrator.
Precondition: Information desk should take data from HBPCRS
Post condition: The system generates the crime information via Information desk
to the administrator.
Extends: ________
Include UC01
1 Information desk wants generate crime record information an administrator.
2. The system display user interface UI07 “crime record information “.
3. Information desk will enter all required information about the crime record
information.
4. The system Validate for the availability of the information entered.
5. The system will display crime registration via “UI08 generate crime registration”.
6. Detective make crime registration letter to be printed.
7. Use case ends.
36
Alternative course A: input information is not valid.
A.1The system determines that the information is not available.
A.2 The system displays crime registration with the previous information
A.3 Use case continues at step 3 of the basic course of action
Generate Administration report
Name: Generate Administration report
Identifier: UC08
Description: allow Administrator to generate report in different form.
Actor: Administrator.
Extends: ________
Include: UC1
1. Administrator wants to generate report.
2. The system displays user interface “UI08 generate report form”.
3. Administrator collects types of report to be generated via “UI8 generate report”.
4. Administrator checks and views the selected report.
5. Use case ends.
Alternative course of action A: No files to be reported for the selected data type.
A.1 The system displays an error message to the Administrator via the report form.
3.2 Sequence diagram
Sequence diagram is used to show the sequence of actions, interaction of an object with
the Actor’s and time frames of the system. [16]
37
Sequence diagram for security login
Security login basic

course of action user Security login Security login Account Account
SD#UC01 <<Actor>> <<Controller>> <<UI>> <<DB>> <<UI>>
user wants to login

create validate user name
1,Detective/Information and password
desk/Administrator wants to login create
into crime record system. Enter password
2,The system displays user and user name
interface(Security login form) first.
3,Detective/Information desk/Admin
should enter user name and
password and submit the form. Display message
4,The system validate user name
and password.
5,The system accepts user name
and password.
6,The first application form
displayed.
7,Use Case end.
destoryed
Fig 3.1, A UML for sequence diagram for security login
Sequence diagram for new crime registration
38
Register new crime
basic course of Detective Main menu Register new crime HBPCRS
action <<Actor>> <<Controller>> <<UI>> <<DB>>
SD#UC02 Detective want
to register new
crime Call to display
1,Detective wants register new Create
crime.
2, the system will display "UC02 Registration form will be displayed
registre crime".
3,Detective enters the crime Fill crime information
information to the system.
4,After fill the required information, Click on submit
submit information.
5, The system validate information. Conform action/check
6,The inputted information is
correct Yes Validate inputted data
7,Crime successfully registerd
invalid
8,Use Case end.
Enter correct information again
Register crime
Fig1. 3.2 ,A UML for sequence diagram for new crime registration
Sequence diagram for update crime registration
update crime
registration basic
Detective Main menu Update crime registration HBPCRS
course of action
<<Actor>> <<Controller>> <<UI>> <<DB>>
SD#UC03
wants to update crime information

1,De tective w ants update crime . call to display
create
2, the syste m w ill display "UC02
update crime information".
3,De tective select information to be form displayed
updated
select information to be upda ted
4,Click on update.
5, The system che cks information
click on update
validity.
6,The syste m accepts valid data conformation
7,Information updated successfully
8,Use Case end. yes validate data
valid
update successfully
crime registered successfully
Fig3. 3.3 , A UML for sequence diagram for update crime registration
Sequence diagram for Generate crime report
39
Generate
registaration report Detective Main menu Generate registration report HBPCRS
basic course of action <<Actor>> <<Controller>> <<UI>> <<DB>>
SD#UC04
wants to generate registration report

1,Detective wants generate report. call to display
create
2,The system calls the form via
"UC04 generate registration
report". form displayed
3,The form will be dislayed.
select information to be generated check for availablity
4,Detective should select the
information to be generated.
5,The system checks available available
information.
6,The information is available in report generated
database
7,report will be generated.
8,Use Case end.
Fig 3.4, UML for sequence diagram for generate registration report
Sequence diagram for Record crime information
Record crime
information basic Informartion Desk Main menu Record crime information
course of action <<UI>> HBPCRS
<<Actor>> <<Controller>>
SD#UC05 <<DB>>
wants to register crime information
call to display
create
form displayed
1,Information desk w ants to
register crime information.
"UC05 record crime information. " select information to be recorded
4,Information desk should select record crime information
the information to be recorded.
5,The system validate information. click on submit
6,The system displays the
information is valid validate information
7,Crime information successfully
registerd.
8,Use Case end. valid
crime information recorded successfully
Fig 3.5, A UML for sequence diagram of record crime information
Sequence diagram for Update crime information
40
Update record
information basic Informartion Desk Main menu Update record information HBPCRS
course of action <<Actor>> <<Controller>> <<UI>> <<DB>>
SD#UC06
wants to update record information
call to display
1,Information desk wants to update create
record information. form will displayed
"UC06 record crime information. "
select information to be updated
4,Information desk should select
the information to be updated. click on update
5,The system validate information.
6,The system displays the
information is valid conformation
7, information successfully
updated. yes validate data
8,Use Case end.
valid
successfully updated
Fig 3.6, A UML for sequence diagram of update crime information
Sequence diagram for generate record report
Generate Record
report basic course of Information de sk Main menu Generate record report HBPCRS
SD#UC07
wants to generate administartion report
1,Information desk wants to generate call to display create
record report.
2,The system calls the form via form will displa yed
"UC07generate administration report."
3,The form will be dislayed. select information to be generated
4,Infformation desk should select the check availablity
information to be generated.
5,The system checks information available
availablity in database.
6,The system displays the information is
available. report generated
7, report is generated successfully.
8,view report.
9,Use Case end. view report
Fig3.7, A UML sequence diagram for generate record report
41
Sequence diagram for generate administration report
Generate administration
report basic course of Administrator Main menu Generate administartion report HBPCRS
SD#UC08
wants to generate administartion report
1,Administrator wants to generate call to display create
administration report.
2,The system calls the form via form will displayed
"UC08generate administration report."
3,The form w ill be dislayed. select information to be generated
4,Admin should select the information to check availablity
be generated.
5,The system checks information
availablity in database. available
6,The system displays the information is report generated
available.
7, report is generated successfully.
view report
8,view report.
9,Use Case end.
Fig 3.8, A UML for sequence diagram of generate administration report
3.3 Conceptual class modeling

Conceptual modeling is the activity of finding out which concepts are important to our
system. This process helps us to understand the problem further, and develop a better
awareness of our customer’s expectation. The UML does not tell us how or when to do
conceptual modeling, but it does provide us with the syntax to express the model. The
model we used is class diagram for conceptual modeling.
42
Crime Accused
Data ID
Name 1...* made 1 Name
ID Sex
Location Age
Region Accusing Date
Zone Exhibit Wanted date
item used Arrested date
Woreda Exhibit ID
Recorded date Item type Charging date
0..* uses 1
Item name Education level
Amount exhibited Nationality
1 Religion
sees
Is involved()
1..*
accuses
Witness
victimized 1 1
Name
Plaintiff
Sex
Age Name
Religion Sex
Nationality Age
Region Plaintiff Date
Zone present Religion
Woreda Job
Kebele Zone
Woreda
Fig 3.9, Conceptual class diagram for main components of the proposed system
3.4 User interface prototyping for the new system
User interface is an iterative analysis technique in which user is actively involved in
the making up of the user interface for the system .it is an analysis that enables us to
explore the problem space of the system, at least from the point of view of its users, and
provides vehicle for us to communicate the possible user interface design of the system
Login screen
User information and Button
User name
Input field include: user Password
name Input field include: password
Button: login Button: cancel

Action click: Send request Action click: used to
and validate password and close the login form.
user name
43
Fig 3.10 user interface prototype for login screen
Main menu screen

Users’ information and Buttons
Detective information Information desk Administrator information
Input field includes: user Input field include: user Input field include: user
type, user Id, password type, user Id, password type, user Id, password
Button: Back
Button: Select Button: close
Action click: used to
Used to choose Action click: used to close
return department select.
department type the main page.
Fig 3.11 user interface prototype for main menu screen
Detective screen
Crime menu Listed menus and Buttons
Crime menu Exhibit menu
Account menu
Accused menu
Witness menu Plaintiff menu
Button: clear Button: Refresh Button: back

Action click: Used to clear Action click: Used to Action click: used to
text from the text box . display the searching . direct to the main
menu
44
Fig 3.12 user interface prototype for Detective screen
Information Desk screen

Information
Crime information Information desk

Input field includes: date, accident Input field includes:
location, types of accident, hour information Id, first name,
last name, reserved Id
Button: submit Button: delete

Action click: send Action click: used to Button: exit
and validate the data Delete record info. Action click: end the
form
Button: back
Action click: directs to
main screen
Fig 3.13 user interface prototype for information desk screen
Administrator screen
Admin information Report information

Input field includes: user
id , first name, last
name, chief position
Button: clear Button: back Button: search

Action click: clear Action click: directs Action click: search
filled texts to the main screen report from requested
table
Fig 3.14 user interface prototype for Administrator screen
45
Crime screen
Crime information and Buttons
Crime name Crime address

Input type includes: crime Input type includes: crime
type, crime Id, crime date location, region, zone, woreda
and recorded date
Button: submit Button: search

Action click: used to send Action click: used to
filled data to database and search particular record
validate it from the table
Button: back Button: update

Action click: used to Action click: used to
direct back to detective update crime information
screen from crime table
Button: load
Action click: used to Button: exit
load data in to grid and Action click: used to close
view with form. the form and end of tasks
Fig 3.15 user interface prototype for crime registration screen
46
Accused screen
Accused screen
accaaaaa Accused person information and Buttons
Accused information Accused address

Input type includes: first name, last Input field includes: region, zone,
name, sex, age, accused ID, woreda, kebele, citizenship
arrested date, charging date,
education level, religion and job
Button: exit
Button: submit
Button: back Action click: used
Action click: used to send and
Action click: directs to to close the form
validate filled data
Detective screen
Button: load Button: search

Action click: used Action click: used
to load data in to to search accused
grid and view with information.
Button: update
form. Action click: used to
update accused
information from
Fig 3.16 user interface prototype for Accused
recorded registration
data base. screen
Fig 3.16 user interface prototype for Accused screen
47
Plaintiff screen
Plaintiff personal information and Buttons
Plaintiff information Plaintiff address

Input type include: first name, Input field includes: region,
last name, sex, age, date, zone, woreda, kebele
plaintiff Id, religion, job
Button: back Button: update

Button: submit Action click: used Action click: used to
Action click: used to to return back to update Plaintiff
send and validate detective screen information from
filled data recorded data base.
Button: search Button: load Button: exit

Action click: used Action click: used Action click:
to search plaintiff to load data in to used to close
information from grid and view the screen
recorded database. with form.
Fig 3.17 user interface prototype for plaintiff registration screen
48
Witness screen
Witness personal information and Buttons
Witness information Witness address

Input field includes: first name Input field includes: region,
last name, sex, age, religion, zone, woreda, kebele,
accused name, crime ID nationality
Button: search Button: update

Button: submit
Action click: used Action click: used
Action click: used to send
to search witness to update Witness
and validate filled data
personal information from
Button: load information. recorded data.
Action click: used to load
data in to grid and view with
form.
Button: exit
Button: back Action click: used to
Action click: used to close the screen
return back to detective
screen
Fig 3.18 user interface prototype for witness registration screen
Fig 3.18 user interface prototype for Witness screen
49
Exhibit screen
Exhibit information and Buttons
Exhibit data Additional information

Input field includes: exhibit Input type includes:
Id, item type, item name, Detective name, position,
amount crimeID
Button: update
Button: submit Button: search Action click: used to update
Action click: send Action click: used to Exhibit information from
and validate filled search Exhibit data. recorded data.
data
Button: back
Fig 3.19click:
Action user interface Button:
directs prototype for Exhibitload
registration screen Button: exit
to detective screen Action click: used Action click:
to load data in to close the form.
grid and view with
form.
Fig 3.19 user interface prototype for Exhibit screen
50
User account screen
User account information

Users’ information Password
Input field includes: user name, Input field include: password
department (Detective, Info
Desk, Admin), user ID
Button: add Button: ok

Guide user to add his/her Button: clear Action click: validate
account in the text box Action click: clear entered account and
text from text box display next screen
Fig 3.20 user interface prototype for user account screen
Change user account screen
Account information
User name Password

Input field includes: user Input field includes: old
name, new user name, ID password, new password
number, account type
Button: create Button: cancel

Action click: create new Action click: cancel filled
user account data from textbox
Fig 3.21 user interface prototype for change user account screen
51
3.5 Supplementary specification
3.5.1 Business rules of the new system
A business rule is effectively an operating principles or policy the software must

satisfy. It often pertains to access control issues, business calculation, or operating
policies and principles of the organization. Therefore our new system has the following
business rules:
BR1: login into the system
Users must have a valid user name and password to open the system.
The system validates user name and password and display the message for error entry
to the user.
BR2: crime registration
The authorized user fills Crime information
BR3: Validate Crime’s information
The authorized user registers the crime’s information and the system
validates it.
BR4: Retrieve crime information
The authorized searches the information from the data base table by using first
name of related records for each class.
BR5: Account change and creation
The system user enters previous password and account name to set the new
account and password.
The system accepts the new account name and set values to account database.
BR6: Delete crime information
Check information on the related database before deleting particular records
52
Do not delete all information from database
BR7: Generate report
System users select information from the related table want to be generated
The system accepts the valid users’ data and allows for generating reports
3.5.2 Constraints
As the customer has suggested for the new project development, they requires
building it up right from the scratch. The implementation language must be window
compatible as requested by the customer and we are requested to develop simple
application system which handles special task processing than the manual system.
The project is not to be outsourced. The feasibility study depicts that the design
analysis has to be so intensive to ensure reliability and quick response.
 The information desk should be allowed to insert, delete, update and
search information in its data.
 Administrator should access to all facilitates PCRMS provides and
direct access to the database.
 Detective team Generate report and to control work flow the detective
team should have access the data base and they will allowed to modify,
delete, insertion of records.
3.5.3 Change cases
Change cases used to describe the potential requirements of our system. They are
developed during requirement gathering and also during analysis as well as design
phases. It enables us to document requirement and our system may need to full fill future
changes. So that every changes based on technological trends can be supported by our
proposed system of Hasseb Ber police station crime record management. Our proposed
system developed based on the standard that enables to handle future trends; because the
development tool that used to achieve our objectives was visual studio 2008 which is the
most commonly used language in many software product companies today. At the time
we are developing an automated system which mainly accompanied on crime
registration, so that in the future the new system developed based on this domain whether
Web based or Networked.
The following issues can be handled by our system in future changes:
 Registration of crimes will be applied for any implication of technological trends
 Changing the system from automated to web based on technological variations
The system does not do under the following conditions:
 The station destructed by natural phenomenon like earth quack, flood
53
 System failure happened during run time
 Some parts of code procedures distorted
Chapter four
System design/using object oriented modeling
4.1 Introduction
The purpose of design is to determine how the system is going to build and to
obtain the information needed to drive the actual implementation of the system. It focuses
on understanding the model how the software will be built. System design is the detail
investigation of system elements from logical view.
4.2 Class type Architecture
It is the concept of organizing software design in to layer/collection of classes or
components that satisfy the common purpose such as implementing the user
interface or business logic of the system.
These layers are: User interface layer, controller/process layer, business/domain layer,
and persistence layer.
User interfaces
M
A
I
N
Application class/process S
Y
S
T
E
M
Business class/domain rules (Platforms)
Persistence data
Database/sources
(Historical data)
54
Chart 4, class type architecture for hasseb ber police crime record system
A, User interface layer

This is the first application layer of the proposed system that contains window request of
user name and password which the entire page will be opened. All systems of application
such as Detective page, Administrator page and Information Desk page will be opened
via the main page. In addition those interfaces contain their own application forms which
help to perform the new system activities. For example the Detective page of user
interface via the user account contains Crime registration page (screen), Exhibit page,
Plaintiff page, Accused page, Witness page, Report page and Account page for the
purpose of create, delete and change user accounts. And also the Administrator page
contains Account and report forms. Information Desk page contains Record form and
report forms.
If the user name and password enters correctly all the above application forms will
be displayed and applicable, unless the system displays an error messages to user of the
system.
B, Application class
Within the process layer, we define the process steps, the sequence in which they are
executed, the roles that execute them, and how the context data of a process is passed
between the process steps. A process is designed using Guided Procedures (GP). GP is a
framework for composing user-centric process flows. It offers the means to bond diverse
back-end applications and services into a single business workflow. It provides role-
based access to resources and guidance through the workflows at runtime, thus, helping
end users to identify and complete their tasks easily.
C, Domain layer (Business class)
This is about business layer such as Crime registration, Exhibit registration, Witness
person registration, Accused person registration and Plaintiff person registration.
D, persistent layer
This summarizes the ability to update, retrieve, and deleting records from database, kept.
E, Database layer
This is the layer that provides for correct information repository. Valid data stores in the
database for decisions and historical information references.
55
F, System layer (platforms)
This refers an operating system environment that used for run time application, example
Window-XP is the most preferable operating system during system testing and client
computers for desktop applications.
4.3 Design Goals
The design goals represent the desired qualities of the system and provide a consistent
set of criteria that must be considered when making design decisions. Based on the
nonfunctional requirements and the information elicited from the users, the following
design goals are identified.
 Inter Operability
From the instance of functional and non functional requirements the proposed system
of Hasseb Ber crime record system have good user friendly interface that provides to the
system user of the station easily interact and task operated.
 Availability
The system should available for any valid users of the station as long as the service
provider is available unless it is shutdown by the administrator.
 Expandability
If someone wants to modify and dynamically developing the new system based on the
standard of our system , the detail design of the developed system leads to the desire
situation what will be added for the future.
 Security
The purpose of developing computerized system of Hasseb Ber police crime record
system was to handle personal information of crimes with a great care through the
station. In order to achieve this security measure the following alternatives are taken as a
solution.
 Authentication: No one access the data rather than the authorized
person of the station. The system does not accessed by unauthorized
user, because the new system has a grant privilege for authorization and
authentication with user accounts. Due to this reason we choose to set
alternatives for system users to have their own user name and password
to access and process the data of crimes.
 Database security: Security feature of Access server to ban the database
from an unauthorized access will be implemented. Authorized users
through the system should only access the database. In order to handle
this, we have to do each system users have their own user account to
56
operate the system database via the system Administrator who controls
the whole system functions.
4.4 Class diagram

A class diagram is a component of unified modeling language that shows level
of association among classes and objects. It also shows multiplicity associations, that
means how many objects participate on the association. Class diagram shows the role of
objects or classes and aggregations. Mostly generalization specialization can be shown in
class diagram. Generalization specialization means a relationship between a general class
and one or more specialized classes.
In design, we model classes to represent the static structure of how the system will
be built. Class model in design is that focus on the solution domain. We have made
necessary modification that will cover the way toward the implementation of our system.
4.5 Class modeling

Design class modeling is used to model the static structure of how the software will
be built. In particular, class modeling shows classes, types, their internal structure, and
their relationships. And also shows a collection of (static) declarative model elements,
such as classes, interfaces, and their relationships, connected as a graph to each other and
to their contents.
The following diagram shows the class diagram of Kombolcha town Hasseb Ber police
station crime record management system.[15]
57
<<include>> <<UI>>
<<UI>> <<UI>>
Main page
Security login commit Accused
-ID : int
has -Name : str
has 1 -Date : int
1 1 -Wanted date : int
<<UI>> <<UI>> -Arrested date : int
1 Detective
Account -Charging date : int
<<UI>> <<UI>> -User name : str -Sex : str
-User name : str
Information Desk Administartor -Password : str -Age : int
-Password : str getreport
1 has 1 -User ID : int +Plaintiff ID : int
-User name : str -User name : str
get report -Education level : str
+Accept user name() -Password : str -Password : str
-User ID : int -User ID : int +Add values() -Nationality : str
+Accepty password()
+Search values() -Religion : str
+Record values() +Collect report() 1+Generate value()
+Generate report() +Generate report() +Submit value()
+Clear value()
n
+Exit()
1 1 1..*
<<UI>> Register
Create Account Update get evidence
Delete Account Uses
Change Account Made
+Accept username() +Search() accuse
+Accept username()
+Accept password() +Update values()
+Accept password() +Accept username()
+Accept account name() +Delete account() +Accept password()
+Set account type() +Change account()
+Set account ID() 1..*
*
1..* 0..* 1
<<UI>> <<UI>>
Witness <<UI>> <<UI>>
Crime
-Name : str Exhibit Plaintiff
-Crime date : str
-Sex : str ID : int -Name : str
-Crime name : str
-Age : int Item type : str -Sex : str
-Crime ID : int
-Religion : str Item name : str -Age : int
-Crime location : str
+Crime ID : int Amount exhibitted : str -ID : int
-Region : str
+Accused name : str Detective name : str -Date : int
-Zone : str
-Nationality : str Detective position : str -Religion : int
-Woreda : str
-Region : str Crime ID : int -Job : int
-Recorded date : str
-Zone : str -Region : int
-Detective name : str
-Woreda : str +Submit values() -Zone : int
-Kebele : str +Clear values() -Woreda : int
+submit values()
+Clear value() +Exit()
+Submit values() +Submit values()
+Exit()
+Clear Values() +Clear values()
+Exit() +Exit()
Fig4.1 class diagram for hasseb ber police crime record system
4.6 Documenting class diagram

Documenting class model is used to document the detail about the class as well as the
reasoning behind any trade off.
The following are the documentation of the class model of Hasseb Ber crime record
management system.
58
Class name: Crime
Crime class is a persistent that is used to contain crime information.
It has the following attributes and methods
Attribute Purpose Type length
Crime Date Represents date of crime action happened Integer 20
Crime Id Uniquely identifies crime code number Integer
crime Name Used to identify types of crime String 30
Crime location Used to identify crime specific location String 25
Region Represents the region that criminal action String 25

happened
zone Represents zone that criminal action happened String 25
woreda Represents woreda of criminal action happened String 25
Recorded date The date that the crime information recorded String 10
Detective name Represents the name of a person who records String 10

crime information
Table 4.1, Description of crime class attributes

Class name: accused (criminal person)
Attribute Purpose Type length
Accused ID Uniquely identifies criminal person identity integer 5
number
Accused name Represents the first and last name of criminal string 50
person
Accused date Identifies accused date of criminal accused by string 10
the accuser
Wanted date Represents starting date of a criminal Integer 13
searched by the police who did the crime
Arrested date Date of criminal arrested by the police Integer 13
Charging date Represents the official claim date made by the string 9
police that somebody has committed as a
crime
sex Identifies sex of accused criminal person string 6
age Used to identify age of Accused person integer 3
59
Plaintiff ID Used to identify identity of Defendant person
Educational level Used to represent education level of Accused string 20
person who did a crime
Nationality Represent citizenship of the Accused person string 20
Religion Used to identify Accused person religion who string 20
believes
Table 4.2, Description of Accused person class attributes
CLASS NAME: EXHIBIT

Attribute Purpose Type Length
Exhibit ID Refers the information about the integer 4
exhibit materials
Item Name Used to identify the name of material String 20
used during crime date
Item Type Types of item that cached by the String 50
police during observed
Amount The number of items that exhibited integer 4
Detective name The name of official person that String 25
record the item
Position Position of the Detective person String 25
Crime ID Uniquely identifies crime code integer 5
number
Table 4.3 Description of Exhibit class attributes
Class name: Witness

Witness ID Uniquely identify an identity of a person Integer 10
who sees the criminal action happened
Name Used to refer the name of a person who String 30
give the evidence
Sex Used to refer sex of the a person who give String 6
the evidence
60
Age Used to represent age of a person who Integer 3
give the evidence
Religion Religion of witness person who give the string 20
evidence about the crime
Crime ID Uniquely identifies crime code number Integer 5
Nationality Represent citizenship of a person who give String 30
the evidence
Region Refers region of a person who give the String 25
evidence
Zone Used to refer zone of a person who give String 30
the evidence
Woreda Used to refer Woreda of a person who sees String 20
criminal action happened
Kebele Used to refer Kebele of a person who sees integer 2
criminal action happened
Table 4.4 Description of Witness class attributes
Class Name: Plaintiff

Plaintiff Date Refers date of a Person who makes a formal String 10
complaint against some body in a court of law
Plaintiff ID Used to identify identity of Defendant person Integer ----
whose rights violated by the criminal
Name Used to identify name of Defendant person String 20
Sex Used to identify sex of Defendant person String 6
Age Used to identify age of Defendant person Integer ---
Religion Represents victimized person belief string 25
Job Represents specific job of a person who string 21
61
suffered by a victim
Region Represents region of a person who suffered by string 15
a victim
Zone Represents zone of a person who suffered by a string 15
victim
woreda Represents woreda of a person who suffered string 15
by a victim
Table 4.5, Description of Plaintiff person class attribute
4.7 state chart modeling
State chart diagram used to show the sequences of states that an object goes through
events that cause a transition from one state to another and the actions that result from a
state change. The following are the state chart diagram for Hasseb Ber crime record
system.
Register new Crime class

during crime registration
Crime
information
Submit
Submitted
[modify]
check
Checked
[return]
Consistent
validate
Validated
Registered
Fig 4.2, A UML state chart diagram for crime during crime registration.
62
Update Crime registration cla ss
during crime registration updated
Crime registered
information
Submit
Submitted
[modify]
che ck
Checked
[return]
Consistent
validate
Validated
Crime information
upda ted
Fig 4.3 ,A UML state chart diagram for Update crime registration during crime registration
Generate Regisration report

class during Registration report
Generated
Crime registered
information
Submit
[modify] Submitted
Check
Checked
[Return]
Consistent
Validate
Validated
Report
Ge nerated
Fig 4.4, A UML state chart diagram for generate registration report during report generat
63
Re cord crime informa tion
cla ss during Re cord informa tion
Crime
informa tion
Submit
[modify]
Submitte d
Che ck
Che cke d [Return]
Consiste nt
Valida te
Va lidate d
Information
re corded
Fig 4.5, A UML state chart diagram for record crime information during information recorded
Update record information

cla ss during crime updated
Recorded
information
Submit
Submitted
[modify]
checking
Checked
[return]
Consistent
validating
Validated
Information
upda ted
Fig 4.6, A UML state chart for update record information during crime information updated
64
Generate Administration report
class during Administration
report
Administrator
information
Submit
Submitted
[modify]
checking
Checked
[return]
Consistent
validating
Validated
Report Generation
Fig 4.7, A UML state chart diagram for Generate administration

report during Administration report generated.
4.8 Collaboration Modeling(using collaboration diagram)

Collaboration diagram is used to show the instances of the classes, their
interrelationships, and the message flow between them. It focuses on the structural
organization of objects that send and receive messages. Collaboration diagrams and
sequence diagrams are alternate representations of an interaction. A collaboration
diagram is an interaction diagram that shows the order of messages that implement an
operation or a transaction, where as a sequence diagram shows object interaction in a
time-based sequence. Collaboration diagram in design phase shows the semantics of
mechanisms and the logical design of the system.
The following collaboration diagrams show Hasseb Ber police station crime record
system. Each collaboration diagram provides a view of the interactions or structural
relationships that occur between objects and object-like entities in the current model.[15]
65
2: user name and password <<UI>>
<<Actor>>
security login
Detective
1:window request user name and

password
3:checkout user name and password
6: main menu displayed

4:correct user name and password
5:call to display
<<UI>>
Main menu
<<DB>>
login database
Fig 4.8, A UML collaboration diagram for Detective security login Basic course of action.
2: user name and password <<UI>>

<<Actor>>
security login
Detective
1:window request user name and

password
5: login page
3:checkout user name and password

4:incorrect user name and password
<<DB>>
login database
Fig 4.9, A UML collaboration diagram for Detective security login Alternative course of action.
66
<<Actor>> 2:User name and password <<UI>>
Information Desk Security login
1:window request user name an password
3: checkout user name and password

6:main menu displayed 4: correct user name and password
5: call to display
<<UI>> <<DB>>
Main menu login database
Fig 4.10, A UML collaboration diagram for Information Desk security login Basic course of action.
<<Actor>> 2: User name and password <<UI>>

Information Desk Security login
1:
window request user name an password
4: Incorrect user name and password 3:checkout user name and password
<<DB>>
login database
Fig 4.11,A UML collaboration diagram for Information Desk security login Alternative course of action.

Administrator Security login
3: checkout user name and password

6:main menu displayed 4: correct user name and password
5: call to display
<<UI>> <<DB>>
Main menu login database
Fig 4.12, A UML collaboration diagram for Administrator security login Basic course of action.
67
Administrator Security login
4: Incorrect user name and password 3:checkout user name and password
<<DB>>
login database
Fig 4.13, A UML collaboration diagram for Administrator security login Alternative course of action.
3: New crime registartion form will be displayed

<<UI>> 6:conformation
Register new 10: successfully registered <<Actor>>
crime Detective
4: Fill personal information about crime

5:click on submit
7:yes 1: wants to register new crime
8: validate data
9:valid
<<DB>> 2: call to display

HBPCRS
<<UI>>
Main menu
Fig 4.14, A UML collaboration diagram for new crime registration Basic course of action.
68
3: form will be displayed
10:New crime registration form
<<UI>> 6:conformation
<<Actor>>
Register New
Detective
crime
4: fill crime information

5:click on submit
7:no
1: wants to Register new crime

8:validate data
9:Not valid 2:call to display
<<UI>>
Main menu
<<DB>>
HBPCRS
Fig 4.15, A UML collaboration diagram for Register New crime Alternative course of action.
3: form displayed
13:crime record updated successfully
<<UI>> 7:searched result displayed <<Actor>>

Update crime Detective
registration
4: search record information
8:mark data to be changed
9:click update(delete function invoked)
5: check availablity 10:insert record inplace then click
11:validate data update again(add function invoked)
6: Available
1: wants to update crime registration
12:valid 2: call to display
<<DB>>
HBPCRS <<UI>>
Main menu
Fig 4.16 , A UML collaboration diagram for Update crime registration Basic course of action.
69
3: form displayed
7:message displayed
8:update crime registration form
<<UI>> <<Actor>>
Update crime Detective
registration
5: check availablity of crime information
6: Not Available
1: wants to update crime registration
2: call to display
<<DB>>
HBPCRS <<UI>>
Main menu
Fig 4.17, A UML collaboration diagram for Update crime registration Alternative course of action.
3: form displayed
<<UI>> 8:view report
Generate <<Actor>>
registration report Detective
4:select types of report to be generated
5: check availablity 1:wants to generate registration report
6:Available 2: call to display

7:report generated
<<DB>> <<UI>>
HBPCRS Main menu
Fig 4.18, A UML collaboration diagram for Generate registration report Basic course of action.
3: form displayed
<<UI>> 8:Generate registration report form
Generate <<Actor>>
registration report Detective
4: select report to be generated
1: wants to generate registration report

5: check availablity
2: call to display
6:report information is not available
7:report is not generated
<<DB>>
HBPCRS <<UI>>
Main menu
Fig 4.19, A UML collaboration diagram for Generate registration report Alternative course of action.
70
3: form displayed
<<UI>> 7:Successfuly record crime information <<Actor>>
Record crime Information
infromation Desk
4: Select crime information

to be recorded
5: Check availablity in database

1:wants to record crime information
6:Available
2: call to display
<<UI>>
<<DB>> Main menu
HBPCRS
Fig 4.20, A UML collaboration diagram for Record crime information Basic course of action.
3: form displayed
<<UI>> 7:Record crime information form <<Actor>>
Record crime Information
infromation De sk
4: Select crime information

to be recorded
5: Check availablity in database

1:wants to record crime information
6:Information is not available in database
2: call to display
<<UI>>
<<DB>> Ma in menu
HBPCRS
Fig 4.21, A UML collaboration diagram for Record crime information Alternative course of action.
3: form displayed
13:record updated successfully
<<UI>> 7:searched result displayed <<Actor>>

Update record Informatio
information n Desk
8:mark data to be change d
9:click update(delete function invoked)
5: check availablity 10:insert record inplace then click
11:validate data update again(add function invoked)
6: Available
1: wants to update record crime information
12:valid 2: call to display
<<DB>>
HBPCRS <<UI>>
Main menu
Fig 4.22, A UML collaboration diagram for Update record information Basic course of action.
71
3: form displayed
7: message displayed
8:Update record information form <<Actor>>
<<UI>>
Update record Information
information Desk
5: Check avilablity
6: Not available
1: wants to update record crime information
2: call to display
<<DB>> <<UI>>
HBPCRS Main menu
Fig 4.23, A UML collaboration diagram for Update record information Alternative course of action.
3: form displayed
<<UI>>
8:view report <<Actor>>
Generate
record report Infromation
Desk
4:Select information to be generated
5: Checkout availablity 1:wants to Generate record report
2: call to display
6: Available
7:report generated
<<UI>>
<<DB>> Main menu
HBPCRS
Fig 4.24, A UML collaboration diagram for Generate record report Basic course of action.
3: form displayed
<<UI>>
8:Generate record report form <<Actor>>
Generate
record report Infromation
Desk
4:Select information to be generated
5: Checkout availablity 1:wants to Generate record report
2: call to display
6: Not available
<<UI>>
<<DB>> Main menu
HBPCRS
Fig 4.25, A UML collaboration diagram for Generate record report Alternative course of action.
72
3: form displayed
<<UI>> 8:View report <<Actor>>
Generate Administrator
Admin report
4:Select report to be generated
5: Checkout availablity 1: wants to Generate Administration report
2: call to display
6: Available
7:report generated
<<UI>>
<<DB>> Main menu
HBPCRS
Fig 4.26, A UML collaboration diagram for Generate Admin report Basic course of action.
3: form displayed
<<UI>> 8:Generate Admin form <<Actor>>
Generate Administrator
Admin report
4: Select report to be generated
5: Checkout availablity 1: wants to Generate Administration report
2: call to display
6: Not Available
<<UI>>
<<DB>> Main menu
HBPCRS
Fig 4.27, A UML collaboration diagram for Generate Admin report Alternative course of action.
4.9 Component modeling (Using component Diagram)

A Component diagram is used to show a subset of the components or packages of
components in the system and their relationships. Component diagrams provide a
physical view of the current model of the proposed system. A component diagram shows
the organizations and dependencies among software components, including source code
components, binary code components, and executable components.
73
Crime Registration
<<Application>> Data access
Crime
management Data access
Update Crime
Registration
<<Infrustructure>>
Generate Security
<<Application>> Data access Registration report
System
Management
Record crime <<Infrustructure>>
information Persistent
Update record
<<Application>> information
Security
Management OLEDB
Generate record
information
Generate Crime DB
Administration report
Change Account
4.28, A UML component diagram for Hasseb Ber police crime record management system.
4.10 Deployment modeling (using deployment diagram)

A UML deployment diagram depicts a static view of the run time configuration of processing nodes and
the components that run on those nodes. Deployment diagram is used to show the hard ware of the system
the software that is installed on that hardware and the middleware used to connect the disparate machines to
one another. It also shows how the hardware and software components work together. The following
deployment diagram shows the above component model of Hasseb Ber police station crime record system
and process flow.
Fig 4.29, A UML Deployment diagram for Hasseb Ber police Crime record management system
74
4.11 Object model (Using object diagram)
The notation used on UML object diagrams is very simple they show objects and the
connections among them. UML object diagrams are effectively notational subsets of
UML communication diagrams, although object diagrams are used to explore structure
whereas communication diagrams explore behavior. It is common for object diagrams to
evolve into communication diagrams simply by adding messages to the diagram.
Police station
D2: Department
KTHBPS Name: Administrator
D1: Department D3: Department

Name: Detective Name: Information Desk
Fig 4.30 object modeling diagram
4.12 User interface hierarchy
User interfaces describes how the user interacts with the new system interfaces. User
interface guides the user with user friendly commands how to operate the system. Most
of the time user interfaces does not need training of users, because users expected only
now commands. User interface is a complex task that focuses all the applying common
UI design principles and techniques, applying the station chosen interface design
standards and involving our UI design. The following user interface describes Hasseb Ber
police station crime record system operating environment.
75
Home Page
Security login
Main Page
Click on click on click on
Detective Administrator Information Desk

Page Page Page
Fill Fill Fill
Account Account Account
Click on a menu
Crime page Accused page Witness page Exhibit page Plaintiff page
Click on click on click on click on
Click
Report form Update form Click on Record form
Click on
Click on
Application user interface hierarchy for Hasseb Ber police station crime record system
FIG 4.31 User interface hierarchy
76
4.13 User interface Design
Fig 4.32 Spalash Screen For HBPCRMS
This screen has two menu strip File And Account when to click on file then can select
open then opend login form ,close option also used to close spalsh screen.in the other
hand when click on the account then go to account form.
77
Fig 4.33, login form for police crime record management system
Fig 4.34, Main form of police crime record management system
This form contain three menu strip Choose Departments, Back and Close .when click
on choose departments menu strip used to select the privilege that detective
,Information disk or administrator. Back menu strip used to return back to login form,
and the last close used to closed the main page.
78
Fig 4.35, Detective main form of police crime record management system
Fig 4.36, Crime registration form for police crime record management system
Fig 4.37, Plaintiff form for police crime record management system
79
Fig 4.38, Accused form for police crime record management system
Fig 4.39, Exhibit form for police crime record management system
80
Fig 4.40, Crime registration form for police crime record management system
Fig 4.41, Account create form for police crime record management system
81
Fig 4.42, information desk form for police crime record management system
82
Fig 4.43, Admin form for police crime record management system
Sample tables
Table 4.5 Crime registration table for police crime record management system
83
Table 4.6 Plaintiff table for police crime record management system
Table 4.7 Accused table for police crime record management system
84
Table 4.8 Exhibit table for police crime record management system
Table 4.9 Witness table for police crime record management system
85
Table 4.10 Relationship table of Detective main form table for police crime record
management system
86
Table 4.11 Administrator table for police crime record management system
87
Chapter FIVE
SYSTEM CONSTRACTION/IMPLEMENTATION
5.1 Introduction
System implementation gives the physical coding of the system ,the coding was done in
VB.net language .the selection of vb dot net language is based on the version of the
system and also it is the most power full language than other language we know.
In this chapter the sample coding for implementation and testing ways will be
described.
5.2 Coding (coding as annex)
After other phases of the system development is completed coding takes next position.
Coding includes implementation of user interface, implementation of database and
logical implementation.
In the following interface implementation, database implementation and logical
implementation are discussed in context of the whole system.
Implementing Interface
In this part implementation of pages of each module is done. Pages are divided in to
interface and user interface. That is for security measurement. Rather than using same
interface its better using independent one is better.
Database Implementing
We have used relational database management system. It supports different activities like
deleting, updating, retrieving, searching, displaying and other functionalities. The data
base used for database implementation is Microsoft access 2007. Database allows access
to police crime record information to users.
sample code for implementation

Sample coding for inserting or adding the record, deleting, searching, update or any
other operation is done by this coding of vb.net.
Imports System.Data
Imports System.Data.OleDb
Dim cnnOLEDB As New OleDbConnection
Dim cmdOLEDB As New OleDbCommand
Dim cmdInsert As New OleDbCommand
88
Dim cmdUpdate As New OleDbCommand
Dim cmdDelete As New OleDbCommand

'code for open database
cmdOLEDB.Connection = cnnOLEDB
cnnOLEDB.Open()
Dim rdrOLEDB As OleDbDataReader = cmdOLEDB.ExecuteReader

' Set connection on the form load event
Private Sub Form_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load
con.ConnectionString = conne
con.Open()
End Sub
Private Sub DisplayButton_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Display.Click
'Display data Table on datagrid
Dim ds As New DataSet()

ds = New DataSet("CrimeTable")
Dim conne As String = _
"Provider=Microsoft.ACE.OLEDB.12.0;" & _
End Sub
Private Sub Submitbutton_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Submit.Click
'check whether add inserted data or Submit values to database
cmd.CommandText = "INSERT INTO
AccusedTable(Accusedid,Accusedname,Sex,Age,Accuseddate,Wanteddate,Arrest
eddate,Chargingdate,PlName,Educationallevel,Nationality,Religion,Plainti
ffID)" & _
"VALUES(" & Me.txtacid.Text & ",'" & Me.accname.Text & "','"
& Me.cbosex.Text & "', '" & Me.txtage.Text & "','" & Me.txtacdate.Text &
"','" & _
Try
cmd.ExecuteNonQuery()
'clear all fields after add data to database
txtacdate.Text = ""
txtage.Text = ""
txtardate.Text = ""
txtchdate.Text = ""
txtedlev.Text = ""
cbocount.Text = ""
cboreligion1.Text = ""
txtacdate.Text = ""
cbosex.Text = ""
txtacid.Text = ""
accname.Text = ""
txtplname.Text = ""
txtpllid.Text = ""
M Catch ex As ExceptionsgBox("You Are record
Successfully And Add New")
MsgBox(ex.Message, MsgBoxStyle.Exclamation)
End Try
cmd = Nothing
cos.Dispose()
89
End Sub
Private Sub LoginButton_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Login.Click
Dim con As New

OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Data
Source=D:\connection databases final\interface
2004\LOGIN.VB\LOGIN.VB\bin\Debug\account.accdb")
Dim cmd As OleDbCommand = New OleDbCommand("SELECT
username,password FROM Table1 where username=? and password=?", conn)
con.Open()
If Me.cbousername.Text.ToLower() = read.Item("username").ToString And
Me.password.Text.ToLower = read.Item("password").ToString Then
Form2.Show()
Me.Hide()
Else
If String.IsNullOrEmpty(Me.cbousername.Text) Xor
String.IsNullOrEmpty(Me.password.Text) = False _
Then
MsgBox("User Login unsuccessful,pls type the
correct details and select the correct usertype")
End If
End If
'validate manager
If Me.cbousername.Text.ToLower() =
read.Item("userName").ToString And Me.cbousername.Text.ToLower =
read.Item("password").ToString Then
MsgBox("Login successful")
Form2.Show()
Me.Hide()
Else
If String.IsNullOrEmpty(Me.cbousername.Text) Xor
String.IsNullOrEmpty(Me.password.Text) = False _
Then
MsgBox(" Login unsuccessful,pls type the correct
details and select the correct usertype")
End If
End If
con.Close()
Else
MsgBox("Login unsuccessful,no connection")
End If
con.Close()
read.Close()
Catch ex As Exception
MessageBox.Show(ex.Message)
Finally
con.Close()
End Try
End Sub
90
Private Sub delete_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles delete.Click
'delete values from the table
cmdDelete.CommandType = CommandType.Text
'the command perform the action within the connection
cmdDelete.Connection = con
cmdDelete.ExecuteNonQuery()
End Sub
'creating connection string

Dim conne As String = _
"Provider=Microsoft.ACE.OLEDB.12.0;" & _
'search results from Database for Update
Dim com As OleDbCommand
Dim srch As OleDbDataReader
com = New OleDbCommand
com.Connection = con
com.CommandType = CommandType.Text
com.CommandText = String.Format("select * from AccusedTable
where PlaintiffID ='{0}'", txtsearch2.Text
srch = com.ExecuteReader
If txtsearch2.Text = "" Then
MsgBox("please enter PlaintiffID for search",
MsgBoxStyle.Question)
'Dim Accuseddate As DateFormat

IsDate(txtacdate.Text)
Else
If srch.Read() Then
txtacid.Text = srch("Accusedid")
accname.Text = srch("Accusedname")
cbosex.Text = srch("Sex")
txtage.Text = srch("Age")
'txtwitid.Text = "0"
'txtcname.Text = "0"
Else
MsgBox(" Such Record is not found in the Database",

MsgBoxStyle.Critical)
End If
End If
'validation not to accept numbers i.e it only accepts text values
If Not IsNumeric(txtplname.Text) = False And txtplname.Text <>

"" Then
MsgBox("Invalid Entry", MsgBoxStyle.Critical, "Please Enter
Number Values")
txtplname.Text = ""
End If
Private Sub UpdateToolStripMenuItem1_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
UpdateToolStripMenuItem
'delete values from the table To update
91
Dim del As DialogResult
del = MsgBox("Are you sure you want to Delete Record?",
MsgBoxStyle.YesNo, "confirm!!!")
If del = Windows.Forms.DialogResult.Yes Then
cmdDelete.CommandText = "DELETE RECORDS FROM
AccusedTable WHERE Accusedid =" & txtacid.Text & ";"
cmdDelete.CommandType = CommandType.Text
End Sub
5.2.1. Algorithm development
In chapter four while the system is being designed we have shown different functions.
Some major functions and their respective algorithms are shown below and the rest are
annexed.
Register New Crime
Register New Crime ()
Display Register New Crime form
Accept input from the user
If "Save" button is clicked
Check for validity of data entered
If invalid data is entered Prompt the user to correct the error by displaying
message "Insert value"
Open database
Open tables that are related with Crime
Check the uniqueness of the CrimeID entered
If the CrimeID is not unique
Prompt the PS to enter another CrimeID or criminal information
Insert the information filled out on the form into the table
Save change made to the table
Close the table
Close the database
92
If everything is successful
Display message "Register crime successfully completed"
Else
Display an error message
If "clear" button is clicked
Clear all the inputs and refresh the form and display the form
End function
Update Crime registration
updateCrime()
Open database
Open the tables related to Crime registration
Retrieve the personal information for the specific Crime
Display the information on the screen
Allow the user to make changes to that information
If "update" button is clicked
If invalid data is entered
Prompt the user to correct the error
Else
Update the information on the tables
Save change made to the tables
Close the tables
Close the database
93
Display message "Crime registration updated successful"
Else
If "cancel" button is clicked or the form is closed
Close the database without making any change
End function
View Crime registration
viewCrime()
Open the database
Open the table called "Crime"
If there is no Crime registered
Display a message "any Crime is not registered"
Else
Retrieve the Crime those are registered
Close table
Close database
End function
Search Crime
SearchCrime ()
Display a search Crime screen
Accept input
94
If "search" button is clicked
Open database
Open the table called "Crime"
If there is no Crime registered
Display a message "any Crime is not registered"
Else
Search the table with the keyword from the form
If a mach is found
Retrieve the Crime registered
Else
Display a message "the data no match is found"
Close table
Close database
End function
Record Crime Information
Recordcrime ()
Display Crime record form
Accept input from the user
If "submit" button is clicked
Prompt the user to correct the error by displaying message "Insert value"
95
Open database
Open tables that are related with Record
Check the uniqueness of the record No and match crimeID from crime record table
If the recordNo is not unique or crID is not match from crime record table
Prompt the user to enter another recordNo or record info
Insert the information filled out on the form into the table
Save change made to the table
Close the table
Close the database
Display message "Record information successfully completed"
Else
If "clear" button is clicked
Clear all the inputs and refresh the form and display the form
End function
Update Crime Record
Updaterecord ()
Open database
Open the tables related to crRecord
Retrieve the Record information for the specific Crime with specific day
Allow the user to make changes to that information
96
If "update" button is clicked
Prompt the user to correct the error
Else
Update the information on the tables
Save change made to the tables
Close the tables
Close the database
Display message "Record updated successful"
Else
If "cancel" button is clicked or the form is closed
Close the database without making any change
End function
View Record Crime information
ViewRecord ()
Open the database
Open the table called "Record"
If there is no Crime Record
Display a message "any Information is not record"
Else
97
Retrieve the Information those are recorded
Close table
Close database
End function
Search Crime Record Information
Searchcrimerecordinformation ()
Display a Record search information screen
Accept input
Open database
Open the table called "Crimerecord"
If there is no information record
Display a message "any crime information is not record"
Else
Search the table with the keyword from the form
If a mach is found
Retrieve the crime record information
Else
Display a message "the data no match is found"
Close table
Close database
98
End function
Open database
View administrator report
Viewreport ()
Open the database
Open the table called "register crime" or “record crinformation”
If there is no crime register or Crime Record
Display a message "any Information is not register / record "
Else
Retrieve the Information those are registered/ recorded
Close table
Close database
End function
5.2.2 Flow chart Design

A flowchart is a common type of chart that represents an algorithm or process showing
the steps as boxes of various kinds, and their order by connecting these with the arrows.
Flowcharts are used in designing or documenting a process or program in various fields
Flow chart is a diagram that depicted or explaining the logic flow of single process or
method.
99
Flow chart primary artifact of structured or procedural modeling
HBPCRMS
Login Login form Cancel
Login into the system
Exit Main page Back
Choose
Detective Crime button
Administrator page
page
Submit
Exit Witness button
Administrator Information
form Display
desk page
Search Information form
Back Delete Plaintiff button
Record in to the
Crime record table
Fill crime
Display crime Exit
Search
information
Registration
Accused form
form
Submit Back Delete
Exhibit form
View crime registration
report from registration
table
Generate administrator
Fig.Flow chart
Fill information primary artifact of structured or procedural modeling Click on crime button
report from
HBPCRMS in thedata
crime
baseform
5.3 Hardware and Software acquisitions
5.3.1 Hardware Acquisitions

Submit in to the
Registration table For the system software installation a Pentium 4 desk top with high hard
Data base disk drive (HDD) and memory capacity, high View crime Record
processor infogood
speed and
from Crime record table
resolution monitor are required. For taking regular back-ups of the data,
secondary storage devices such as CDs are used.
100
For exchanging data between server and client our team use UTP cable
Cat 6 and to connect two ends to both computer our team use RJ-45.
Besides all these, to protect data loss due to power interruption we use
UPS (uninterrupted power supply).
5.3.2 Software Acquisitions
Since the technologies used for front-end and back-end application are developed using
windows operating system. Our HBPCR system can be installed in windows operating
system environment such as windows 2000 or windows XP.
5.4 Data preparation and Installation
Data preparation:- Before installing the system the following criteria should be
Fulfilled.
The recent Windows operating systems such as windows 2000or Windows

XP should be installed in the personal computer.
Personal computer with high storage memory and HDD (minimum of 40

GB).
A powerful UPS should be available.
Detective person and HBPCRS Administrator office is equipped with the

secure cables and number of sockets the office should have proper
ventilation.
Before installing the system the following criteria should be fulfilled.
The recent Windows operating systems such as windows 2000or Windows

XP should be installed in the personal computer.
Personal computer with high storage memory and HDD (minimum
of40GB).
A powerful UPS should be available.
Detective and HBPCRS administrator office is equipped with the secure

cables and number of sockets the office should have proper ventilation.
101
Installation:-The HBPCRS software can be installed in the HBPCRS office Desktop
computer that satisfies the hardware and software requirements that are discussed above
and database server are installed in the HBPCRS office.
5.5 Testing
Developing software is a complex business. No matter how hard we try, we won’t be able
to eliminate all faults simply by going through the phases of requirements, analysis,
design, specification, and implementation .however through good practice we can make
sure that the most series fault does not occur in the first place. In addition we need a
separate testing phase, with the goal of elimination all remaining faults before release.
Testing a code and other artifacts as we go along the development of the system help us
to acquire the following advantage:
If improves the quality of the software
It reduces the cost of the testing phases
It shows the programmers that they are making real progress
It reduces the number of faults that are linked to the program

during the testing phase.
It helps programmers to reorganize their code, for style

performance reasons, without breaking anything that has already
written.
To simplify the testing process the project team followed the different types of tests that
break the testing process up into the distinct levels. These types testing are unit testing
integration testing and system testing.
Unit test: Each module is tested alone in attempt to discover any error in its code but
since modules exist and work with other modules in programs and system they must be
tested in longer groups.
Integration test: The process of bringing together all of the modules that a program
comprises for testing purposes. Modules are typically integrated in top won incremental
fashion.
System testing: a test performed on an entire system Ensures that application programs
written and tested in isolation work properly when integrated into the total system.
5.6. Start-up strategies
The system start by enter password and user name in the HBPCRMS login form then
display the main page of the system.
102
Chapter six
CONCLUSION AND RECOMMENDATION
In developing this system we have observed that there are other systems
that need to be
Automated in the Kombolcha Town Hasseb Ber police station. In relation to our
project, the manual System hinders the Police station not to use its resources
efficiently and serve its people effectively. However, we have seen great interest
of the stakeholders of the police station to automate some manual systems that
needs to be automated.
After spending three to four months on developing this project, we have
tried to automate the new computerized police crime record management system
of the station.
The crime record system needs some improvements before it is applied to a
real application; which is created due to the time shortage, shortage of experience
and other technical Problems. Taking these problems in to account, if the materials
requested are provided and all the installation process is completed; the patient
information system will work well.
More over, the system will bring a radical change on current working
condition of the police station. Specially, to operations concerned the record office
The police crime record management system conversion from the old
system to this new system is based on a radical change which needs a complete
acceptance from the users of the system as
Was hoped and agreed with stakeholders at the beginning of this project.
103
Finally, we concluded that the police crime record management system will
be taken as a means for the Police station to deliver efficient and effective report
generating, crime recording and information sharing to the police station.
Conclusion
The computers and computerization technology in the world is growing along the fast
lane where Ethiopia is attempting to run along this lane in which there are achievements
recorded. And as years, pass by, we are pretty much confident that extent progress will be
made in our country.
System development is one of the ways in which we can make progress by making a lot
of tasks easier and the over all use of computers along with the developed systems is
believed to lead to the peak of the technology standard.
The system that we have developed is one that is relatively minor in its type, but can be
a break through for other researcher to further implementation on the system.
Concussively, the issues raised in the summary of finding will be discussed in this
conclusion part. There for, we conclude
1. The program complete in modular forms and in its overall status
where it consists of all the necessary features required for a
system to call a system. The testes and evaluations made show
that the system is full fledged and complete.
2. The developed system can conclusively be called user friendly
in which the form developed are suitable for use by any user
who will defiantly get accustomed to the system’s environment
easily. There for, the Kombolcha Hasseb Ber PCRMS is quite
user friendly for use by simple user at it should be.
3. It can be conclude that the graphical user interface is fully
developed with all the necessary text boxes, buttons, tables and
textual representation with the use of the international language
i.e. English on all expressive labels that are used in the system.
All the forms required exist in the system .there fore, we can say
that the essential forms are available and are in proper order.
104
4. The system is strongly secure with the use of identification
(login name) and a password where unless otherwise one has the
proper and id, she/he can access or get into the system. Also
there is a mechanism for changing that existed before into a new
one for greater security, since periodical changing once
password will leave the user on the safe side.
5. The database of the system is properly organized with fulfilled
tables on their connection is appropriately made with the right
forms through the coding. All the necessary tables are created
effectively and in a sufficient manner.
6. The system is exhaustive in such away that it consists of all the
features a
7. PCRS should consist of, but the system conclusively can be seen
as one that can be implemented further with the inclusion of the
financial aspects in detail. Other than that, our system is
believed to be inclusive of many of the features a PCRS should
include.
8. Data reception in our system is accomplished in quite consistent
way in which there is no major appearance difference on the
forms and the buttons creation and once some one is accustomed
to one form’s appearance, the other will not be difficult to get
used to .therefore, consistency is observed in our system’s over
all appearance and data reception (input) method.
All in all , Kombolcha Hasseb Ber PCRMS developed is a system that definitely going
to be help full if it is going to be introduce and applied in the office and with further
enhancements , it can turn into a great system with many great features for out standing
results in whatever is done around the kombolcha town.
RECOMMENDATION
Finally, we the project team members recommend the following points:
105
This system will give a solution for some of the problems in the record
management system of the police station, but the police station should prepare a
conducive environment to test such systems.
 There should be a healthy working environment, specifically in regard to
the database
Administration that we are going to assign the total authority to view the security
database and handle problems that may arise in the application of the police crime
record management system. So it is better to assign this position to some one who
is trustworthy, accountable and responsible person.
 The police station has to fulfill all the infrastructures needed for the system
implementations. In addition, all the specifications mentioned for the hard
wares and soft wares are Mandatory.
 The different data manipulators in the police crime record management
system, who are the main users of the police crime record management
system, must have knowledge about this technology.
 We recommend to the University’s department of Information System to
provide its. Students the opportunity to work on developing systems that
are aimed in solving the real Problems of the society.
The last but not least, developed considering the expansions that the record office
of the station will undergo in the near future, we recommend the
The police station uses this system as a basement and sees how its problems can
be solved.
References
[1]:- Kombolcha town Hasseb Ber police station Human resource and allocation office
manual documentation book on page 104.
[2]:- Jaffrey McManus, Home Encyclopedia Databases of SQL and Access, 1st edition
1997
106
[3]:- RPT software, URL:http://www.rptsoftware.com/aboutus/microsoft access database/
retrieved on Jan 14, 2012
[4]:-Michael A. vine, complete reference for VB.NET 2008, 2nd edition, 2001
[5]:- M.Jacob, complete reference for VB.NET 2008, 3rd edition, 2005
[6]:- Searchcio Mid market, URL: http://searchcio
midmarket.techtarget.com/definition/Rational-Rose, retrieved on Jan 14, 2012
[7]:-IBM, URL: http://www-01.ibm.com/software/rational/ ,retrieved on
February13,2012
[8]:- Terry Halpin, rule and principal guidance for democracy, 1997, Kombolcha
[9]:-S.A Kalkar, Software Engineering, 3rd edition, 2007
[10]:-Solomon Grudey, object oriented primer, 2nd edition, 2001
[11]:- Solomon Grudey, object oriented primer, 2nd edition, 2001
[12]:-Brian Wilkerson, Object oriented design 1st edition, 2004
[13]:- S.A Kalkar, Software Engineering, 3rd edition, 2007
[14]:-Rebecca and Lauren Wienner, object oriented design, 1st edition, 2004
[15]:- Solomon Grudey, object oriented primer, 2nd edition, 2001
Appendix :- የኮምቦልቻ ከተማ ሀሰብበር ፖሊስ ጣቢያ የወንጀለኛ መመዝገቢያ

ስርዓት(Manual crime recording system)
1.የተከሳሸ ስም ከነአያት__________________
2.የተከሳሸ ብዛት____________________
ወንድ _________ ሴት_____ ድምር_______
3.የትምህርት ደረጃ________________________
4.የቤተሰብ አቋም________________
107
5.ስራ________________
6.ክልል_________ ዞን_____ ወረዳ _____ ቀበሌ ________
ልዩ ቦታ_________ የቤት ቁጥር _________ ስ/ቁጥር ____________
7.የተከሰሰበት የወንጀል አይነት_____________
8.ክስ የተመሰረተበት ቀን_____________ የታሰረበት ቀን_______________
9.የወንጀል እለት ሁለገብ መዝገብ ቁጥር(የአለት መመዝገቢያ)_________________
10.መለያ ቁጥር_________________
11.የእዝግቢት መዝገብ ቁጥር (የደበደበበት መሳሪያ)___________
12.የከሳሸ ስም ________ ስራ ________ እድሜ ____ ፆታ________
ክልል:_________
13.የጉዳቱ መጠን __________መርማሪዉ አካል___________
14. ለአቃቢ ህግ የተላከበት ቀን__________________________
15.የቀረበለት ዐ/ህግ /ወረዳ ___________________________
16.የዐ/ህግ መዝ/ቁጥር _________________________
17.ክሱየተመራለት ፍ/ ስም ______________ የፍታ/መለያ ቁጥር ________
18.የፍርዱ ዉሳኔ / ቅጣት_______________________________
Source, Kombolcha town Hasseb Ber police station Detective office
108

PCRS in Wollo

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PCRS in Wollo

Uploaded by

Copyright:

Available Formats

Wollo University

Kombolcha institute of technology

Automated Police crime record management system

Submitted to the School of Graduate Studies of Wollo

Advisor, Demeke Shumeye (Msc)

List of diagram or figuers

Fig 4.13, A UML collaboration diagram for Administrator security

1.4.4 Schedule Feasibility

Phases Activities and tasks deliverables

1.6 Significance of the project

Benefiaries of the Project

1.7 Scope of the project

1.8.1 Data collection methods

Visual Basic.NET:-for interface designing &programming the process Logic

Rationale rose:-for drawing the different artifacts of the requirement analysis

Microsoft word:-for documentation of each phase.

1 Information gathering 11/18/2011 11/22/2011 3d

2 Planning phase 11/25/2011 12/29/2011 5w

3 Analysis phase 12/30/2011 1/27/2012 4w 1d

4 Design phase 1/27/2012 2/23/2012 4w

5 implementation 2/24/2012 4/23/2012 8w 2d

6 testing 4/24/2012 5/10/2012 2w 3d

Chart1.1 Schedule of the project

Item Quantity Unit Price Total Price

Role of personal clerks

2.2 Problem of the Existing system

-In accuracy of data and information may produced

 Security and control problem

 Automating the HBPCRS particularly within the Station of sub-

Option analysis is means of evaluating the alternative solutions in terms of their

 The new system can be implemented without changing the organization

 The new system does not require more human labor.

 Processing data with high speed and short hand form.

Overview of the proposed system

Record crime information

fig 2.0 Essential use case diagram

Essential use case description

Basic course of Actions

The user interface is user friendly of graphical user interface. There is an

It functions with the latest operating system

It handles error corrections and prompts users for correction

 Microsoft OLDEB Data control object 6.0

 Basic support for Visual Basic.NET components

System or product function

Fig 2.1, user interface prototype for crime registration

Record crime information

Crime information Additional information

Button: search Button: clear

Generate crime report

Button: search Button: print

Fig 2.3 user interface prototype for generate report

User characteristics for system interaction

Table 2. Class responsibility collaborator card for Detective manager

Table 2.1 Class responsibility collaborator card for Administrator

Table 2.2 Class responsibility collaborator card for Information Desk

Table 2.3 Class responsibility collaborator card for crime class

Table 2.4 Class responsibility collaborator card for Accused class

Table 2.5 Class responsibility collaborator card for Exhibit class

Table 2.6 Class responsibility collaborator card for Witness class

2.4 Nonfunctional requirements

Object Oriented Analysis

3.1.2 Documenting use cases