Chapter two

2. Business Area Analysis and Requirement Definition

2.1. Business Area Analysis

Business Area Analysis evaluates how well business processes, business rules, business data,

organizational structure, and people skills match the mission of the organizational unit. It

develops recommended process improvement actions which can include quick fixes for serious

problems, modifications of existing automated systems, workflow adjustments, and new

development of an automated system or the initiation of a business process

2.2. Study of the activitiesThe activates or tasks that performed in debre markose city police administration regarding to

crime management system are the following

Recording new criminal case

Generate different report

Generate different summons forms

Delete ,update user accounts

Register plaintiff ,and criminals

Recording decisions files

View decissons files

2.3. Problem of the existing systemIn the existing crime management system , most of the operation are done manually like sending

complaints, taking actions against crimes ,viewing status .so with the existing system if anybody

wants to complain against crimes he must do it through the police .if we are doing the system

manually ,so many minor errors will occurs.

Some of the problem of the existing system are as follows:

More man power.

Time consuming

Consumes large volume of pare work.

 Needs manual calculations.

No direct role for the higher officials

Damage of machines due to lack of attention

To avoid all these limitations and make the working more accurately the system needs to

be computerized

2.4. Forms and reports currently usedThere are a lot of forms and reports used by police office for different purpose. These forms and

reports are put in the police office in paper based. The following forms and reports that are used

in the police currently

Forms and reportsComplaint registration formWitness summons formCrime summonses formDifferent reports formCriminal record formsRecording of decision filesWitness acceptance form

2.5. User of existing systemUsers are entities that interact with the system

In concerns on only in crime management system of debre markose city administration police

office

The crime management system we will focus only on person or actors involved on those

activities. Here are the user are involved in the existing system

Users Is part of proposed systemAdministrator YesDetective police YesCustomers Yes

Administrator

The administrator Check all the necessary information

View different reports and interacts with the detective police office.

Detective police

Detectives can take some cases from administrator or normal public.

Detective can start the some discussion forms and post some information to

others.

Detective view complaint registration forms, view crime registration forms

record crime, generate reports, record decision files and prepare summons

forms.

Customers

The customers register to the detective police office

The customers view summons forms

The customers view their file

2.1.5 Business Rule IdentificationBusiness rules are statements about the organization’s way of doing business. They

reflect business policies. Organizations have policies in order to satisfy the business

objective, satisfy customers, and make good use of resources, and conform to laws

or general business conversions. Business rule become requirements that is they

may be implemented in software as a means of requirements of this software

system

2.3 .Use case DiagramUse case is a list of steps, typically defining interactions between a role of actor and a system to

achieve a goal.

The actor can be a human or an external system.

A use case is a methodology used in system analysis to identify, clarify, and organize

system requirements.

The use case is made up of a set of possible sequences of interactions between systems

and users in a particular

Use case have the following components

Use case name

Actor

description

Pre condition

Post condition

Alternative flow of actions

The system that I have being develop has four actors those are

Criminal

compliant

Administrator

Detectives(police office)

Each actor has their Owen use case activities that have performed.

Login

View reports

Generate Summons form

Create, delete Update user account

View compliant

Record criminal

Record files

Logout

Admin

Detective Police officer

