lOMoARcPSD|36041483

Project CS - This

Research (Arba Minch University)

Scan to open on Studocu

Studocu is not sponsored or endorsed by any college or university

Downloaded by Steve Zenebe (steveiamid@gmail.com)
 lOMoARcPSD|36041483

ARBA MINCH UNIVERSITY

PROJECT TITLE: Web based court information management system

Group members

Name Id number

1. Mulugeta Gebino ---------------------------------------------EAMIT/2142/10

2. Tsega Bezabih -------------------------------------------------EAMIT/2169/10
3. Yehualashet Wolde--------------------------------------------EAMIT/2177/10
4. Meseret Mekayhu --------------------------------------------EAMIT/2138/10
5. Trufat Asfaw --------------------------------------------------EAMIT/2167/10
6. Tademe Zewdihun -------------------------------------------EAMIT/2153/10

SUBMITTED TO: - Computer Science Department

Jun 2022

Arba Minch, Ethiopia

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Contents
Chapter One................................................................................................................................................................7
1. Introduc琀椀on.............................................................................................................................................................7
1.1 Background of the organiza琀椀on.........................................................................................................................7
1.2. Background of the project................................................................................................................................8
1.3 Statement of the problem.................................................................................................................................9
1.4. Objec琀椀ve.........................................................................................................................................................10
1.4.1. General objec琀椀ve.....................................................................................................................................10
1. 4.2. Speci昀椀c Objec琀椀ve....................................................................................................................................10
1.5. Methodology..................................................................................................................................................10
1.5.1 Data collec琀椀on..........................................................................................................................................10
1.5.2 System analysis and design.......................................................................................................................11
1.5.3 System Development Tools......................................................................................................................12
1.6 Scope and Limita琀椀on of the Project.................................................................................................................13
1.6.1 Scope........................................................................................................................................................13
1.6.2 Limita琀椀on of the project...........................................................................................................................13
1.7 Signi昀椀cance of the project...............................................................................................................................13
1.7.1 Bene昀椀ts for court......................................................................................................................................13
1.7.2 Bene昀椀ts for society...................................................................................................................................14
1. 8. Feasibility.......................................................................................................................................................14
1.8.1 Economic feasibility..................................................................................................................................14
1.8.2 Technical feasibility...................................................................................................................................16
1.8.3 Time feasibility..........................................................................................................................................16
1.8.4 Opera琀椀onal feasibility...............................................................................................................................16
1.9 Task breakdown and deliverables....................................................................................................................16
1.10 Communica琀椀on plan......................................................................................................................................17
1.1 Time Schedule...........................................................................................................................................17
Chapter Two..............................................................................................................................................................18
Descrip琀椀on of the exis琀椀ng system.............................................................................................................................18
2.1 Introduc琀椀on.....................................................................................................................................................18

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

2.2 Exis琀椀ng System................................................................................................................................................18

