Chapter two

1. Requirements specification
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 NonFunctional Requirements. Functional Requirements are functions and NonFunctional 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 new crime and civil case to the database was the main process for the
system.
Reduce redundancy, inconsistency and integrity problem of data and information
maintaining detail of crimes and civil 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 legal system in
practice.

The tedious process that is observed in transferring crimes 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

Essential use case diagram

Essential use cases are of primary importance early in a projects 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.

These use case modeling is a simplified abstract, generalized use case that captures the
intentions of the user in a technology and implementation independent manner. It identifiers use
case and actors of the existing system.

Use case discrption

Name:

Register Criminal and civil case

ID
Actors
Description

UC1
Information desk, Customer

Precondition

The customer who have case can register into the file
The customer provide the necessary data to information desk

Post
condition
Basic Course
of Action

The customer is registered

Alternate
Course of
Action

If the information is invalid or incomplete

1
2
3
4
5

The customer request for registration.

The Information desk gives the customer registration form
The customer fills the prepared form.
The Information desk registers the customer into the file.
End of use case

The Information desk asks the customer to fill the appropriate information.
The Resident fills the appropriate information on the form.
The use case continues from step 4

Table 2.3 Register Criminal Case

Name:

Register Civil case

ID
Actors
Description

UC2
Information desk, Customer

Precondition
Post
condition
Basic Course
of Action

The customer who have case can register into the file
The customer provide the necessary data to information desk
The customer is registered
1
2
3
4
5

The customer request for registration.

The Information desk gives the customer registration form
The customer fills the prepared form.
The Information desk registers the customer into the file.
End of use case

Alternate
Course of
Action

If the information is invalid or incomplete

The Information desk asks the customer to fill the appropriate information.
The Resident fills the appropriate information on the form.
The use case continues from step 4

Table 2.4 Register Civil Case

Name:

Generate Report

ID
Actors
Description

UC3
Record officer
The Record Officer generates different types of reports for the top manager.

Pre condition

A particular period of time to generate the report

Post
condition
Basic Course
of Action

Generated report
1.the record office collects information about the services given within some
period of time(daily, monthly, yearly)
2. the record officer generates the 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

Business Rule Identification

Business rules are statements about the organizations 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

Analysis

2.1 business area analysis

Business area analysis evaluates how well business process, business rules, business data,

organizational structure, and people skills match the mission of the organization unit. 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.
2.1.1 Study of the activity

Record new civil cases

Record new criminal cases
Give appointment for different cases
Evaluate the cases and give decision
2.1.2 Problem of the current system

The system works manually and the data handling and processing system creates problem on
summarization, updating and integration of data for decision making. The problems of the
existing manual based system are described using the PIECES from work. Where

P is performance
I is information
E is economics
C is control,
E is efficiency and
S is service

Performance

Throughput
The current working system has a low level of throughput because it can only handle
limited number of customer at a time.
Response time
The response time to a given task in the current working system is significantly low due to
The time taken to get the accurate information of customers and prepare different
reports

Information (and Data)

Outputs
It is difficult to produce needed information from the manual documentation
Inputs
Data is not accurately captured, contain errors
Data is captured redundantly, example appointment date
Stored data
Since the file handling system is manual there is no any security
Data is not organized

Economics
Costs
The current system takes more costs to perform its tasks
Profit
The current system does not design at producing profit when it compares with the
cost it expense.
Control and security
Data is not adequately edited
Data privacy regulations or guidelines can be violated

Efficiency
Information is redundantly generated
o There is no way of knowing if customers repeatedly come for
insured purpose

Service

The system is inflexible to change

2.1.4 Users of the existing system

Users
Is part of the computerized system?
Manager
NO
Criminal case Judges
NO
Civil case Judges
NO
Record office
Yes
Information desk
NO
Customer
NO
File opener
NO

Table 2.2 Users of the existing system

Manager
The Manager gets reports from the case workers manually. The reports help the manager to see
how services are given to the customer and manage the organization.

Criminal Case Judges

They interact with customers and record office. They judge the case concerned with criminal
cases and give decision.
Civil Case Judges
They interact with customers and record office. They judge the case concerned with civil cases
and give decision.
Record office
The record officer records different files and case either decision or not
Information Desk
This record officer only interacts with customers by any types of case. Particularly new case
arrived from the customer. Here the record officer asks the customer every information needed,
gather the information and fill manually on a paper then finally send the file to record office.
Customer
The customer does not interact with the computerized system rather he/she requests a service
from the information desk. The customer then gives necessary information based the case. The
customer gets his/her requested service from the information desk.
File opener
File opener does not interact with the computerized system rather he/she requests a service from
the information desk. The file opener then gives necessary to the judge based the case.
2.1.5 Business Rule Identification

Name:-loan money Statement of claim

Id: - BR1
Description:

The claim person must have real evidence to loan money to him/her
The claim person must came the file that contains the agreement of between them about
the loan of money