Customer(Compliant and criminal

Register

Print Summons form

View Summons form

View files

Generate report

2.3.1. Description of use case diagram

Use case name:

Login

ID UC1

Actors Admin ,compliant , criminal and detective officer

Description

Users and customers They can login by his/her account

Pre-condition They should have account

Post condition

They are authenticated and taken to their own user interface

Basic Course of Action

1.They opens the system

2.The system display login interface

3.They inputs valid user name, password

4. The system validates the account and displays the required interface

5.use case ends

Alternate

Course of Action

A If the login name or password is invalid

The system displays invalid user name or password message

The user reenters the user name and password Use CaseName:

Register Criminals and complain

ID UC2Actors Complain and criminals

DescriptionA complain and criminals can register a crime charge sheet for identifying what types of crime is held on.

Pre condition 1. User should log in to the system account.

Post condition

For achieving social service from the organization

Use CaseName:

View Report

ID UC3Actors Admin Description

An administrator shows all reports that have been done by the police department

Pre condition 1.Department should post report

Post condition

To know what activities have done by the department

Basic Course of Action

1. Post the reports by department what activates have done and how many conditions are under control.2. View reports and give criticize on the report and checks how many the report is correct.

Use CaseName:

Create ,delete update user account

ID UC1Actors Admin,compliant ,criminal Description

Admin ,public prosecutors and customers can create an account for accessing the system

Pre condition If you have an interest to join in to the system

Post condition

For accessing the system

2.4. Activity diagram

Activity diagram is another important diagram in UML to describe dynamic aspects of the

system.

Activity diagram is basically a flow chart to represent the flow form one activity to another

activity. The activity can be described as an operation of the system.

The purposes can be described as:

Draw the activity flow of a system.

Describe the sequence from one activity to another

Login

Valid

Create accountDelete account view report

Yes

No

Activity diagram for administrator

Login

Valid

view complain

Yes

No

Generate Summons form

View crime

Crime record

Age >15

Record crime

Not record

Generate Report

No

Yes

Activity diagram for detective police office

login

valid no

yes

register

view summ form

view files

logout

2.5. A sequence diagram

A sequence diagram is a kind of interaction diagram that shows how processes

operate with one another and in what order.

It is a construct of a Message Sequence Chart.

A sequence diagram shows object interactions arranged in time sequence.

Sequence diagram is used to show the sequence of actions, interaction of an

object with the Actor’s and time frames of the system.

Home Admin page Database

UML Sequence Diagram for ADMIN

ADMINmer

Check

Openview report

Open

Login

Update Account

create account

Successdelet

account

Logout

Display home Page

Display

Success

Success Update

HomePolice

Officer page Database

UML Sequence Diagram for ADMIN

Police Office

r

Check

Open

Open

Login

Created

Display home Page

Display

Stored succes

Success

View Compliant

Generate sum Form

Record crime

File record

Generate report

Success Logout

Home Customer Interface

Database

UML Sequence Diagram for customer

Customerr

Check

Open

Compliant Register

Compliant stord

Open

Login

search files Display Files

View summonsDisplay Forms

Print forms

Logout

Display Home Page

2.6. Class diagram class diagram in the Unified Modeling Language (UML) is a type of static structure

diagram that describes the structure of a system by

Showing the system's classes,

their attributes,

operations (or methods),

And the relationships among the classes.

A class diagram is an illustration of the relationships and source code dependencies

among classes in the Unified Modeling Language (UML).

Class defines the methods and variables in an object, which is a specific entity in a

program or the unit of code representing that entity.

Class diagrams are useful in all forms of object-oriented programming (OOP).

It provides an overview of the target system by describing the objects and classes inside

the system and the relationships between them.

It provides a wide variety of usages; from modeling the domain-specific data structure to

detailed design of the target system.

Class diagram for crime management system is briefly drown below

Admin

Admin flame:=stringAdmin lname:=string

Admin age =string

View report():Create account ();Update account ();

Delete account ();

police officer

pfname =stringplname =string

psex=string

view compliant();generate summons form();

crime record();file record();

Criminal

Crime name=string;Crime name=string

Crime age=int;Crimes ex=string;

view files();Watch video ();

Compliant

fname-string;lname=string

age=intsex=string;

kebele=stringword a=string;Zone=string;

Register ();View summons form ();

View file ();

1..*1..1

Class Diagram of crime mgt system

ManagedE

1..*

1..*

1..*

1..*1..*

1..*

2.7. Collaboration diagram for the new system 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.

2.2 Requirements Definition

It develops recommended process improvement actions which can include quick fixes for

serious problems, modification of existing automated system or the initiation of a business

process reengineering project.

There are two main types of Business Requirements. Functional and Non-

Functional Requirements. Functional Requirements are functions and Non-

Functional Requirements are considered constraints. The following are Functional

and Nonfunctional Requirements of the proposed new system that identified from

requirement use cases associated with each Actor and use case interaction.

2.2.1 Functional Requirements

The Functional requirement is concerned with actual performance of the system that is going to

be developed. Functional requirements describe the functionality or service provided by the new

system:

Recording of crimes to the database was the main process for the system.

Reduce redundancy, inconsistency and integrity problem of data and information

maintaining detail of crimes data usual error like record duplication will be prevented by

the proposed system

The high effort that is required in maintaining the file controlling section is made

Easy, because the system is easily maintained and not complicated

The system is capable of reducing the time that spent the existing crime management

system in practice.

The tedious process that is observed in transferring crime’s information manually be

avoided by the system

Validates data entry for correctness.

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.2.2 Non Functional Requirements A Non-Functional Requirement is usually some form of constraint or restriction that must be

considered when designing the solution

The following are the non functional requirements associated with the new system:

Non functional are expected but not stated.

The proposed system must useable anyone who have the skill to read and write.

The proposed system must recover immediately when a user enters mismatch/invalid data

type.

The proposed system must be able to communicate where ever the users to found at

different place.

The proposed system must have a better response time.

The proposed system must be compatible with any environment

The proposed system must be error free when operating with a huge set of data.

The proposed system must be secured when ever any one trays to activate without his

/her authentication role.

The proposed system must have the capacity to satisfy to the user and control criminal

activity

The proposed system must have the capacity to retrieve data from the stored database.

The proposed system must be available to all user

CHAPTER THREE

3. System design

3.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.

3.2 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.

Interoperability

From the instance of functional and non functional requirements the proposed system of debre

markos police office crime management 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 debre markose city police office 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 operate the system database

via the system Administrator who controls the whole system functions.

3.1.1 Performance Criteria

The system is compatible with wamp server platform. Because, the system is programmed with

php and my_sql.

3.1.2 Maintenance Criteria

ModifiabilityThe system is easily modifiable when the Debre Markos Police station changes the new IIS

server.

PortabilityThe system is portable from window platform to other plat forms easily b/c it uses the IIS server.

Readability The source code of the system is restricted to be understood by the programmer of the system or

a person who has a great knowledge on Microsoft web developing languages. Such us

Wamp server

CSS

HTML

3.1.3End User Criteria

Since the system is developed by using Microsoft products, it is easy to make and that have help

panel for the end user.

this project has a great help panel for end users by using

Documents

Video Tutorials

3.1.4.Security Criteria

Security For users of the system The system provides privileges to authorized users can create user name and password to

log in to the system.

And also system has another security keeping mechanism, which is called Session and

cookies which can help users to log in to the system and cannot back to the securable

pages such as user name and password.

Security for Administrators of the system

The Administrator of the system which is directly connected the database is more secured

part of the system protection.

Only a person who a privilege to the system can logon by providing username and

password and the system will check if a specified role is given to that system.

Security for Department/Police station of the system Any member of the police station has accounts that have been created by

administrator.

The members can modified their user name and password and related concepts in

their department profiles.

3.2 System Architecture

3.3 Subsystem Decomposition

To reduce the complexity of the solution domain,the system decomposed into simpler

parts, called subsystems, which are made of a number of solution domain classes.

In the case of complex subsystems, we recursively apply this principle and decompose a

sub- system into simpler subsystems.

Decomposition Results large systems in to a set of loosely dependent parts which make

up the system.

Large system is usually decomposed into sub system layer and partition. In partition the

system vertically divided into several implement of sub system that provided service on

the same level of the abstraction whereas, layers is a sub system that provided system

service to higher.

2.2. Component diagramComponent diagram show the interaction and dependencies between software components. it helps to model the physical aspects of an object oriented software system. Those software components including run-time components, execute components and source code of components

Chapter 4

4.1. Conclusion and Recommendation

4.1.1. Conclusion

The project is aimed to develop a computer based crime management system.

In the first chapter, that described the background of the police office with the explanation

of how the police stations is established in terms of the objectives of the police

department ,the problems of the existing system that the police office faced during

accomplished its tasks, the objective of the project, the scope and limitation of the project,

beneficiaries of the project ,feasibility and work breakdown structure have been discussed

including the methodology of the project which describes what and which material used

to accomplished those project .

In second chapter, that performed a detailed business area analysis that describes what the

current system looks. In business area analysis the identified the problems of the current

system, the forms and reports of the existing system. Then we used an essential use case to

model the features of the existing system by identifying actors and use cases. After business

area analysis we determined the requirements of the proposed system in terms of

functional and non functional requirements. Finally, done a user interface prototyping that

describes the user interface requirements in a technology independent manner.

The third chapter of the project discussed about object oriented design which tries to

produce the conceptual model of information for the problem domain that raised on

chapter one of the existing system. To accomplished this task, used object oriented

analysis and design tool ( EDRAW) and different types of techniques like system use case,

different diagram such as sequence diagram , class diagram and activity diagram including

user interface prototyping that is an extension of the essential user interface .

The project is described clearly theoretically how it was done with every steps of the

system in the manner of the other people can understand. Our project is easy to maintain

the system or to modify a particular use case if necessary or one can add additional

functionality on a particular use case.

4.1.2. RecommendationThese system is a computer crime management system in case of debre markose police

office so every users of our system should have knowledge how to use computer

application.

In order to use the system debre markose city police office should be .

The police office should have adequate computer facilities to use the new system

effectively.

Budget should be allocated to take specific measure, such as:

o To change the manual system into the new computerized

system.

o To maintain the system in a timely and speedy manner.

4.2. Future Enhancement

will develop by which the user can report online easily.

will develop SMS alert for Iphone and Smart phone by which user can report from the

mobile. Communication between user and police office

4.3. Reference 1. Howard, Michael. “Microsoft Internet Information Server Security”

URLs.

http://www .highcourtofkerala.com/

http://www.casecitation.com/

www.developer.com