2. Chapter two 2.1. Requirements specificationIt 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.1 .1 Functional RequirementsThe 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 2.1.1.1Essential use case diagramEssential 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 descriptionName: Create account

IDUC1

Actorsadministrator

Description

Administrator can create an account for accessing recourses from the system

Pre-conditionIf admin have an interest to join in to the system

Post conditionFor accessing admin from the system

Basic Course of Action1. The admin can create an account if he/she cant have an account.1. The employer should enter validate values to the field.3.Login in to the system if he/she has an account that has registered

AlternateCourse of Action

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

Name:Register Criminal and civil case

IDUC2

ActorsCustomer

Description

The customer who have case can register into the file

PreconditionThe customer provide the necessary data to information desk

Post conditionThe customer is registered

Basic Course of Action1. The customer request for registration.2. The Information desk registration the customer The Information desk registers the customer into the file.3.End of use case

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

Name:Generate Report

IDUC3

ActorsRecord officer

Description

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

Pre conditionA particular period of time to generate the report

Post conditionGenerated report

Basic Course of Action1.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

NameGive decision

IDUC4

Actors judges

Description

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

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

Post conditionThe judges give decision.

Basic Course of Action1.The real evidence from three persons(witness)2. prepare all the necessary documents 2. To provide agreement document 3. End of use case.

Name:View decision

IDUC5

Actorscustomers

Description

Customers views all reports that posted by the judges

Pre-conditionpost the decision by the judge

Post conditionTo interact between their responsibilities and functionalities.

Basic Course of ActionDecision about crime should posted by judgesCustomer looks new decision posted by judge then came and contact with judge

Name:View appointment

IDUC6

Actorscustomers

Description

Customers views all appointments that is posted by the judges

Pre-conditionpost the appointment by the judge

Post conditionTo interact between their responsibilities and functionalities.

Basic Course of ActionAppointment should posted by judgesCustomer looks appointment by entering file number posted by judge.

Name:Open file

IDUC 7

ActorsFile opener

Description

The customer who have case can register into the file then information desk give for file opener then file openers start opening file by giving file number

PreconditionThe customer provide the necessary data to information desk

Post conditionFile opened

Basic Course of Action1. The information desk request for file openers.2. The Information desk gives the case to the file opener3. End of use case

AlternateCourse of Action

If the information is invalid or incomplete

The Information desk asks the customer to fill the appropriate information.

2.1.2 Non Functional Requirements A Non-Functional Requirement is usually some form of constraint or restriction that must be considered when designing the solutionThe 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 user2.1.2.1Business Rule IdentificationBusiness 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 system2.1.2.2 Business area analysisBusiness 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.2.2.1 Study of the activity Open new files Record new civil cases Record new criminal cases Give appointment for different cases Evaluate the cases and give decision 2.1.2.2 Problem of the current system or change caseThe 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 servicePerformance Throughput The current working system has a low level of throughput because it can only handle limited number of customer at a time. Response timeThe 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 reportsInformation (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 CostsThe current system takes more costs to perform its tasks ProfitThe 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 violatedEfficiency Information is redundantly generated There is no way of knowing if customers repeatedly come for insured purposeService The system is inflexible to change .1 Users of the existing systemUsersIs part of the computerized system?

ManagerNO

Criminal case JudgesNO

Civil case JudgesNO

Record officeYes

Information deskNO

CustomerNO

File openerNO

Table 2.2 Users of the existing systemManagerThe 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 JudgesThey interact with customers and record office. They judge the case concerned with criminal and and give decision.Civil Case JudgesThey interact with customers and record office. They judge the case concerned with civil cases and give decision.Record officeThe record officer records different files and case either decision or not Information DeskThey record case. Particularly new case arrived from the customer. CustomerThe 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 openerFile 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 .2 Analysis 2.1.6 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

Use CaseName:Login

IDUC 1

ActorsAdmin, file opener, information desk, record officer, judge

Description

Customer should register, view summons form view appointment, view judgment without login and the admin can create another Admin account after login in to the system.

Pre-condition1.the account should registered in to the data base of the system

Post conditionFor administering all functionalities of the system .

Basic Course of Action1.login in to the system2.work all activities regarding to system3.logout

AlternateCourse of Action

1.change password and username

Name: Create account

IDUC2

Actorsadministrator

Description

Administrator can create an account for accessing recourses from the system

Pre-conditionIf admin have an interest to join in to the system

Post conditionFor accessing admin from the system

Basic Course of Action1. The admin can create an account if he/she cant have an account.1. The employer should enter validate values to the field.3.Login in to the system if he/she has an account that has registered

AlternateCourse of Action

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

Name:Register Criminal and civil case

IDUC3

ActorsCustomer

Description

The customer who have case can register into the file

PreconditionThe customer provide the necessary data to information desk

Post conditionThe customer is registered

Basic Course of Action1. The customer request for registration.2. The Information desk registration the customer The Information desk registers the customer into the file.3.End of use case

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

Name:Generate Report

IDUC4

ActorsRecord officer

Description

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

Pre conditionA particular period of time to generate the report

Post conditionGenerated report

Basic Course of Action1.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

NameGive decision

IDUC5

Actors judges

Description

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

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

Post conditionThe judges give decision.

Basic Course of Action1.The real evidence from three persons(witness)2. prepare all the necessary documents 2. To provide agreement document 3. End of use case.

Name:View decision

IDUC6

Actorscustomers

Description

Customers views all reports that posted by the judges

Pre-conditionpost the decision by the judge

Post conditionTo interact between their responsibilities and functionalities.

Basic Course of ActionDecision about crime should posted by judgesCustomer looks new decision posted by judge then came and contact with judge

Name:View appointment

IDUC7

Actorscustomers

Description

Customers views all appointments that is posted by the judges

Pre-conditionpost the appointment by the judge

Post conditionTo interact between their responsibilities and functionalities.

Basic Course of ActionAppointment should posted by judgesCustomer looks appointment by entering file number posted by judge.

Name:Open file

IDUC 8

ActorsFile opener

Description

The customer who have case can register into the file then information desk give for file opener then file openers start opening file by giving file number

PreconditionThe customer provide the necessary data to information desk

Post conditionFile opened

Basic Course of Action4. The information desk request for file openers.5. The Information desk gives the case to the file opener6. End of use case

AlternateCourse of Action

If the information is invalid or incomplete

The Information desk asks the customer to fill the appropriate information.

Use CaseName:Logout

IDUC9

ActorsAdmin, file opener, information desk, record officer, judge

Description

Admin, file opener, information desk, record officer, and judge should logout after stop his/her work.

Pre-conditionAdmin, file opener, information desk, record officer, judge finishes his/her task

Post conditionFor closing the account and live the system out of his/her password for security purpose.

Basic Course of Action1.login in to the system2.work activities on their interest3.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 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 diagramActivity 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 for Admin

Activity Diagram for customerActivity Diagram for record officerActivity diagram for Information DiskActivity Diagram for file opener