Name:-Claim for divorce request

Id: - BR2
Description:

Husband and wife came their profile that describes the marry of contract
Duration of time they live together

Amount of capital they have

Name:-Successor certificate claim request

Id: - BR3
Description:

Successor have evidence that checks the child of died person

Him/her show when and where the father and mother die
They should come person that knows the child of the died person
Successor/s should signed

Name:-Maintenance claim request

Id: - BR4
Description:

Maintenance requester have evidence the relationship between maintenance requestor

and maintenance give person
The maintenance request age should be under 18
Maintenance request should signed

Name:- Divorce by agreement and effects of divorce approved claim request

Id: - BR5
Description:

Husband and wife came their profile that describes the marry of contract
Duration of time they live together
Amount of capital they have
Attach their divorce by agreement document
Both of them should be signed

Name:-Appeal request from

Id: - BR6
Description:

Him/her case is should have been closed

Ask the appeal by their signature

2.1.6 Use case diagram

Use 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

Name:

Register Criminal and civil case

ID
Actors
Description
Precondition

UC1
Information desk, Customer
The customer who have case can register into the file
The customer provide the necessary data to information desk

Post
condition
Basic Course
of Action

The customer is registered

Alternate
Course of
Action

If the information is invalid or incomplete

6
7
8
9
10

The customer request for registration.

The Information desk gives the customer registration form
The customer fills the prepared form.
The Information desk registers the customer into the file.
End of use case

The Information desk asks the customer to fill the appropriate information.
The Resident fills the appropriate information on the form.
The use case continues from step 4

Table 2.3 Register Criminal Case

Name:

Register Civil case

ID
Actors
Description

UC2
Information desk, Customer

Precondition

The customer who have case can register into the file
The customer provide the necessary data to information desk

Post
condition
Basic Course
of Action

The customer is registered

Alternate
Course of
Action

If the information is invalid or incomplete

6
7
8
9
10

The customer request for registration.

The Information desk gives the customer registration form
The customer fills the prepared form.
The Information desk registers the customer into the file.
End of use case

The Information desk asks the customer to fill the appropriate information.
The Resident fills the appropriate information on the form.
The use case continues from step 4

Table 2.4 Register Civil Case

Name:

Generate Report

ID
Actors
Description

UC3
Record officer
The Record Officer generates different types of reports for the top manager.

Pre condition

A particular period of time to generate the report

Post
condition
Basic Course
of Action

Generated report
1.the record office collects information about the services given within some
period of time(daily, monthly, yearly)
2. the record officer generates the report

Table 2.5 report description

Name:

Login or logout

ID

UC4

Actors

Record officer, Admin, file opener, Civil and crime judges,

information desk

Description
Users They can login by his/her account
Pre-condition

They should have account or case no (for customer)

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 and case no(for
customer)
4. The system validates the account and displays the required
interface
5.use case ends
6 logout

Alternate

A If the login name or password is invalid

Course of Action

The system displays invalid user name or password message

The user reenters the user name and password
The use case continues from step 3
Table 2.6 login and logout description

Name:

Create account

ID
Actors
Description

UC5
administrator

Precondition
Post
condition
Basic
Course of
Action

Administrator can create an account for accessing recourses from the system
If admin have an interest to join in to the system
For accessing admin from the system
1

The admin can create an account if he/she cant have an

account.

The employer should enter validate values to the field.

3.Login in to the system if he/she has an account that has

Alternate
Course of
Action

registered
You can change the password and user name for better security.

Table 2.7 admin create account

Name

Give decision

ID

UC6

Actors

judges

Description

They judges the case concerned with criminal cases and civil case give
decision.

Precondition

The Criminal & civil judges gather information from information desk and
necessary evidence that checks.

Post condition

The judges give decision.

Basic Course of 1.The real evidence from three persons

Action

2. prepare all the necessary documents

2. To provide agreement document
3. End of use case.
Table 2.8 decision use case description

Name:

View decision

ID
Actors
Description
Precondition
Post
condition
Basic
Course of
Action

UC7
customers
Customers views all reports that posted by the judges
post the decision by the judge

To interact between their responsibilities and functionalities.

Decision about crime should posted by judges
Customer looks new decision

posted by

judge then came and contact with judge

Table 2.9 customer view decision

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 Actors and time frames of the system.

Fig 2.Squance diagram for give appointment

Fig 3.Squance diagram for give judgment

Fig 4.Squance diagram for record file

Fig 5.Squance diagram for record cases

Fig 6.Squance diagram for open new files

Fig 7.Squance diagram for generate report

Fig 8.Squance diagram for view appointment

Fig 2.Squance diagram for record new case

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

Activity diagram for judge

Activity diagram
Admin

for

Activity Diagram for customer

Activity Diagram
for record officer

Activity diagram for Information Disk

Activity Diagram for file opener