2.2.1 Exis琀椀ng System Descrip琀椀on......................................................................................................................18
2.2.2 Why describe the exis琀椀ng system.............................................................................................................19
2.2.3. Problems of the exis琀椀ng system..............................................................................................................19
2.2.4 Alterna琀椀ve op琀椀ons to address the problems of exis琀椀ng system..............................................................20
2.3. Supplementary Requirements........................................................................................................................20
2.3.1. Business Rule...........................................................................................................................................20
2.4 The New Proposed System..............................................................................................................................21
2.4.1 So昀琀ware Requirement Speci昀椀ca琀椀ons (SRS................................................................................................22
Chapter Three............................................................................................................................................................24
Analysis deliverables of new system..........................................................................................................................24
3.1 Introduc琀椀on.........................................................................................................................................................24
3.2 use case diagram.............................................................................................................................................24
3.3 System Use case diagram................................................................................................................................24
3.3.1 Use Case Documenta琀椀on..........................................................................................................................26
3.4 Analysis level of class diagram.........................................................................................................................34
3.5 Sequence diagram...........................................................................................................................................37
3.6 Ac琀椀vity diagram...............................................................................................................................................39
3.8 Essen琀椀al User Interface Prototyping................................................................................................................48
3.8.1 User Interface Prototyping as Flow Chart Diagram...................................................................................48
3.9 Change cases...................................................................................................................................................48

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

List of Table
Table 1.1 software costs............................................................................................................................................15
Table 1. 2 Hardware cost...........................................................................................................................................15
Table 1.3 tangible benefits.........................................................................................................................................15
Table 1.4 net cost benefit...........................................................................................................................................16
Table 1.5 Task Breakdowns......................................................................................................................................17
Table 1.6 Time Schedule...........................................................................................................................................17

Table 3. 1 Use Case Documentation for Login 26

Table 3. 2 Use case documentation for generate report 26
Table 3. 3 Use case documentation for Create account 27
Table 3. 4 Use Case Documentation for Update account 28
Table 3. 5 Use Case Documentation for View Appointment 28
Table 3. 6 Use case documentation for view information 29
Table 3. 7 Use case documentation for search customer information 30
Table 3. 8 Use case documentation for Give appointment 30
Table 3. 9 Use case documentation for new case registration 31
Table 3. 10 Use case documentation for advocator registration 31
Table 3. 11 Use case documentation for view assigned case 32
Table 3. 12 Use case documentation for record decision 33
Table 3. 13 Use case documentation for View Decision 33
Table 3. 14 Use Case Documentation for Give Comment 34
Table 3. 15 Analysis level of class diagram 37

List of Figure
Figure 3. 1 System use case.......................................................................................................................................25
Figure 3. 2 Sequence diagram for login.....................................................................................................................37
Figure 3. 3 Sequence diagram for new case registration............................................................................................38
Figure 3. 4 Sequence diagram for View Information.................................................................................................39
Figure 3. 5 Activity diagram for login.......................................................................................................................40
Figure 3. 6 Activity Diagram for Advocator Registration..........................................................................................41
Figure 3. 7 Activity Diagram for View Appointment................................................................................................42
Figure 3. 8 Activity Diagram for View Information..................................................................................................43
Figure 3. 9 Activity Diagram for Search Customer Information................................................................................44
Figure 3. 10 Activity Diagram for Create Account....................................................................................................45
Figure 3. 11 Activity Diagram for Give Comment....................................................................................................46
Figure 3. 12 Conceptual modeling using class diagram.............................................................................................47
Figure 3. 13 UI Flow Chart Diagram.........................................................................................................................48

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Declara琀椀on
This is to certify that the project is original and has not submitted for partial fulfillment of
Bachelor of Science in Information system (Name and Signature of the project group members)

Name signature Date

1. Mulugeta Gebino _____________ _____________
2. Tsega Bezabih _____________ _____________
3. Yehualashet Wolde _____________ _____________
4. Meseret Mekayhu _____________ _____________
5. Trufat Asfaw _____________ _____________
6. Tademe Zewhidune _____________ _____________
This is to certify that I have read this project and that in my opinion it is fully adequate, in e
and quality, as a project for the degree of Bachelor of Science.

Advisor Name: Signature Date

Endale ………………… …....................

Examiner’s Name Signature Date

1. Department Head …………….. ….…………

2. Examiner 2 ………..……. ………………

ARBA MINCH UNIVERSTY FACULTY OF COMPUTING AND SOFTWARE

ENGINEERING DEPARTMENT OF COMPUTER SCIENCE

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Abstract
The purpose of this project is to full fill the requirement of bachelor degree of Computer Science as final
year project in order to graduate.
Now days, using computers to simplify tedious manual work is significance. Because using computer
gives many benefits like speed, accuracy, storage capacity, security, flexibility, cost reduction and
minimizing tedious manual work. Arba minch court office was limited on manual works. This has a
limitation for customers wasting large amount of time in front of the office to register and high
consumption of resources.
To overcome this problem we are proposing the new web base system for Arba minch Court
Information management System. Customer can find advocators by using online system. So that no needs
waste the time and resource to find advocators
This system is developed based on two-tier approach with step by step from planning, analysis,
design, and then implementation. With the Unified Modeling Language (UML) diagram such as use case,
activity diagram and sequence diagram is drawn. The system flow and the actor are drawn to understand
how the system works does and who the actors that interact the system are.
The programming language used to develop this project is PHP and HTML .Database
application is MySQL.

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Apendex

ACIMS…………………………………………. arba minch court information management system

CRC…………………………………………….class responsibility collaboration
ACIMSCA …………………………………… arba minch court information management system create
account
ACIMSCL…………………………………… arba minch court information management system login
UC…………………………………………… Use Case

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Chapter One

1. Introduction
Different organizations are established in order to give services to the community. Among those our
project is “Court information management system”.

1.1 Background of the organization

The court office was established during the “Haile silase ” regime. Before this time disagreement and
criminal cases were solved in traditional way. Starting from that time it passes many obstacles to reach
today’s position. The he organization is located around the Gamo zone Arba minch town sikela sub town
in menariya kebele 02. court office of in Arba minch town established in 1996 E.C started to serve the
customer in modern ways. The purpose of the court is to provide legal decision for those plaintiffs and
defendants based on their evidences as well as for those who commit crimes. The lawyers make decision
based on the constitution of the country. The court information management system addresses two major
cases those are civil case and criminal cases. It has the responsibility to support, manage, giving response
to the case, taking case from the kebele (mahiberawifirdeshengo) to woreda level court office. The woreda
has this partially automation system after 2017 E.C. We have seen some problems in data processing and
handling. During the process there are many difficulties of manual processing of files/data. Not only this
but also giving comments for one court is difficult because of distance. Now we are going to develop
software that can solve problems of data processing, data handling and etc.

1.2. Background of the project

The system based on the court information management system that improves the manual data processing.
Court Information Management System is document management system or handling of data, dataflow
system, court fee, appointment and also concern with a customers’ comment. There are two major types of
cases. Those are civil law and criminal law. Each of them contains their own sub branches. In order to
execute those cases some process takes place.
As we visited the work place of; how the court information management system takes place; we have seen
some problems in data processing Arba minch town and handling. During the process there may be many
difficulties of manual processing of files/data. Not only this but also giving comment for one court may be
difficult because of distance. This means there is no online giving comment service before for the court
found on the distance.

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Now we are going to develop software that can solve problems of data processing, data handling, give
appointment ,assign case ,registering case and view assigned case etc. we can achieve our aim by using
hardware (pc) and software (programming language). The main purpose of doing this project is that to
save person’s file from damage, store files forever, secure files that must be secured, reduce costs and
time. There will be data communication from one office to the other. There will be many advantages after
the end of our project. The following things will be the result after the implementation of the new
proposed system we are going to develop.
• protect the data from damaging

• prevent the data from the thieves, robbers

• Save the data in secure way if needed

• Giving appointment for customer in simple way

• Court fee can be registered and saved into database in civil case.

• Dead files can be seen by a person who wants to see it but active file is secure

• Giving comment online for court Administrator is possible

1.3 Statement of the problem

Court information management system of Arba minch town does on both criminal and civil case type. As
mentioned above these major types contain so many sub branches. Criminal case is initiated when crime is
committed, then investigation held to collect information and evidence about what is happened to
determine who committed the crime. After that the accused is charged with the crime and taken into
custody.
Based on evidence, then the judge determine whether he/she guilty or not guilty. At the end the decision is
presented. This process is done manually. Also Civil court cases arise where an individual or a business
believe their rights have been attacked in some way. All these processes and documentation system is
takes place manually. By this system the following problems are identified.
• Difficulty of storing the documents neatly

• Files may be stolen by thieves, robbers or internal attackers.

• Files may be fade because of long life

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

• Files may be destroyed by natural disasters like fire , flood

• Giving comment may be difficult for customers on distance place

• Difficulty of data store in secure way.

• Difficulty of retrieving needed document timely..

• Recording examination, cross examination and reexamination may difficult while collecting
evidence from witness.

• Difficult to giving appointments for customers.

• Difficult to evaluate every judge decisions.

• Difficult to assign cases to judges.

• They pay cost for paper, copy, print, scan and etc…

1.4. Objective
1.4.1. General objective
Our main objective is to develop web based court information management system for Arba minch town
court office.

1. 4.2. Specific Objective

To achieve the general objectives of the project, the proposed system consists of the following specific
objectives:-
• Analyze the existing system and design better system for the organization

• To store all data’s of the accuser and accused person into the database.

• To design and developed a user friendly system to handle data insertion, updating, deletion,
retrieving on the database.

• To develop a secured Data base system

• To develop suitable system to give appointment and assign cases.

• To develop the court information management system

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

1.5. Methodology
In order to achieve our aim, we use different methods to bring the system from imagination to realization.
These methods include different models, techniques and tools for our work.

1.5.1 Data collection

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.
A) Interview Techniques: is one of the primary ways analysts gather information on information
systems. During interviewing the team will gather facts, opinions, and speculation and observe body
language, emotions, and other signs of what people want and how they assess current systems. Interviews
are good tools for collecting rich and detailed information.
B) Observation: Observing current system users is a more direct way of seeing how an existing system
works. By watching what people do or by obtaining relatively objective measures of how people behave in
work situation, the team can have firsthand and accurate appreciation of what they really do or how they
do it observing work flow at the work place. Though this technique is cost effective we hoped to achieve
the target.

