MIZAN TEPI UNIVERSITY TEPI CAMPUS

School of computing and informatics

Department of software Engineering
court information management system for sheka zone 1st
instant court
A mini project (documentation)
Prepared by group six:
Name id
1. Gebreslassie Dessie……………………………………..MTUUR /1440/14
2. Begna Leta……………………………………………....MTUUR/0629/14
3. Firomsa Dine…………………………………………….MTUUR/1386/14

Submission date 15/08/2016 E.C

Submitted to Mr. Melkamu d.

Mizan-tepi, Ethiopia

May, 2024

Acknowledgements
First of all, we want to thank the God who made all things good. We would like to express our
greatest gratitude to the people who have helped & supported us throughout our project.
 Web-based court information management system
2016E.
c
We grateful to our advisors Mr. melkamu for his support for the project, from initial advice and
contacts in the early stages of conceptual inception and through ongoing advice and
encouragement to this day. We wish to thank all peoples who contribute their own part for their
support and interest who inspired us and encouraged us. And we want to thank our teacher and
friends who appreciated us for our work and motivated us.

2|Page
 Web-based court information management system
2016E.
c

Abstract
The purpose of this project is to full fill the requirement of bachelor degree of Information
System as mini project in order to develop. 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.
Sheka zone 1st instant 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 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.

3|Page
 Web-based court information management system
2016E.
c
Table of Contents
Acknowledgements........................................................................................................................................ii
Abstract.........................................................................................................................................................iii
Chapter One...................................................................................................................................................1
1. Introduction................................................................................................................................................1
1.1 Background University........................................................................................................................1
1.2 Background of the project....................................................................................................................1
1.3 Team Composition...............................................................................................................................2
1.4 Tasks and Schedule..............................................................................................................................2
1.4.1 Project Initiation (Week 1)...........................................................................................................................2
1.4.2 Requirements Gathering (Week 2)..............................................................................................................3
1.4.3 System Design (Week 3-7)..........................................................................................................................3
1.4.4 Development (Week 8).......................................................................................................................3
1.4.5 Implementation (week 9).............................................................................................................................3
1.5 Statement of the Problem.....................................................................................................................3
1.6 Objective..............................................................................................................................................4
1.6.1 General objective.........................................................................................................................................4
1.6.2. Specific Objective.......................................................................................................................................4
1.7 Scope of the project.............................................................................................................................5
1.8 Feasibility.............................................................................................................................................5
1.8.1 Operational feasibility..................................................................................................................................6
1.8.2 Technical feasibility.....................................................................................................................................6
1.8.3 Economic feasibility....................................................................................................................................6
1.8.4 Behavioral /Political feasibility....................................................................................................................6
1.8.5 Schedule feasibility......................................................................................................................................6
1.9 Schedule Feasibility.............................................................................................................................8
1.10 Methodology......................................................................................................................................9
1.10.1 Data collection...........................................................................................................................................9
1.11 System analysis and design................................................................................................................9
1.12 Implementation Methodology..........................................................................................................11
1.13 Development Environment and Programming Tools......................................................................11
1.14 Significance of the project...............................................................................................................11
1.15 Limitation of the project..................................................................................................................13
Chapter Two................................................................................................................................................13
2.0 Introduction............................................................................................................................................13
2.1 Description of the Existing System...................................................................................................13
2.2 Why describing the existing system is important?............................................................................14

4|Page
 Web-based court information management system
2016E.
c
2.3 Player’s in the existing system...........................................................................................................14
2.4 Major functions/activities in the existing system..............................................................................14
2.5 Business rules....................................................................................................................................15
2.6 Report generated in the existing system............................................................................................15
2.7 Forms and other documents of the existing systems.........................................................................16
2.8 Criminal and law and Civil law file opening form............................................................................17
2.9 Bottlenecks of the existing system.....................................................................................................19
2.10 Practices to be preserved..................................................................................................................20
2.11 Proposed solution for the new system that address problems of the existing system.................20
2.12 Requirements of the Proposed System............................................................................................20
2.12.1 Functional requirements...........................................................................................................................20
2.12. 2 Non-functional requirements..................................................................................................................21
Chapter Three...............................................................................................................................................23
System Analysis...........................................................................................................................................23
3.2 System Requirement Specifications (SRS)........................................................................................23
3.2.1 Use case diagrams......................................................................................................................................23
3.2.2 Use case documentation.............................................................................................................................27
3.2.4 Activity Diagram.......................................................................................................................................47
3.2. Analysis level class diagram (conceptual modeling)........................................................................54
3.2.6 User Interface Prototyping.........................................................................................................................56
3.2.7 Supplementary specifications....................................................................................................................57
Chapter Four................................................................................................................................................58
System Design.............................................................................................................................................58
4.1 Introduction........................................................................................................................................58
4.2 Class type architecture.......................................................................................................................58
4.3 Class modeling...................................................................................................................................60
4.4 State chart modeling..........................................................................................................................63
4.5 Collaboration Diagram.......................................................................................................................68
4.6 Component Modeling........................................................................................................................74
4.7 Deployment modeling........................................................................................................................75
4.8 Persistence Modeling /database design..............................................................................................76
Chapter five……………………………………………………………………………………………..…78
5.1Conclusions.............................................................................................................................................77
5.2 Recommendation………………………………………………………………………………...……78
References ………………………………………………………………………………………………78

5|Page
 Web-based court information management system
2016E.
c

List of Tables
Table 1: Team composition
Table 2: Tangible cost……………………………………………………………………………………5
Table 3: Cost of projects
Table 4: Gantt chart for Schedule
Table 5: Actor Specification
Table 6: Use Case Documentation for Login table
Table 7: use case documentation for logout table
Table 8: Use case documentation for generate report table
Table 9: Use case documentation for Create account table
Table 10: Use Case Documentation for Update account table
Table 11: Use Case Documentation for Delete account table
Table 12: Use Case Documentation for View Appointment
Table 13: use case documentation for view information table
Table 14: Use case documentation for search customer information table
Table 15: Use case documentation for Give appointment table
Table 16: Use case documentation for New case registration table
Table 17: Use case documentation for view assigned case table
Table 18: Use case documentation for record decision table
Table 19: Use case documentation for View Decision table
Table 20: Use Case Documentation for Give Comment table

6|Page
 Web-based court information management system
2016E.
c