1.5.2 System analysis and design

The team plan to use the Object Oriented Software Development Methodology (OOSD) for the
development of the system among the different methodologies. Because it is better way to construct,
manage and assemble objects that are implemented in our system. We used OOSD because of the
following important features:
• Increase reusability: - the object oriented provides opportunities for reuse through the concepts of
inheritance, polymorphism, encapsulation and modularity.
• Increased extensibility: -when you to need to add new feature to the system you only need to
make changes in one part of the applicable class.
• Improved quality: - quality of our system must be on time, on budget and meet our exceeded the
expectation of the users of our system, improved quality comes from increased participation of
users in the system development.
• Financial benefits: - reusability, extensibility and improved quality are all the financial benefits,
because they led to the business benefits of the object- oriented from the point of view of the users,
the real benefits are we can built, system faster and cheaper.

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

• Reduced maintenance cost: - Software organizations currently spend significant resources

maintain operating system so the object oriented development methods helps us to overcome this
problem.
• Managed complexity:-The object-oriented methods solve software complexity in the following
way, design your software the expectation that it will need to be modified and being able to
respond quickly when your environment changed.
Object oriented design methodology has two phases:-
Object Oriented Analysis (OOA): During this phase the team will look at the problem domain and with
the aim of producing a conceptual model of the information that exists in the area which will be analyzed.
And this model the functions of the system (use case modeling), identifying the business objects, organize
the objects and also the relationship between them and finally model the behavior of the objects.
Object Oriented Design (OOD): During this phase the model interactions and behaviors that support the
use case scenario, and finally update object model to reflect the implementation environment. And also
transforms the conceptual model produced in object-oriented analysis to take account of the constraints
imposed to our system format, so that we will use this phase to refine the use case model to reflect the
implementation environment.
State chart diagram, component diagram and deployment diagram to model our system.

1.5.3 System Development Tools

We used the software and hardware tools for developing our project.
Hardware tools
• Computer with internet connection

• Secondary storage device

• flash disk(16 GB)

• Memory :8GB RAM

• Hard disk:1TB

Software tools

The different kind of software we used for developing the project is:-

• mysql server – to develop database application

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

• Microsoft office word 2010 for documentation.

• Microsoft Visio – to design Gantt chart

• Edraw Max—to design Use case Diagram, design Sequence Diagram, design Activity
Diagramand. Class Diagram, Deploy Diagram and other diagram

• Programming Language: - PHP and HTML, js, css

1.6 Scope and Limitation of the Project

1.6.1 Scope
Scope of the system identifies the problem to be studied, analyzed, designed, constructed and ultimately
improved. It is specifically concerned with what problem the proposed system addresses. The project can
cover the following activities:-
• Register open new case, customers and Advocator that wants to give service for
customer,

• Assigned cases to judges, appointment dates.

• View assigned cases that law officers are assign to Judges

• Generate reports.

• Search the files in short times.

• Update employee’s information.

• Record examination, cross examination and reexamination in the database while

collecting evidence from witness.

• Register finished cases decisions and the evidence Register finished cases decisions
and the evidence of the witness.

1.6.2 Limitation of the project

 Time,
 cost,
 Experience,
 resource

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

1.7 Significance of the project

After the implementation of this project, it provides various benefits for courts and for societies.

1.7.1 Benefits for court

• Save time.

• It reduces the work load for workers.

• Decrease Error in filing the client document.

• Employers will have confidence on handling data.

• Searching documents when it is needed is easy.

• They can secure active files and dead file as they want.

• Information about court can be accessed any time from any place based on given privilege.

• Data communication is possible

• To know the appointment date is very easy.

• Calculating court fee depending on cases become simple

1.7.2 Benefits for society

• Customer can access the information they need from the web.

• Save their time

• Reduce the complexity.

• Can save their financial budget.

• Customers will give their comment online without going there.

1. 8. Feasibility
Feasibility study is the process of determina琀椀on of whether or not a project is worth doing. There are
many types of feasibility study
1.8.1. Economic Feasibility
1.8.2. Technical Feasibility
1.8.3. Time Feasibility

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

1.8.4. Operational feasibility

1.8.1 Economic feasibility:-

The project that we are going to develop is economically feasible than the manual system. Manual system
use large amount of document for Registration and record decision this implies economically infeasible,
our System changes this into computerized manner so no wastage of resource. The system developed by
considering budget of an organization which is economically feasible. This refers to the benefits or
outcomes we are deriving from the product as compared to the total cost we are spending for developing
the product.

A. Software cost

Item Price
Microsoft window 10 50
MSVisio2010 60
Microsoft word 2010 30
SQL Server 2005 45
Macromedia Dreamweaver 50
Visual basic studio 65
Total 300
Table 1.1 software costs
B. Hardware costs
Item Quantity Unit price Total
PC 1 24,000 24,000
Flash disk 1 350 350
Other material --- ---- 1200
Total 25,550
Table 1. 2 Hardware cost
• So the first year total cost can be calculated like this:-

Total cost=hardware cost +software cost =25,550 + 300=25,850

Tangible benefits
Benefits Price
failure reduction 4,500
Cost reduction 20,000
Service Value 12,500
Total benefit 37,000
Table 1.3 tangible benefits

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Net cost benefit

• The new system net benefit on the first year is as shown in table 1.4.

Total benefits Total cost Net benefit

37,000 25,850 11,150
Table 1.4 net cost benefit

So if we got this amount of net benefit on the first year we are economically feasible.
Intangible benefits
• Reduce workload of the organization
• Increase customer and user satisfaction
• Modernize organization work
• Error reduction
• Give better and effective service
• Increase security
• Increase efficiency

1.8.2 Technical feasibility

The court management system will deliver service by using digital system of file handling and
transferring files digitally, which will simplify task. It has a graphical user interface to assist employers
and customers of the organization. The system can be easily maintained, portable, available and reliable. It
is also support multi user, data handling system and easy to install. Generally the system is technical
feasible.

1.8.3 Time feasibility

Time feasibility refers to the time that particular work takes to implement or performed. A System that
going to be developed should save times than the exist system. I.e. The software we are going to develop
could perform action within short time when compare with current system. Searching, saving, viewing
details, should be shorter than before action.

1.8.4 Operational feasibility

The organization brought changes by building central database and web based system on the top of the
existing system. To adopt with the system introduction to computer is required. The existing staff has no
problem to adopt this system, since they use computers by themselves. In case if there are people who
need an assistant of the system, website has its own help page. Generally the system is operationally
feasible to operate it.

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

1.9 Task breakdown and deliverables

Our project has four main stages. This are:-

1. Proposal- in this stage the project contains the facts that shows how the existing system works and
other information’s such as the background of the organization and the problem of existing system. This
stage also shows the needs that the new system wants to solve the problem. The proposal stage is the main
stage that contains the plane to complete the project effectively.
2. Analysis-in the analysis stage requirements will be determined. This means the new system should do
from as many sources as possible (user of the existing system, forms and procedures). In the analysis stage
requirements that we determined will be represented diagrammatically in order to make them easier to
translate into technical system specification.

3. Design-in this stage that we will make the layout that shows how the new system will do at its
implementation stage. These are user interface, sequence diagram, etc.
4. implementation-it is the last stage that we will run and test the new system according to the layout
in the design phase and requirements specified in the analysis stage.
NO NAME ROLE
1 Mulugeta Gebino In All activity
2 Tsega Bezabih In All activity
3 Yehualashet Wonde In All activity
4 Meseret Mekayhu In All activity
5 Turifat Asfa In All activity
6 Tademe Zewdihun In All activity
Table 1.5 Task Breakdowns

1.10 Communication plan

Communication plan describes the schedule of group member or the time of communication plan to
develop project. The group member communicates four days in each week and communicates for 3 hours.
ID Task Name Start Finish Dura琀椀on

1 Proposal 03/01/2022 10/01/2022 1 week

2 Documenta琀椀on 11/01/2022 25/01/2022 2 week
3 Design 26/01/2022 26/03/2022 2 month
4 Implementa琀椀on 27/03/2022 27/06/2022 3 month
5 Presenta琀椀on 29/06/2017 30/06/2022 2 days

1.1 Time Schedule

Table 1.6 Time Schedule

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Chapter Two

Description of the existing system