List of Figures
Figure 1: File storage Forms of the existing system
Figure 2: New case registration form
Figure 3: Appointment Form
Figure 4: Use Case Diagram
Figure 5: Sequence diagram for login
Figure 6: Sequence diagram for new case registration
Figure 7: Sequence diagram for Give Appointment
Figure 8: Sequence diagram for Logout
Figure 9: Sequence diagram for recording decision
Figure 10 : Sequence diagram for assigned case
Figure 11: Sequence diagram for view decision
Figure 12: Sequence diagram for view appointment
Figure 13: Activity diagram for Login
Figure 14: Activity diagram for Create Account
Figure 15: Activity diagram for Give Appointment
Figure 16: Activity diagram to view client information
Figure 17: Activity diagram to new case registration
Figure 18: Activity diagram for Advocator registration
Figure 19: Activity diagram to view Appointment
Figure 20: Class diagram
Figure 21: UI Prototype
Figure 22: Class Type Architecture
Figure 23: Class modeling
Figure 24: State chart diagram create account judge…………………………………………………..
Figure 25: State chart diagram for create account
Figure 26: State chart diagram for login
Figure 27: State chart diagram for generating report
Figure 28: State chart diagram for assigning case
Figure 29: state chart diagram to view appointment

7|Page
 Web-based court information management system
2016E.
c
Figure 30: Collaboration diagram for register client
Figure 31: Collaboration diagram for login
Figure 32: Collaboration diagram for generate report
Figure 33: Collaboration diagram for register case
Figure 34: Collaboration diagram for create account
Figure 35: Collaboration diagram for Give Appointment
Figure 36: Component diagram
Figure 37: Deployment diagram
Figure 38: Persistence Modeling Diagram

Acronyms/Abbreviation

BR.......................................................Business Rule

CMS..................................................Court Management System

CIMS……………………………….Court Information Management System

CRS...................................................Class Responsibility Collaboration Diagram

GUI....................................................Graphical user interface

MTU....................................................Mizan-Tepi University

MS.......................................................Microsoft

OOA…...............................................Object-oriented analysis

OOD….............................................Object-oriented design

PC......................................................Personal computer

PHP…................................................Hypertext Preprocessor

PHP…................................................Hypertext Preprocessor

RAM…..............................................Random accesses memory

SDLC.................................................Software Development Life Cycle

SQL....................................................Structural Query language

SRS...................................................System Requirement Specification

8|Page
 Web-based court information management system
2016E.
c
UC…..................................................Use case

UML..................................................Unified model language

HTML………………………………….Hyper text markup language

Symbols

Actors

Use case

Node

Component
Package

Line connector
System boundary

Message
Dependency

Message return

Decision

9|Page
 Web-based court information management system
2016E.
c

Chapter One
1. Introduction
The advancements of the 21st century have led to an emergence of many disciplines with great
potential to solve existing problems. One such potential field is Technology, which has over the
years been increasingly adopted in many processes to avert the problems of ineffective and
inefficient service delivery. One of the key areas of interest is automation of the judicial
processes. Many challenges have been faced in the process of attaining justice including delays
due to misplacement of the case files at the registry when reference is ought to be made. As legal
practice has become more technologically advanced, pressure mounts on the courts is to join the
flow of technological progress in other to provide a good service delivery. In addition, to
emphasis on government transparency, to build public trust and confidence in judicial
institutions. Different organizations are established in order to give services to the
community. Among those our project is "Court information management system".
1.1 Background University
Mizan-tepi University is one of high level educations in Ethiopia. Its location is south part of
Ethiopia, which is 611km far from Addis Ababa. It has two campus, one of them is Tepi
Campus, under this campus school of computing and informatics is one of the collages with
different departments. Mizan-Tepi University has begun to give services for students in 1998
E.C.
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, 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 in sheka zone 1st instant court 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

1|Page
 Web-based court information management system
2016E.
c
means there is no online giving comment service before for the court found on the distance.
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 and robbers, save the data in secure way if needed, giving appointment for customer in
simple way, 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 Team Composition
Project Web based court information management system
Title
S. S. Name ID NO phone number Responsibilities
No
Prep 1 Gebreslassie Dessie MTUUR/1440/14 0902067211 Leader
aired by 2 Begna Leta MTUUR/0629/14 0910867533 Data collector
3 Firomsa Dine MTUUR/1386/14 0976151414 Designer
Date 15,april,2016
Adviser Mr. Melkamu D.
Table 1: Team composition
1.4 Tasks and Schedule
Task and Schedule for court information management System Project in Sheka zone first
instant court:

1.4.1 Project Initiation (Week 1)

 Define project scope, objectives, and deliverables

2|Page
 Web-based court information management system
2016E.
c
 Identify project team members and stakeholders
 Create a project charter and obtain approval.

1.4.2 Requirements Gathering (Week 2)

 Conduct interviews with court office and management staff to understand current
processes and pain points
 Document functional and non-functional requirements for the digital system
 Prioritize requirements based on business needs.

1.4.3 System Design (Week 3-7)

 Develop system architecture and data flow diagrams
 Design user interface and user experience
 Create wireframes and mockups for key system functionalities

1.4.4 Development (Week 8)

 Build database structure and data models
 Develop core system functionalities such as employee onboarding, performance
management, and reporting.
 Conduct iterative testing and quality assurance to ensure system reliability

1.4.5 Implementation (week 9)

 Train court office and management staff on using the new digital system
 Migrate data from legacy systems to the new digital platform
 Roll out the system in phases to different departments or locations.
1.5 Statement of the Problem
Court information management system of sheka zone 1st instant court 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

3|Page
 Web-based court information management system
2016E.
c
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
 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
1.6 Objective

1.6.1 General objective

Our main objective is to develop web based court information management system for sheka
zone 1st instant court office.

1.6.2. Specific Objective

The specific of this project is to develop software that controls court information
Management system. This system includes Specific Objective.
 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.

4|Page
 Web-based court information management system
2016E.
c
 To develop a secured Data base system
 To develop suitable system to give appointment and assign cases.
 To develop the court information management system. .
 To create an administrator page that will show statistical analysis.

1.7 Scope of the project

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 finished cases decisions and the eviden Register finished cases decisions and
the evidence of the witness.
 View assigned cases that law officers are assign to Judges
 Register Any Advocator with full address that wants to give service for customer
 Register appointment dates that judges give for customer.
 Make the system high secure, efficient and effective
 View assigned cases that law officers are assign to Judges
 Register any customer that wants to open new case and assigned cases to judges.
 Generate reports based on customer queries
 avoiding the data redundancy of the system.
 Search the files in short times from many files.
 Update employee's information.
 Record examination, cross examination and reexamination in the database
while collecting evidence from witness.
 Accept comment that customers are writing for court offices.
1.8 Feasibility
Feasibility study is used to investigate the proposed system in multiple dimensions. It used to
indicate whether the system feasible or not. Feasibility study is an important phase in both
research and software development process. It enables the developer to have an assessment of

5|Page
 Web-based court information management system