2.1 Introduction
Description Of the existing system is the detailed study of the various operations performed by the system
and their relationships within and outside the system. Analysis is the process of breaking something into
its parts so that the whole may be understood. System analysis is concerned with becoming aware of the
problem, identifying the relevant and most decisional variables, analyzing and synthesizing the various
factors and determining an optimal or at least a satisfactory solution. During this a problem is identified,
alternate system solutions are studied and recommendations are made about committing the resources
used to design the system.

2.2 Existing System

2.2.1 Existing System Description
In Arba minch town has providing many services. But the development team concentrates to Court
information management system. How to hold data or file. So this description contains two major cases.
Those are civil case and criminal case including their sub branches according to our e.
Civil case proceeding is case among or between two individuals. Types of civil case are family issue,
property and succession. Since civil case takes place between two individuals; the accuser opens the case
to the court. The court registered the case. This is done by law officer or registrar office. The law officer
verifies the case. In this case or during verification; the case may be accepted or rejected. If the case
accepted the law officer receive court fee. The amount of the court fee depends on the case type. Then
he/she register court fee on the paper. After that the database administrator records the amount of the court
fee into the database including plaintiff details. The judges give appointment to accuser. Then the law
officer write summon for the accuser. The accuser sends summon to the accused person. On the day of
appointed the law officer collects the case and give to the judge on manually. All information record on
paper documented.
In the second phase the judge sees the case and rendering decision is given by judgment passer. If extra
information is needed, the judge gives appointment on the other days. The appointment date is recorded
on paper. The process repeated in the manner starting from hearing to rendering decision.
The criminal case is the same process like civil case what makes it different is that it can be conducted
between state and individuals. Public prosecutor investigates, collect information and evidence and so on.

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

The summon send to the accused when the accused is present on the appointment he/she can defense the
case. In both civil and criminal case all information, detail of accuser and accused as well as advocator
detail and also their words registered on the paper.
If the customers want to appeal, the law officer gives the appeal. There is limitation date to ask appeal
after decision made by judges. Then if one asks appeal, the hard copy of all his/her document including
words of witnesses given to him/her within a given time.
The other is if customer wants to give his/her comment for employees or for organization; he/she
writes and put it in comment box. In order to give comment for them one must go there. On the holding of
data; the file saved in two ways active files and dead files. Those files handle manually. Also searching
document is takes place manually. If the law officers want to assigned case, they search by case card in the
shelf. this is very difficult to find the accuser document.

2.2.2 Why describe the existing system

The main reason why the existing system describing is:-
• To know the back ground of the existing system.

• To identify which of these problems could be solved by the current project.

• To determine the essential business practice to be preserved if any.

• To identify problem of the existing system.

• To know the statement of the problem and challenge of the system and to come up with the
perfect solution.

2.2.3. Problems of the existing system

Problems are undesirable situations that hinder the organization from fully achieving its purpose, goals or
objectives.
Performance
The performance of the existing system does not provide fast response time because it is difficult to access data
from the stored document. And also, it is slow /time and energy consuming.
Security and Controls
Every record of document in the existing in Arba minch Court Information Management System is stored in the
manual way, so, it is difficult to control and secure these manual records, since it doesn’t have any authentication
and authorization system.

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Economic
• Due to the operation that is done by the hand most of the activities are causes to high consumption of
resources like papers, man power, time, pen etc. This makes the existing system costs are too high.
Data storage problem
• Data are not easily accessible due to place in different location.

• Difficult to change and edit.

• Data redundancy that leads to inconsistency

2.2.4 Alternative options to address the problems of existing system

After the team has identified the real problem of the existing system which is in a manual system, the team suggests
an alternative option to overcome the problem.
These alternative options are:-
• Changing the manual system into web based system.
• Changing the manual system into a computer system that works on web based environment.
The team has analyzed all of the alternative options based on the ability of performance, information flow and
service to the users and efficiency. This analysis has enforced to select the web based system.

2.3. Supplementary Requirements

2.3.1. Business Rule
There are some business rules and constraint to prevent any violation during process. This focuses on
access control issue.
BR1: The client must be come to the office on the appointment day.
BR2: The judge assigned for one case does not changed from that case.
BR3: any appointed case can see within 10 up to 15 days.
BR4: Civil cases must see by civil law Judge
BR5: Criminal cases must see by criminal law Judge
BR6: If accuser, accused, advocator or public prosecutor does not satisfied to the decision of
judges, he/she can ask appeal to the upper court.
BR7: Seeing active case except the judge assigned is impossible for the others.
BR8: any accused or accuser can’t defend by himself can represent advocator.
BR9: All employees have their own responsibility such as to come on time at the work place, do
their work as rule and regulation of the court.

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

BR10: In court management system administrator has responsibility to manage all the system in
court. He/she has authority to managing information, financial order, and ordering work flow,
manages employee and etc.

2.4 The New Proposed System

After observing the current manual court management information system and evaluating all the
problems occurred during every activity on the existing system the project team has desired to design a
web based court information system for the administrator, law officers and judges can view information at
any time and place. The judge can easily see the assigned case and can know the appointment dates. This
helps to give appointment for customers. The new proposed system used to save times and money for
customers and for the organization. The new proposed system is suitable for employees to find customers
information in short time. The new proposed system is suitable for register for customer information and
record the final decision of customer’s case. The new system used store more data in a small space. The
new system used for customers easily finds the advocators by searching in the website of DBTCIMS. This
helps to save the time and cost etc.
The proposed system will use the major functionality of the existing system able to advance accordance
with speed of performance, security and reliability of the system, by using different object oriented
techniques in order to overcome the current problems.
Advantages of the newly proposed system
The advantage of the new system is:

• Performance:-the system will have faster response time and use minimal space usage.

• Speed:-regarding on the speed the system will generate output within short times.

• Reliability:-the system is reliable by analyzing each business rule set by the organization

• Security:-the system provides or contains user name and password for each users based on their privilege.

• For administrative it is best to see the weekly, monthly and yearly report and activity. It also helps to know
how the judge is resolving problems and it helps to getting feedbacks from the customer about the court
management information system. For the organization, the system will help saving cost and time.

• The new proposed system used to minimizes the number of tasks that labeled to the employees.

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

• Economy: when we apply Wed based court information management system there will be areas in
which cost will be reduced. Example as a result of a new system the payment too many employees
will be reduced. Reduce cost of paper and other materials.

• Efficiency: the Web based court information management System by itself is short and clear and in
this system there is no duplication of data through the new system is powerful to manage things.

2.4.1 Software Requirement Specifications (SRS )

2.4.1.1 Functional Requirements

A functional requirement specifies what the system should do to perform some task. The following are
some functionalities of the system.
• The system would able to handle the data properly. This means data is stored on database, so the
documents do not fade and loss.
• The system would able to search the file within short time. In the proposed system if the workers
want to find document can easily find the document by using case id and other criteria.
• The system would able to assign the cases to the judges. This means the law officers can easily
assigned the judge to the new open cases by looking the previous appointment whose judges have
more active cases by using user ids and date.
• The system would able to giving appointments for the customers. This means the judges can easily
look the previous appointment and give appointment for customers
• The system would able to giving comment online to administrators. this helps to know the
activities of employees by receive the feedback from the customers
• The system would able to generate reports. If the law officer or the administrator wants to see the
activities of employee, weekly, monthly dead files and active files can see by generate the
information in different ways. This means can see any information by using any primary key id.
• The system would able to record final decision and evidences. This means the judges can easily
record the final decision of customer’s case with evidence in secured ways in the database.
• The system would able to view information for customers. anyone can access the information by
using the website of Arba minch court information management system
• The system would able to register the details of accuser, accused, and advocator properly. The
proposed system is suitable for register the customers full name , sex, age, case type and
description of cases ,court fees and etc.

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

• The system should allow adding new user account; modifying recent users account and delete user
account. This can delete or modify the customers or other user by using user id.
• The system should allow giving privileges to each user. The proposed system can give privilege
only the authorized users can access.
• The system should allow changing their password.
• The system enforce only authorized user to perform this task.

2.4.1.2 Non-functional requirements

• Accuracy: proposed system will be better due to reduction of error. All operation can be one
correctly and it ensures that whatever information is coming from the data base is accurate.
• Reliability: The reliability of the proposed system will be better due to proper storage of
information when users access the application.

• No Redundancy: In the proposed system can be avoided reputation of data anywhere in the
database.

• Availability: All data in the system will be available all the time.

• Efficiency: The system must ensure allocation and use of services being requested for the users by
using minimum memory storage, cost, time and human power.

• User friendly Interface: Users can easily input and retrieve their profile and history.
• Security: The system should allow login to only authorized users. For security issue, only
authenticated user can visit the system. Usability: The system is user friendly. It can be easily
understandable by the user. Any user who have known how about computer can easily do with it.
For employers of the courts tutorials will give to adopt the system.

• Error handling: The system handles an error done by the user and display error message.

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Chapter Three
Analysis deliverables of new system
3.1 Introduction
Analysis is the process of breaking something into its parts so that the whole may be understood. System
analysis is concerned with becoming aware of the problem, identifying the relevant and most decisional
variables, analyzing and synthesizing the various factors and determining an optimal or at least a
satisfactory solution. During this a problem is identified, alternate system solutions are studied and
recommendations are made about committing the resources used to design the system

3.2 use case diagram

Essential use cases are of primary importance early in a project’s analysis phase. Essential use case
contains actors, use cases, basic course of action and description. An Actor is a person, organization or an
external system/sub-system/program that has interactions with the application and drawn in stick man
shape. A use case describes a sequence of actions that provide something of measurable value to an actor
and drawn in horizontal ellipse.

3.3 System Use case diagram

Use Case represents interaction between the user and the system.
The following use cases have been identified from the system specification

• Login
• Manage account
• Generate report
• New case registration
• Advocator registration
• View appointment
• Give appointment
• Record decision
• Search Customer Information
• View assigned case
• View decision
• Give comment
• View information

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

• The identified actors that will be participating in the system are

• :Actors
• Administrator
• Criminal Law Officer
• Civil Law Officer
• Judge
• Customer

Figure 3. 1 System use case

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

3.3.1 Use Case Documentation

Use case Name Login

Actor/s Administrator, Civil and Criminal Law Officer and Judge
Description It allows user to login in to enter the system
Precondition The users must have user name and password.
Post condition The user will get system home page and able to access as his/her privileges.
Basic course of Actor action System response
action: Step 1. The users want to login into Step4. The system verifies the username
the system. and password.
Step5.The system displays the appropriate
Step2.The user fills his/her user name home page.
and password and click login button. Step6. The use case ends
Alternate course A3. The username/password is invalid.
of action: 3.1. The system displays error message.
3.2. The system continues at step 3 to fill user name and password again.

Table 3. 1 Use Case Documentation for Login

Use case Name Generate Report

Actor/s Administrator, Civil and Criminal Law Officers and Judges
Description It allows generating report in the database.
Precondition He/she must login in to the home page login form
Post condition Successfully generate report as him/her wanted.

Basic course of Actor action System response

action: Step 1. Open the generate report link Step2. The system
form menu. Displays the page.

Step3. Select link he/she want to Step4. The system displays the selected report.
generate a report. Step5. The use case ends

Table 3. 2 Use case documentation for generate report

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Use case Name Create Account

Actor/s Administrator
Description It allows administrator to create for new user accounts.
Precondition He/she must login in to the home page.
Post condition The system successfully created account.
Basic course of Actor action System response
action: Step 1. Open the manage Step2. The system Displays the Manage account page.
account page. Step4. The system display create account page.
Step6. The system display successfully created
Step3. Open create account message.
link. Step 7. The use case end.

Step5. Administrator fill

create account form and click
create button.
Alternate A5. Invalid information entry
course of
5.1. If enter incorrect ID error message display for the user
action:
5.2. Go to step3 and fill again

Table 3. 3 Use case documentation for Create account

Use case Name Update Account

Actor/s Administrator
Description It allows administrator to update user accounts.
Precondition He/she must login in to the home page.
Post condition The system display successfully updated account.

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Basic course of Actor action System response

action: Step 1. Open the manage Step2. The system Displays the Manage account
account page. page.
Step3. Open update account Step4. The system display update account page.
link. Step6. The system display successfully updated
Step5. Administrator fill update message.
account form and click create
Step 7. The use case end.
button.
Alternate A5. Invalid information entry
course of 5.1. If enter incorrect ID error message display for the user
action: 5.2. Go to step3 and fill again
Table 3. 4 Use Case Documentation for Update account

Name View Appointment

Actor/s Civil and Criminal Law Officer, judge
Description It allows civil and criminal law officer to view appointments.
Precondition He/she must login in to the home page.
Post condition Civil and criminal law officers and judge successfully view selected information.
Basic course of Actor action System response
action: Step 1. Open the view appointment Step2. The system
form from menu. Displays the view appointment page.
Step4.The system
Step 3. Law officers and judge enter Displays selected information.
appointment date and judge id and Step5. The use case ends
click search button.

Alternate 1.Invalid information entry

course of
2.1If enter incorrect date error message display for the user
action:
3. Go to step3 and fill again

Table 3. 5 Use Case Documentation for View Appointment

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Use case Name View Information

Actor/s Customer
Description It allows customer to view information that is the information of advocator and courts.
Precondition Open view information page from website.
Post condition He/she see information.

Basic course of Actor action System response

action: Step 1. Open the view information Step2. The system
page. Displays the
Step3. Select one from lists link. View information page.
Step4. The system display information.
Step6. The use case ends

Alternate • Unknown the website.

course of
action:
Table 3. 6 Use case documentation for view information

Name Search Customer Information

Actor/s Administrator , Civil and Criminal law Officer and Judge
Description It allows Administrator, Civil and Criminal law Officer and Judge to search the
required information in the data base.
Precondition They must login in to the home page.
Post condition Successfully display the required information.
Basic course of Actor action System response
action: Step 1. Open the search Step2. The system
Customer Information Displays the search customer information page.
page. Step4. The system displays the selected user
information.
Step3. Enter input and Step5. The use case ends
Click Search Button.
Alternate A3. Invalid information entry

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

course of 3.1 If enter incorrect ID error message display for the user
action:
3.2 Go to step3 and fill again

Table 3. 7 Use case documentation for search customer information

Name Give Appointment

Actor/s Judge
Description It allows judge to give appointments for customers.
Precondition He/she must login in to the home page.
Post condition judge successfully give appointment.
Basic course of Actor action System response
action: Step 1. Open the give Step2. The system
appointment page from Displays the give appointment page.
menu. Step4.The system
Step 3. Judge fills the Displays success or fail.
form. Step5. The use case ends

Alternate A3.Invalid information entry

course of
3.1 If enter incorrect date error message display for the user
action:
3.2 Go to step3 and fill again

Table 3. 8 Use case documentation for Give appointment

Name New case Registration

Actor/s Civil Law and criminal Law Officer
Description It allows the law officer to register new case.
Precondition he or she must login in to the home page.
Post condition Successfully registered.
.

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Basic course of Actor action System response

action: Step 1. Open the new case Step2. The system
registration link from menu. Displays the
Step3. Fill the new case Registration form.
registration form and click Step4. The system displays registration successfully
Register button. or failed.
Step5. The use case ends

Alternate A3. Invalid information entry.

course of 3.1 The system displays error message.
action: 3.2 Go to step 3 to fill again

Table 3. 9 Use case documentation for new case registration

Name Register Advocator

Actor/s Law Officer
Description It allows the law officer to register Advocator. Those are for accuser or accused
person.
Precondition He or she must login in to the home page login form .
Post condition Successfully registered.
Basic course of Actor action System response
action: Step 1. Open the advocator Step2. The system
page from menu. Displays the
Step3. Fill the advocator Registration form.
registration page and click Step4. The system displays registered successfully or
save button. failed.
Step5. The use case ends
Alternate A3 Invalid information entry.
course of 3.1 The system displays error message.
action: 3.2.Go to step 3 to fill again
Table 3. 10 Use case documentation for advocator registration

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Name View Assigned Case