2016E.
c
the product being developed. It refers to the feasibility study of the product in terms of outcomes
of the product, operational use and technical support required for implementing it. Feasibility
analysis is undertaken to prove if the proposed system is valuable to implement.Our system
feasibility can be seen according to the following literals.

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

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 Economic feasibility

The project that we are going to develop is economically feasible than the manual system.
Manual system uses 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.

1.8.4 Behavioral /Political feasibility

The political feasibility is a feasibility that makes sure the system does not break law. Our
system does not violent with any law, hence the system is politically feasible.

6|Page
 Web-based court information management system
2016E.
c
1.8.5 Schedule feasibility
Schedule feasibility is a feasibility that makes sure that the proposed system completed in a time
given and we are dead sure that we will complete the developing the system in a given time
frame since all member of the team are quit dedicate and potential.

1.8.5.1 Tangible Cost

This cost contains the various types of costs in which you spent for the development of the
project or the University sponsors some of the hardware, network services expenses. The
following table lists the different miscellanies costs that have been used in the process of the
development of the system.

Table 2: # Item Name Quantity Cost

Tangible Cost 1 Paper 250 50 birrs
2 Flash 16GB 1 250birr 1.8.5.2 Intangible Cost
Intangible cost 3 Document print 20 40 birrs is uncountable cost that
to be acquired in developing the system
.It comprises stakeholder knowledge, skill and effort. The project team advisor advice and the
project team themselves knowledge and effort apply to develop the system may not be
measurable in terms of money.

1.8.5.3 Cost of the projects

Item Price /Birr

Labor cost 700 ETB
Paper 40 ETB
Computer 10,500 ETB
Printer 50 ETB
Flash 200 ETB
Laptop 40,0000ETB
Total material cost 51490ETB

Table 3: Cost of projects

7|Page
 Web-based court information management system
2016E.
c
1.8.5.4 Cost Breakdown
Beside tangible and intangible costs, we breakdown cost of system development into two:
onetime cost and recurrent cost.
One-time cost: Is a cost with project up and developments or system startup. This mean that it
refers to those associated with project initiation and development cost and the startup of the
system. The cost typing encompasses activities such as system development, new hardware &
software purchase or system startup user training, and system or data conversion.
Recurrent cost: Recurrent costs are those incurred for goods and services in the course of a
budget year and which must be regularly replaced since we are developing this system as senior
project, we may not gain any income
1.9 Schedule Feasibility
Schedule feasibility defines the starting and ending date of the project and manages the duration
of activities until the given project is finished. Time evaluation is the most important
consideration in the development of project. The time schedule required for the developed of this
project is very important since more development time effect machine time, cost and cause delay
in the development of other system.
1st quarter 2ndquarter 3rd quarter 4th quarter 5th quarter

S .No Phases Feb13- March5- March17- April5- May17-

march4/2016 march15/2016 april3/2016 may15/2016 may25/2016

1
Project proposal

2 Requirement
Analysis and
Modeling

Design
3

Implementation
4

Installation&
Project

8|Page
 Web-based court information management system
2016E.
c

5 Closure

Table 4: Gantt chart for Schedule

1.10 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.10.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. Direct 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.
C. Analysis of existing document: To get more information about the existing system we use
earlier documents that are stored in the sheka zone first instant court office. During the analysis

9|Page
 Web-based court information management system
2016E.
c
of documents, we give special consideration to those documents which can bring more features
to the project.
D. Questionnaires: This is another method that we were used to gather information about the
current system and how the users satisfied with the system.
1.11 System analysis and design
T he t e a m plan to use the Object Oriented Software Development Methodol ogy
(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.
 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:-

10 | P a g e
 Web-based court information management system
2016E.
c
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.12 Implementation Methodology
 For Front end programming we will use: CSS, JavaScript, HTML
 For Server-Side Scripting, we will use: PHP
 For Backend (Data Storage) we will use MYSQL Server. Because it requires low
computer resource requirements and is easy to implement for web systems.

1.13 Development Environment and Programming Tools

Our team uses the software and hardware tools for developing the project.
A. Hardware tools
 Computer with internet connection use to do a project.
 Secondary storage device like flash disk (16 GB) used to backup data.
 Projector used to present the project.
 Hard disk

B. Software tools
 MySQL: - to develop a database application
 Microsoft office word (2010):- for documentation.
 E-draw max: - for designing UML diagrams, a user interface associated with the project.
 Sublime text: - we will use for writing the code of the system

11 | P a g e
 Web-based court information management system
2016E.
c
 PHP:- For server-side.
 HTML, JAVASCRIPT client-side coding:-For user interface of the system.
1.14 Significance of the project
After the implementation of this project, it provides various benefits.
I 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.
 Customer can see some news on distance.
 Customer informed appointments day and time remotely.

II This project has its own significance to the law officer as follow

 Easy to store all data of the accuser and accused person documents neatly, files may be
not stolen by thieves, robbers or internal attackers, and files does not fade because of long
life and files may not be destroyed by natural disasters like fire flood, generally no
security problems.
 Adequate and fast communication with judge and other coworker.
 Accessing individual document is not bulky and no consumes time with our system.
 Assigning new case to judge easy and secure more with this this system.

III. This project has also its own significance to the judge officer.
 The judges find appointment date and time easily for many case in short period of time.
 Recording examination, cross-examination, and reexamination is easy while collecting
 Evidence from witnesses.
 Judge search appointed case and decide on it in easily.

12 | P a g e
 Web-based court information management system
2016E.
c
Generally this project has its own significance for the organization as follow:

 Very fast and accurate.

 May no need any extra manpower.
 It doesn’t require any extra hardware materials like paper, pen, pencil and etc.
 It reduces the wastage of time during searching and modifying employee
 Information, and also reduces cost and data loss.
 Reduce cost paid for extra hardware materials like pen, paper, and printing.
 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.
 To know the appointment date is very easy.
 Calculating court fee depending on cases become simple

1.15 Limitation of the project

 The system does not send appeals to the high court and Supreme Court because there is
no interconnected web-based system with zonal court office.
 Our system does not take online evidence from the witness.
 Our system has no court free or online payment.
 The system does not include sector office like jail and police.

Chapter Two
2. Introduction
The existing system partially works manually from the beginning to the end of the process. That
means information records on paper and documented way and various open and closed files are
not secure, more over it is not possible to accommodate the language you speak as you will not
be able to speak an official language.

13 | P a g e
 Web-based court information management system
2016E.
c
2.1 Description of the Existing System
Existing system contains two major cases. Those are civil case and criminal case including their
sub branches. 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 registers the case. This is done by office Registrar. On the day of appointed the law
officer collects the case and give to the judge on manually. All information recorded on paper
and 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 and posted on the board.
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.
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 accuser or accused
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.
2.2 Why describing the existing system is important?
The main reason why we describe the existing system is:-
 To know the background 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 problems 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.3 Player’s in the existing system.

14 | P a g e
 Web-based court information management system
2016E.
c
The Judge: The judge who presides in the court room. The judge rules on issues of law that
comes up in trial. The judge decides on the verdict if it’s a bench trial.District judges
determine the appropriate punishment and sentence those convicted of crimes.
The Public: With only a few exceptions, all hearings and trials are open to the public. You are
welcome to observe at almost any time.
Court Interpreter: Everyone involved must be able to hear and understand the proceedings.
Administrator: Who administrates the court.
Lawyer: can act as legal defense representing clients in civil or criminal proceedings.
Accused: a person or group of people who are charged with or on trial for a crime.
Accuser: a person who claims that someone has committed an offence or done something
wrong.
2.4 Major functions/activities in the existing system
 Case registration.

 Giving appointment.

 Assigning case to Jude.

 Decision making.

 Case hearing.
2.5 Business rules
There are some rules and constraint to prevent any violation during process.
If accuser, accused, lawyer or public prosecutor does not satisfied to the decision of judges,
he/she can ask appeal to the upper court.
Seeing active case except the judge assigned is impossible for the others.
Any accused or accuser can’t defend by himself can represent advocator.
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.
Generally our systems have the following business rules:-
BR1: The client must become to the office on the appointment day.
BR2: The judge assigned for one case does not changed from that case simply.

15 | P a g e
 Web-based court information management system
2016E.
c
BR3: Civil cases must be seen by civil law Judges.
BR4: Criminal cases must be seen by criminal law Judge
BR6: Seeing an active case except the judge assigned is impossible for the others.
BR7: any accused or accuser who can’t defend himself can represent an advocator.
BR8: All employees have their responsibility such as to come on time at the workplace, do their
Work as rule and regulation of the court.
BR9: In court management system administrator has the responsibility to manage all the
system in court.
He/she has authority to manage information, financial order, and ordering workflow,Manages
employees, etc.
2.6 Report generated in the existing system
Reports are important in order to check up the rules. It plays a vital role to achieve the court goal.
The court generates a report for the existing system in the form of files and forms. In an existing
system the reports are prepared manually.
2.7 Forms and other documents of the existing systems
The following form is used to identify data files stored in court office shelves such as opened
case, type of charge, file opening date, name of the plaintiff, and defendant decision date of the
existing system.

16 | P a g e
 Web-based court information management system
2016E.
c

Figure 1: File storage Forms of the existing system

2.8 Criminal and law and Civil law file opening form
The form which is shown below is used to open files which case related crime and civil.

17 | P a g e
 Web-based court information management system
2016E.
c

Figure 2: New case registration form

18 | P a g e
 Web-based court information management system
2016E.
c

Figure 3: Appointment Form

19 | P a g e
 Web-based court information management system
2016E.
c

2.9 Bottlenecks of the existing system

There are a lot of problems in the existing system as compared to the proposed system. These
problems can be seen from the following perspectives like performance, information, control,
efficiency and services given by the existing system to the users.
Problems are undesirable situations that hinder the organization from fully achieving its purpose,
goals or objectives.
Performance (Response time)
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.
Input (Inaccurate/redundant/flexible) and Output (Inaccurate) During filling the form
user make error at that time erase and change another form this one of redundant file that
means the existing system is inflexible to change because the system is manual due to this
reason the output of the system also inaccurate.
Data are not easily accessible due to place in different location;
Data redundancy that leads to inconsistency.
Inaccuracy in updating important information because of manual processing.
Security and Controls
Every record of document in the existing in 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.
Efficiency
Due to the manual operation most of the activities are prone to wastage of resources like papers,
man power, time etc., to produce the corresponding outputs. This makes the current system
inefficient while utilizing resources. There should be a mechanism that reduce wastage of
resources and that make the system to be efficient.
Economic
Due to the operation that is done by the hand most of the activities are causes to high

20 | P a g e
 Web-based court information management system
2016E.
c
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 being placed in a different location.
 Difficult to change and edit.
 Data redundancy that leads to inconsistency
2.10 Practices to be preserved
 New case registration form.
 Generating report.
The main business rules will be preserved as it is.
2.11 Proposed solution for the new system that address problems of the
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.12 Requirements of the Proposed System
A requirement is a formal definition for the functionality of a system. It contains conditions
about the performance and functionality of the entire system. The functionality can be classified
into two main groups; functional and non-functional requirements.

2.12.1 Functional requirements

A functional requirement specifies what the system should do to perform some task.
The functional requirements describe how the system will work in terms of its inputs, the

21 | P a g e
 Web-based court information management system
2016E.
c
behavior, and outputs. The following are some functionalities of the system.
Performance requirements: The system would able to handle the data properly.
This means data is stored on database, so the documents do not fade and loss.
Process requirements: 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.
Input related requirements: This will provide the registrar the authority to add new cases and
to terminate cases if they pass away.
Output related requirements: At the end of every day’s activities a report will be printed out
on the screen. So as to keep track of events.
Storage related requirements: This shall be developed to store, record, information about
users, (date, suit number, plaintiff, defendant, judge etc.) The system would be able to search the
file within a short time.
Generally our systems have the following activities:-
 The system would able to assign the cases to the judges.
 The system would be able to give appointments for the customers.
 The system would be able to give comments online to administrators. This helps to
know the activities of employees receiving feedback from the client.
 The system would be able to generate reports.
 The system would be able to record final decisions and evidence.
 The system would be able to view information for customers or clients.
 The system would be able to register the details of the accuser, accused, and
advocator properly.
 The system should allow adding new user accounts; modifying recent users’ accounts
and deleting user accounts by the president.
 The system should allow giving privileges to each user.
 The system should allow changing their password.
 The system should allow video and audio record.
 The system enforces only authorized users to perform this task

22 | P a g e
 Web-based court information management system
2016E.
c
2.12. 2 Non-functional requirements
Non-functional requirement describes how a system should behave and what limits there are on
its functionality.
Performance: The system shall allow several system users at the same time without
downgrading performance. Availability: The system shall be available and can be access
anywhere.
User Interface: Users can easily input and retrieve their profile and history.
Security and Access permissions: each user is required to login. The system shall allow people
with assigned user names and passwords. The system shall be designed to make it
impossible for unauthorized people to logon without valid usernames or password.
Backup and Recovery: This shall be developing to backup data periodically.
Accuracy: The system shall work accurately without high failure or error.
Reliability: The reliability of the proposed system will be better due to the system having low
system failure occurrence and low risk. And will not.
No Redundancy: In the proposed system can be avoided reputation of data anywhere in the
database.
Availability: The system shall be available to all courts and can be accessed anywhere.
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.
Security: each user is required to log in. The system shall allow people with assigned user names
and passwords. The system shall be designed to make it impossible for unauthorized
people to logon without valid usernames or password
Usability: The system shall be easy to learn and use by all users including the registrar and
administrator.
Error handling: The system handles an error done by the user and displays error messages
Constraints: Constraints are any events or circumstances that may restrict, limit, or regulate a
project.
The following are constraints that we might face while doing this project
Include:

23 | P a g e
 Web-based court information management system
2016E.
c
 Shortage of equipment.
 Electric power interruption
 Resources like time and human power.
 Shortage of internet connection.

Chapter Three
System Analysis
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. It is a process of collecting and interpreting facts,
identifying the problems, and decomposition of a system into its components.
System analysis is conducted for the purpose of studying a system or its parts in order to identify
its objectives. It is a problem solving technique that improves the system and ensures that all the
components of the system work efficiently to accomplish their purpose. Analysis specifies what
the system should do.
3.2 System Requirement Specifications (SRS)
A System Requirements Specification (SRS) is a document or set of documentation that
describes the features and behavior of a system. It includes a variety of elements that attempts to
define the intended functionality required by the customer to satisfy their different needs.

3.2.1 Use case diagrams

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 environment and related to a particular goal. The use case
should contain all system activities that have significance to the users. A use case can be thought
of as a collection of possible scenarios related to a particular goal, indeed, the use case and goal
are sometimes considered to be synonymous.

24 | P a g e
 Web-based court information management system
2016E.
c
Actors
 Administrator
 Criminal Law Officer
 Civil Law Officer
 Criminal Judge
 Civil judge
 Client
 Civil Advocator
 Criminals Advocator

Actors Actors’ role

Administrator  Manage account (Create account, Update account,
delete)
 Post schedule
 View appointment
 Can View decision, View feedback, or View comment
 Search Customer information
 Generate report
 Schedule
Law officer  Register: Advocator, new case, defendant
 Generate report
 Search customer information
 View appointment
 View information
 View post information
 Assign new case to judge
 Assign advocator

25 | P a g e
 Web-based court information management system
2016E.
c
 Login to the system
Judge  Record decision
 See the assigned cases
 Gives Appointment
 Search customer information
 View posted information
Client
 View his final decision
 Comment on court
 View appointment
 View advocator list, advocator view case
Table 5: Actor Specification

Use Case represents the 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
 View appointment
 Give appointment
 Record decision
 Create account
 Search Client Information
 View assigned case
 View decision
 Give comment
 View information
 Update information
 Logout.

26 | P a g e
 Web-based court information management system
2016E.
c

create delete update

account account account
view
decision register register
<<extend>>extend><><extend>>
view new case advocator
comment
manage
account search view Criminal
customer <<extend>><extend>>
schedule Judge
Administrator information
schedule

Generate Register
<<include>>
report <<include>>
<<include>>
Civil
<<include>>
<<include>> Judge

Civil law assign

officer advocator <<include>> login
to case
<<include>>
<<include>> view
<<include>> <<extend>> <<extend>> appointment
<<include>> day
Judge
assign case process
to judge logout Civil Advocator
view
Criminal view court
assigned
law information
<<extend>> <<extend>> case
officer <<extend>><<extend>>

Give
view view comment
assigned appointm
case ent
give record
view Customer
Criminal Advocator appointment decision
appointm
ent day

27 | P a g e
 Web-based court information management system
2016E.
c

Figure 4: Use Case Diagram

3.2.2 Use case documentation

Use case No UC-1

Use case Name Login

Actor/s Administrator, Civil, and Criminal Law Officer, civil and

criminal Judge, Civil and Criminal Advocator.

Description It allows those users to login in to enter the system

Precondition The users must have a user name and password.

Post condition The user will get the system home page and be able to access
it as his/her privileges.

Basic course of Actor action System response Step2.

action:
Step 1. The users want The system Displays the
to login into the system. Login Page
Step3.The user fills in Step4. The system verifies the
his/her user’s name and
username and password.
password and clicks the

28 | P a g e
 Web-based court information management system
2016E.
c
login button. Step5.The system displays the
appropriate home page.
Step6. The use case ends

An alternate A3. The username/password is invalid.

course of action:
A4. The system displays an error message.
A5. The system continues at step 3 to fill user name and
password again.

Table 6: Use Case Documentation for Login table

Use case name Logout

Actors Administrator, Civil, and Criminal Law Officer, civil and
criminal Judge, Civil and Criminal Advocator.
Basic course of action Step 1, The user stays in its
home page.
Step2, the user wants to logout.
Step3.The user clicks the logout
button
Step4. The user logout from the
system.
Step 5. The use case ends.
Exit condition When the user clicks log off button.
Pre-condition The user stays in the home page of the system.
Post condition The user logout from the system.
Table 7: use case documentation for logout table

Use case Name Generate Report

29 | P a g e
 Web-based court information management system
2016E.
c

Actor’s Administrator

Description It allows generating report.

Precondition He/she must login in to the home page login form

Post condition Successfully generate report as him/she wanted.

Actor action System response Step2. The

Basic course of
action: Step 1. Open the generate system Displays the page.
report link from the menu. Step4. The system displays The
Step3. Select the link he/she selected report.
wants to generate a report.
Step5. The use case ends

Table 8: Use case documentation for generate report table

Use case Name Create Account

Actor/s Administrator

Description It allows administrator to create account.

Precondition He/she must login in to the home page.

Post condition The system successfully created account.

30 | P a g e
 Web-based court information management system
2016E.
c
Actor action System response Step2. The
Basic course of
Step 1.Open the manage
action: system Displays the
account page
Step3. Open create an Manage account page.
account link. Step4. The system display creates an account
Step5. The administrator fills
create account form and clicks page.
create button. Step6. The system displays a
successfully created message.
Step 7. The use case end.

Alternate Invalid information entry

course of
action: 1. If enter incorrect ID error message display for the user

2. Go to step3 and fill again

Table 9: Use case documentation for Create account table

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.

31 | P a g e
 Web-based court information management system
2016E.
c

Post condition The system displays successfully updated account.

Basic course of Actor action System response

action: Step 1. Open the manage Step2. The system
account page.
Step3. Open update account link. Displays the

Step5. The administrator fills Manage account page.

update account form Step4. The system displays
and clicks create button. updated account page.
Step6. The system displays a
successfully updated message.

Step 7. The use case end.

Alternate Invalid information entry

course of
action: 1. If enter incorrect ID error message display for the user

2. Go to step3 and fill again

Table 10: Use Case Documentation for Update account table

Use case No UC-4

Use case Name Delete account
Actor/s Administrator

32 | P a g e
 Web-based court information management system
2016E.
c
Description It allows administrators to delete user accounts.
Precondition He/she must log in to the home page.
Post condition The system successfully deleted the account.
Basic course Actor action System response
of action: Step 1. Open the manage Step2. The system
account page. Displays the
Step3. Open delete Manage account page.
account link. Step4. The system displays the
Step5. The administrator delete account page.
deletes the account from Step6. The system displays a
the account list and clicks successfully deleted message.
the delete button. Step 7. The use case end.
An A5. Invalid information entry
alternate A6. If enter incorrect ID error message displays for the user
course of A7. Go to step3 and fill again
action:

Table 11: Use Case Documentation for Delete account table

Name View Appointment

33 | P a g e
 Web-based court information management system
2016E.
c
Civil and Criminal Law Officer, Civil and Criminal judge, Civil
Actor/s
and Criminal Advocator and client.
Description Allows Administrator, Judge, and Client to view appointment date.

Precondition He/she must login in to the home page.

Post condition Administrator, Judge, and Client successfully view selected information.

Basic course of Actor action System response Step2. The

action system
Step 1. Open the view
Displays the view appointment page.
appointment form from the
Step4.The system
menu.
Step 3. Civil and Criminal Displays selected information.
Law officers, Civil and Step5. The use case ends
Criminal judges Civil and
Criminal Advocator, enter
the file number and click
the search button.

Alternate 1.Invalid information entry

course of
action: 2.1If enter incorrect date error message display for the user

3. Go to step3 and fill again

Table 12: Use Case Documentation for View Appointment

34 | P a g e
 Use case Name View Information

Actor’s Client

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.

Actor action System response

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

Alternate No information yet to display

course of
action:
Table 13: use case documentation for view information table

35 | P a g e
 Name Search Client Information

Administrator, Civil, and Criminal law Officer, and civil and

Actor/s
criminal Judge
Description It allows Administrator and Registrar to search the required information in
the database.

Precondition They must login in to the home page.

Post condition Successfully display the required information.

Actor action System response

Basic course of
action: Step 1. Open the search Step2.The
system
Customer Information page.
Displays the search customer
Step3. Enter input and Click information page.
the Search Step4. The system displays the
selected user information.
Button.
Step5. The use case ends

Alternate Invalid information entry

course of
action: 1 If enter incorrect ID error message display for the user

2 Go to step3 and fill again

Table 14: Use case documentation for search customer information table

36 | P a g e
 Name Give Appointment

Actor/s Civil and criminal Judge

Description It allows judge to give appointments for client.

Precondition He/she must login in to the home page.

Post condition Judge successfully give appointment.

Actor action System response

Basic course of
action: Step1. Open the give Step2. The system
appointment page from the Displays the give appointment page.
menu. Step4.The system Displays success or
Step 3. Judge fills the form. failure.
Step5. The use case ends

Alternate A3. Invalid information entry

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

Table 15: Use case documentation for Give appointment table

37 | P a g e
 Name New case Registration

Actor’s Civil Law and Criminal Law Officer

Description It allows the Client to register case.

Precondition He or she must login in to the home page.

Post condition Successfully registered.

Basic course of Actor action System response

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

Alternate A3. Invalid information entered.

course of A4. The system displays an error message.
action:
A5. Go to step 3 to fill again

Table 16: Use case documentation for New case Registration table

38 | P a g e
 Name View Assigned Case

Actor Civil and criminal Judge.

Description It allows the judge to view the assigned case.

Precondition He/she must login in to the home page.

Post condition View the assigned case.

Actor action System response

Basic course of
action: Step 1. Open view assign case Step2. The system
page from the menu Displays the View assigned case page.
Step3. Enter the date and Judge Step4. The system displays an assigned
ID in the view assigned case page case or no assigned case.
form and click the view button. Step5. The use case ends

Alternate A3. Invalid information entry.

course of A4. The system displays an error message.
action:
A5. Go to step 3 to fill again

Table 17: Use case documentation for view assigned case table

39 | P a g e
 Use case Name Record decision

Actor/s Civil and criminal 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
Step2. The system Displays the
from the menu
Step3. Record the decision on Record Decision page.
the record page and click the Step4.The system display record
Save button.
successfully or failed.
Step5. The use case ends

Alternate A3.Invalid information entry.

course of action A4. The system displays error message.
A5. Go to step 3 to fill again

Table 18: Use case documentation for record decision table

40 | P a g e
 Use case Name View Decision

Actor/s Administrator and Advocator

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.

Actor action System response

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

Alternate A3.Invalid information entry.

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

Table 19: Use case documentation for View Decision table

41 | P a g e
 Use case Name Give Comment

Actor/s Client/Customers

Description It allows customer to give comment about court office.

Precondition He/she must know court office website.

Post condition give comments

Basic course of Actor action System response

action: Step1.Open the give Step2. The system Displays the give
comment page comment page.
Step3.Customer writes Step 4. The system Displays success or
Comment and click send failure.
button. Step 5. The use case ends

Table 20: Use Case Documentation for Give Comment table

 Security Login
Each user is required to login. The system shall allow people with assigned user names and passwords.
The system shall be designed to make it impossible for unauthorized people to login without valid
Usernames or password.
 Registration
The user must meet Office of the Clerk to register in the system. There is no online registration.

42 | P a g e
 3.2.3 Sequence diagram
A sequence diagram simply depicts interaction between objects in a sequential order i.e.
the order in which these interactions take place. We can also use the terms event diagrams or
Event scenarios to refer to a sequence diagram. Sequence diagrams describe how and in what
order the objects in a system function.

Figure 5: Sequence diagram for login

43 | P a g e
 Figure 6: Sequence diagram for new case registration

44 | P a g e
 Home Give Give
Judge Data
page Appointment Appointment
<<actor>> Base
<<UI>> <<UI>> <<controler>>

send give
login to the
appointment
system
request
click give
appointment
link Display
form

fill the form

click save
button send request check
again validity

if invalid
If
valid
Save()

Display saved appointment saved

appointment

Figure 7: Sequence diagram for Give Appointment

<<Actor> Home Page Logout

Logout Link Confirmation
<<UI>> controller

Login

Click Logout
button
Logout request

Redirect

Displays Login
page

Figure 8: Sequence diagram for Logout

45 | P a g e
 Judge Record
Main page Record decision
<<actor>> decision page validator Database
<<link>>

Login

click record
decision link

Displays record
decision
Fill form and
Click save
button

Check

Fill form

Failed to
record Valid user
Decision
recorded
successfully

Figure 9: Sequence diagram for recording decision

46 | P a g e
 Main- view view
Judge Data
form assigned case assigned case
<<actor>> base
<<UI>> <<UI>> <<controller>>

Login to
the system
Send request

Click see Display case

Assign form
Assigned case
link
Fill the form
Click show button
Send request
again
check
validity
If invalid
Show()
Show assigned If valid
Case successfully

show
assigned
case

Figure 10 : Sequence diagram for assigned case

47 | P a g e
 View
Administrator Home page view decision Data
Decision
<<actor>> <<UI>> <<controller>> base
<<UI>>

Login to
the system

click link send request

show decision

desplay a form
inter inputs to view
data and select form

check valid

if invalid
if valid
Show()
show decision
show decision
successfully

Figure 11: Sequence diagram for view decision

48 | P a g e
 Figure 12: Sequence diagram for view appointment

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

49 | P a g e
 Figure 13: Activity diagram for Login

50 | P a g e
 Figure 14: Activity diagram for Create Account
51 | P a g e
Figure 15: Activity diagram for Give Appointment

52 | P a g e
 Figure 16: Activity diagram to view client information

53 | P a g e
Figure 17: Activity diagram to new case registration

54 | P a g e
Figure 18: Activity diagram for Advocator registration

55 | P a g e
 Open home page

Click view appointment

Displays message

Figure 19: Activity diagram to view Appointment

3.2. Analysis level class diagram (conceptual modeling)

In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of
static structure diagram that describes the structure of a system by showing the system's classes,
Their attributes, operations (or methods), and the relationships among objects. The class diagram
is the main building block of object-oriented modeling. It is used for general conceptual
modeling of the structure of the application, and detailed modeling translating the models into
programming code. Class diagrams can also be used for data modeling. The classes in a class
diagram represent both the main elements, interactions in the application, and the classes to be
programmed. In the diagram, classes are represented with boxes that contain three
compartments: The top compartment contains the name of the class. It is printed in bold and
centered, and the first letter is capitalized. The middle compartment contains the attributes of the
class. They are left-aligned and the first letter is lowercase. The bottom compartment contains
the operations the class can execute. They are also left-aligned and the first letter is lowercase. In
the design of a system, several classes are identified and grouped in a class diagram that helps to
56 | P a g e
determine the static relations between them

Figure 20: Class diagram

57 | P a g e
 3.2.6 User Interface Prototyping
User interface prototyping is an excellent means of generating ideas about how the GUI can be
designed and it helps to evaluate quality of solution at early stage.

HOME ABOUT US CONTUCT US LOG IN

Figure 21: UI Prototype

Civil law Criminal law
Administrator
officer officer Judge page Customer ADVOCATOR
page
page page

Login Login Login Login Log in Log in

58 | P a g e Home Home Home Home Home

Home Create
account
Manage Delete New case New Case G ve View
Registration View appointment
Account Account Registration appo ntment
appointment
Update Advocator Advocator Record View
Generate Report
 3.2.7 Supplementary specifications
The Supplementary Specifications capture the system requirements that are not readily captured
in the use cases of the use-case model. Such requirements include: -
 Legal and regulatory requirements and application standards.
 Quality attributes of the system to be built, including usability, reliability,
performance, and supportability requirements.
 Other requirements such as operating systems and environments, compatibility
requirements, and design constraints.
The other Supplementary specifications are the rules. The rules is a principle or a policy in which
the proposed system operates accordingly. It deals with access control issue. Some of the rules
that we have included in this project are the following:
 Users must have a valid user name and password
 System manager create, delete and update account for other Actors.
 Only the manager is authorized to register and edit the information of employee.
 The storekeeper must know the item which is stored, borrowed and returned.
 The User should see the item before sending request.

59 | P a g e
 Chapter Four
System Design
4.1 Introduction
System design is the phase that bridges the gap between problem domain and the existing system
in a manageable way.
In this chapter we will transform the analysis model to design model. Until now we were in the
problem identification stages, now we will proceed to the first stages of the solution domain. The
purpose of design is to determine how to build the system and to obtain information needed to
drive the actual implementation of the system. The focus is particularly on the solution domain
rather than on the problem domain. System Design is the process of defining the architecture,
components, Modules, Interfaces, Deployment, and data for a system to satisfy the specified
requirements. Systems design is therefore the process of defining and developing systems to
satisfy specified requirements of the user.
4.2 Class type architecture
It is the concept of organizing software design in to layer/collection of classes or component that
satisfy the common purpose such as implementing the user interface or business logic of the
system that the users interact with the interfaces depending on their account level. These layers
are: User interface layer, controller/process layer, business/domain layer, persistence layer, and
System layer.
Collaboration within a layer is allowed. For example, UI objects can send messages to other UI
objects and business/domain objects can send messages to other business/domain objects.
Collaboration can also occur between layers connected by arrows. In Figure below, interface
classes may send messages to domain classes but not to persistence classes. Domain classes may
send messages to persistence classes, but not to interface classes . By restricting the flow of
messages to only one direction, for example, the domain classes don't rely on the user interface of the
system, implying that you can change the interface without affecting the underlying business logic.
All types of classes may interact with system classes. This is because our system layer
implements fundamental software features such as inter-process communication (IPC), a service
classes use to collaborate with classes on other computers, and audit logging, which classes use
to record critical

60 | P a g e
actions taken by the software. For example, if your user interface classes are running on a
personal computer (PC) and your domain classes are running on an EJB application server on
another machine, and then your interface classes will send messages to the domain classes via
the IPC service in the system layer. This service is often implemented via the use of middleware.

User Interface Layer

Process Layer

System Layer

Domain Layer

Persistence Layer

Data
Sources

Figure 22: Class Type Architecture

 User interface layer

This is the first application layer of the new system that contains window request of user name
and password which the entire page will be opened. And also incorporates classes, which enables
the user to interact with the system business functionalities.
In our project the following user interface classes are identified.
 Login UI class.

61 | P a g e
  Administrator UI.
 Client’s registration UI class.
 Registration UI.
 Controller/process layer
The process layer implements business logic that involves collaborating with several domain
classes or even other process classes.
 Business/Domain layer
This layer implements the concepts relevant business domain.
 Persistence layer
Persistence layers encapsulate the capability to store, retrieve, and delete objects/data
permanently without revealing details of the underlying storage technology in the system.
Often implement between object schema and database schema and there are various available to
us.
 System layer
System classes provide operating-system-specific functionality for our applications, isolating our
software from the operating system by wrapping OS-specific features, increasing the portability
of your application.
4.3 Class modeling
A class diagram in the UML is a type of static structure diagram that describes the structure of a
system by showing the systems classes, their attributes, operations (or methods), and the
relationships (including, inheritance, aggregation and association) among objects.
Attributes identifies the characteristics of a class while methods identify the behavior of it.
Relationships are the logical links between classes and can be in different flavors. UML
diagrams like activity diagram, sequence diagram can only give the sequence flow of the
application however class diagram is a bit different. It is the most popular UML diagram
in the coder community.
Class Notation
A class notation consists of three parts:
1. Class Name
The name of the class appears in the first partition.
2. Class Attributes
62 | P a g e
  Attributes are shown in the second partition.
 The attribute type is shown after the colon.
 Attributes map onto member variables (data members) in code.
3. Class Operations (Methods)
 Operations are shown in the third partition. They are services the class provides.
 The return type of a method is shown after the colon at the end of the method
signature.
 The return type of method parameters is shown after the colon following the
parameter name.
 Operations map onto class methods in code.

63 | P a g e
 Figure 23: Class modeling

64 | P a g e
 4.4 State chart modeling
The state chart diagrams are used to describe the change of an object through time. Based upon
events that occur, the state diagram shows how the object changes from start to finish. States are
represented as a rounded rectangle with the name of the state shown in the system. Connecting
states together are transitions. These represent the events that cause the object to change from
one state to another.
The guard clause of the label is again mutually exclusive and must resolve itself to be either true
or false. Actions represent tasks that run causing the transitions. Like activity diagrams, state
diagrams have one start and one end from at which the state transitions start and end
respectively. State diagrams show the change of an object over time and are useful when an
object exhibits interesting or unusual behavior such as that of a user interface component.

Figure 24: State chart diagram create account judge

65 | P a g e
 Figure 25: State chart diagram for create account

66 | P a g e
 Figure 26: State chart diagram for login

67 | P a g e
 Figure 27: State chart diagram for generating report

68 | P a g e
 Figure 28: State chart diagram for assigning case

69 | P a g e
 Figure 29: state chart diagram to view appointment
4.5 Collaboration Diagram
A collaboration diagram is used to show some data flows between objects and the interaction
caused between them.
A collaboration diagram is an interaction diagram that emphasizes the structural organization of
the objects that send and receive messages. A collaboration diagram shows a set of objects, links
among those objects, and messages sent and received by those objects. The objects are typically
named or anonymous instances of classes, but may also represent instances of other things, such
as collaboration, components, and nodes.

70 | P a g e
 Figure 30: Collaboration diagram for register client

71 | P a g e
 Figure 31: Collaboration diagram for login

72 | P a g e
 Figure 32: Collaboration diagram for generate report

73 | P a g e
 Figure 33: Collaboration diagram for register case

74 | P a g e
Figure 34: Collaboration diagram for create account

Figure 35: Collaboration diagram for Give Appointment

75 | P a g e
 4.6 Component Modeling
In this modeling components of the system will be wired showing that there is relation among
components, this in some extent shows which components or objects will be accessed by whom
Component diagrams are used in modeling the physical aspects of object-oriented systems that
are used for visualizing, specifying, and documenting component-based systems. Component
diagrams are essentially class diagrams that focus on a system's components that often used to
Model the static implementation view of a system

Figure 36: Component diagram

76 | P a g e
 4.7 Deployment modeling
Deployment modeling used to show the hardware of the system, the software that is installed in
the hardware and also the middleware that is used to connect the disparate machines to one and
other. It also shows how the software and the hardware components work together.
A UML deployment diagram is a diagram that shows the configuration of run time processing
nodes and the components that live on them. Deployment diagram is a kind of structure diagram
used in modeling the physical aspects of an object-oriented system. They are often be used to
model the static deployment view of a system (topology of the hardware).
The associations between nodes Represents a physical connection. The physical deployment
model provides a detailed model of the way components will be deployed across the system
infrastructure. It details network capabilities, server specifications, hardware requirements and
other information related to deploying the proposed system.

Figure 37: Deployment diagram

77 | P a g e
 4.8 Persistence Modeling /database design
Persistence modeling is used to communicate the design of the database, usually the data base to
both the users and the developers. It is also used to describe the persistence data aspect of the
system. Database design is the process of producing a detailed data model of a database. This
data model contains all the needed logical and physical design choices and physical storage
parameters needed to generate a design. The term database design could also be used to apply to
the overall process of designing, not just the base data structures, but also the forms and queries
used as part of the overall database application within the DBMS

Figure 38: Persistence Modeling Diagram

78 | P a g e
 Chapter Five
5.1 Conclusions
This project mainly focuses on the Web-Based Information management system for Sheka zone
1st instant court Office. It include basic function such as Case Registration, Generate report, view
information, record decision, giving appointment, view appointment, assign case to judge and
advocator etc.as stated in the various sections of the document.
So far we were intended in analyzing the existing system of the court case system up to
proposing our new system that solves the difficulties related to the existing system. Until now we
have been doing the documentation and we will do the implementation of the system. In the
documentation we have seen the introductory sections about the overall system we have also
done the detail analysis and the design of the system that we developed and will be implemented.
To say something on the existing system: it is running almost manually, wastage of time
specially at the time of new case registration, wastage of resource. By having this problems over
the existing system our aim was to build a new system that have greater functionality that
enhance effectiveness and efficiency related parameters on the system.
5.2 Recommendation
According to the scope of our project, the project team develops a web based system for Sheka
zone 1st instant court office. Because of the time constraint, we cannot do beyond to scope, but in
the future the team believes that this system can be fully operational by having enough time and
full information.
Neatly, the team would recommend that further work should be done on the system. Based on
the preceding information in our project, we believe that the following recommendation will help
the organization to improve their system more reliable and available as they want. The
organization should be interconnected with the zonal court Office to communicate online. Be
able to use the more acceptable and available system to internal as well as external system users.
It should be interesting to give full information to those who develop the system. It is better to
adapt and use software-based system operations (business process action) in each sub system of
the organization.

79 | P a g e
 References
1. http://en.wikipedia.org/wiki/Class diagram
2. http://www.smartdraw.com/resources/tutorials/uml-statechart-diagrams/
3. http://creately.com/blog/diagrams/uml-diagram-types-examples/
4. http://edutechwiki.unige.ch/en/User_interaction_and_user_interface_design
5. http://www.smartdraw.com/resources/tutorials/uml-statechart-diagrams/
6. http://creately.com/blog/diagrams/uml-diagram-types-examples/
7. http://edutechwiki.unige.ch/en/User_interaction_and_user_interface_design
8. http://www.codeproject.com/Tips/351122/
9. www.ambysoft.com/essays/classTypeArchitecture.html
10. https://www.visual-paradigm.com/guide/uml-unified-modeling-language/uml-class-diagram-
tutorial/
11. https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-component-
diagram/
12. https://www. /visual-

80 | P a g e