Actor/s Judge
Description It allows the judge to view the assigned case.
Precondition He/she must login in to the home page.
Post condition See the assigned case.
.
Basic course of Actor action System response
action: Step 1. Open view assign case page Step2. The system
from menu Displays the View assigned case page.
Step3. Enter the date and Judge ID in Step4. The system displays assign case or
the view assigned case page form and no assigned case.
click view button. Step5. The use case ends

Alternate A3 Invalid information entry.

course of 3.1 The system displays error message.
action: 3.2.Go to step 3 to fill again
Table 3. 11 Use case documentation for view assigned case

Name Record decision

Actor/s Judge
Description It allows the Judge record the decision.
Precondition He/she must login in to the home page.
Post condition Successfully record the decision.

Basic course of Actor action System response

action: Step 1. Open the record page from Step2. The system
menu Displays the
Step3. Record the decision in the Record Decision page.
record page and click Save button. Step4. The system display record
successfully or failed.
Step5. The use case ends
Alternate A3 Invalid information entry.
course of 3.1 The system displays error

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

action: message.
3.2.Go to step 3 to fill again
Table 3. 12 Use case documentation for record decision

Name View Decision

Actor/s Administration
Description It allows administrator to view decisions of every case passes by judges.
Precondition He/she must login in to the home page.
Post condition Successfully view decisions.

Basic course of Actor action System response

action: Step 1. Open the view decision Step2. The system
page from menu Displays the
Step3. Enter input to view View decision page.
decision and click search button. Step4: the system display list of cases.
Step5: Select cases and click Step6: The system displays selected case
view button. information in details.
Step7. The use case ends

Alternate A3 Invalid information entry.

course of 3.1 The system displays error
action: message.
3.2.Go to step 3 to fill again
Table 3. 13 Use case documentation for View Decision

Name Give Comment

Actor/s Customers
Description It allows customer to give comment about court office.

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Precondition He/she must know court office website.

Post condition give comments
Basic course of Actor action System response
action: Step 1. Open the give comment Step2. The system
page Displays the give comment page.
Step 3. Customer write comment Step4.The system
and click send button. Displays success or fail.
Step5. The use case ends
Table 3. 14 Use Case Documentation for Give Comment

3.4 Analysis level of class diagram

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. [5] Those can be shown in the
following table.

Class name

Responsibilit Collaborator
y
Name: The name, located at the top of the card, describes the class that the CRC card represents.

Responsibility: A responsibility is something that a class knows or does, represented along the
left side of the card.

Collaborators: Responsibilities will collaborate with one or more other classes to fulfill one or
more Scenarios. Collaborators are listed on the right hand side of the CRC card, next to the
responsibilities that they are helping to realize.

Login

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

User name Administrator ,

Password Civil and Criminal
Law Officer,
Login()
Judge pages
Registration
Id:

Name

Age

Sex Law officer form

Address

Phone no

Case type

Case id

Court fee

Register()

Reset()

Assigned case
Judge ID
Case ID
Case type
Judge
Date
Send() form
Reset()

Manage account

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

User id
User name
Password
Confirm password
create()
update()
delete()
reset()

Give Appointment

Case ID Law officer form

Date

Judge ID

Submit()

Search

CaseID Registration
Form
Date

JudgeID

Search()

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Comment
Name

Address

Administrator
Date
Form
Comment

Submit()

Table 3. 15 Analysis level of class diagram

3.5 Sequence diagram

A sequence diagram in a unified modeling language (UML) 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

Figure 3. 2 Sequence diagram for login

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Figure 3. 3 Sequence diagram for new case registration

Fig 3.5.3 Sequence diagram for Give Appointment

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Figure 3. 4 Sequence diagram for View Information

3.6 Activity diagram

An Activity diagram is similar to a flowchart to represent the flow from one activity to another activity.
Activity diagrams and State chart diagrams are related. While a State chart diagram focuses attention on
an object undergoing a process (or on a process as an object), an Activity diagram focuses on the flow of
activities involved in a single process. The Activity diagram shows how these single-process activities
depend on one another.

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Figure 3. 5 Activity diagram for login

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Figure 3. 6 Activity Diagram for Advocator Registration

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Figure 3. 7 Activity Diagram for View Appointment

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Figure 3. 8 Activity Diagram for View Information

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Figure 3. 9 Activity Diagram for Search Customer Information

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Figure 3. 10 Activity Diagram for Create Account

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Figure 3. 11 Activity Diagram for Give Comment

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

Figure 3. 12 Conceptual modeling using class diagram

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

3.8 Essential User Interface Prototyping

User interface prototype is to indicate the surface that can be used by user and the system to communicate
to each other, but, not actual work area.

3.8.1 User Interface Prototyping as Flow Chart Diagram

Figure 3. 13 UI Flow Chart Diagram

3.9 Change cases

Change case will used to describe potential modifications requirements to the system.
There are many cases that change the content of the project. From these:-
• Missing activities: -Where there the important activities missed in each project development
phase and the developing team latterly understood them, they should include them.

Downloaded by Steve Zenebe (steveiamid@gmail.com)

 lOMoARcPSD|36041483

• Important comments: - When crucial comments are raised from the advisor, teachers and
examiners that should be included and excluded the developing team assess the project again.
• Lack of resources: - If there is scarcity of resources occurred to develop many system activities,
the developing team also restructured the contents of the project.

Downloaded by Steve Zenebe (steveiamid@gmail.com)