ARBAMINCH INSTITUTE OF TECHNOLOGY (AMIT)

(ARBAMINCHUNIVERSITY)

Court case management system

S.NO NAME ID No.

1 Tadesse Samuel RAMIT/1900/09
2 Zelalem Zewde RAMIT/2560/09
3 Tebkew Yirsaw RAMIT/1904/09
4 Mohammed Ibrahim RAMIT/2267/09
5 Mekuanint Tarko RAMIT/1849/09
6 Addisu Fisseha RAMIT/1742/09

Advisor’s Name &Signature Examiners Name & Signature

Mr. Mohammed Ali Dr. Azath Hussain

--------------- ------------------

A senior project (proposal)

Submitted to Department of Computer Science and IT, Faculty of Computing and

Software Engineering, AMIT, Arba Minch University, in Partial fulfillment for the
requirement of the Degree of Bachelor Science in Information Technology(IT)

Arba Minch, Ethiopia

Jan, 2021

Arbaminch, Ethiopia
March, 2010
 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. We
grateful to our advisors Mohamed 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. At last but not the least we want to thank our teacher and friends
who appreciated us for our work and motivated us.

i
 Abstract
Access to justice has become an important issue in many justice systems around the world.
Increasingly, technology is seen as a potential facilitator of access to justice, particularly in terms
of improving justice sector efficiency. The major functionalities covered in court works are
registration, indexing and follow up of cases. Case management is the key success factor in judicial
system. Systematic, efficient and organized case management system provides comprehensive
information for courts to guarantee unbiased decision and transparency information system to
hinder the misuse of power or corruption, case postponement and delays in decision making. It
also reflects the good image in judiciary.
This project is about Court Case Management System (CCMS) which is developed to make the
functional areas in Judicial Service more efficiency and effective. One of the main intension of
this project is to control and allow complete registration of all court cases and tracking of case
current status.
The methodology I used for the project development is the Agile Development Methodology. This
methodology was used because the project is needed to deal directly with the clients and users so
that we the developers will know what they really want and how they want the system to function
from the feedback they give after each iteration.

ii
 Contents
Acknowledgements ........................................................................................................................................................ i
Abstract.......................................................................................................................................................................... ii
List of figures........................................................................................................................................................ vi
List of tables ........................................................................................................................................................ vii
1. Introduction ...........................................................................................................................................................1
1.1 Background of Organization ................................................................................................................................2
1.1.1 Vision ...........................................................................................................................................................2
1.1.2 Mission .........................................................................................................................................................2
1.2 Background of the project....................................................................................................................................2
1.3 Team Composition...............................................................................................................................................3
1.4 Statement of the Problem .....................................................................................................................................4
1.5 Objective of the project .......................................................................................................................................5
1.5.1 General objective ..........................................................................................................................................5
1.5.2 Specific Objective .........................................................................................................................................5
1.6 Feasibility ............................................................................................................................................................6
1.6.1 Operational feasibility ..................................................................................................................................6
1.6.2 Technical feasibility ......................................................................................................................................6
1.6.3 Economic feasibility: - ..................................................................................................................................6
1.6.4 Behavioral /Political feasibility ....................................................................................................................6
1.6.5 Schedule feasibility .......................................................................................................................................6
➢ Tangible Cost ...............................................................................................................................................6
➢ Intangible Cost .............................................................................................................................................7
System design ............................................................................................................................................................9
1.7 Scope and Significance of the Project ..........................................................................................................9
1.7.1 Significance of the project ..........................................................................................................................10
1.8 Target Beneficiaries of the project .....................................................................................................................10
1.9 Methodology ..................................................................................................................................................11
1.9.1 Data collection ...........................................................................................................................................11
1.9.2 Fact finding techniques...............................................................................................................................11
1.9.3 System analysis and design .........................................................................................................................11
➢ Development Tools .....................................................................................................................................12
1.9.5 Limitation of the project .............................................................................................................................12
Chapter Two ................................................................................................................................................................13
Description of the Existing System .........................................................................................................................13
2.1 Introduction of Existing System ........................................................................................................................13
2.2 Player’s in the existing system. ..................................................................................................................14

iii
2.4 Business rules ........................................................................................................................................................15
2.5 Report generated in the existing system .....................................................................................................15
2.6 Forms and other documents of the existing systems ..................................................................................16
2.7 Bottlenecks of the existing system .............................................................................................................17
2.7.1 Performance (Response time) ................................................................................................................17
2.7.2 Input (Inaccurate/redundant/flexible) and Output (Inaccurate)..............................................................17
2.7.3 Security and Controls.............................................................................................................................17
2.7.4 Efficiency...............................................................................................................................................17
2.7.5Economic .....................................................................................................................................................18
2.8 Practices to be preserved ............................................................................................................................18
2.9 Proposed solution for the new system that address problems of the existing system.................................18
2.10. Requirements of the Proposed System .......................................................................................................18
2.10.1 Functional requirements ....................................................................................................................18
2.10.2 Non-functional requirements .............................................................................................................19
Chapter Three ..............................................................................................................................................................20
System Analysis ......................................................................................................................................................20
3.1 Introduction ................................................................................................................................................20
3.2 System Requirement Specifications (SRS) ................................................................................................20
3.2.1 Use case diagrams..................................................................................................................................20
3.2.2 Use case documentation.........................................................................................................................23
3.2.3 Sequence diagram .................................................................................................................................37
3.2.4 Activity Diagram ...................................................................................................................................42
3.2.5 Analysis level class diagram (conceptual modeling) .............................................................................48
3.2.6 User Interface Prototyping .....................................................................................................................50
3.2.7 Supplementary specifications ................................................................................................................51
Chapter Four: System Design ......................................................................................................................................52
4.1 Introduction ...............................................................................................................................................52
4.2 Class type architecture ..............................................................................................................................52
4.3 Class modeling ..................................................................................................................................................55
4.4 State chart modeling ..........................................................................................................................................57
4.5 Collaboration Modeling .....................................................................................................................................64
4.6 Component Modeling ........................................................................................................................................67
4.7 Deployment modeling .......................................................................................................................................69
4.8 User Interface design .........................................................................................................................................70
Chapter Five: Implementation and Testing................................................................................................................77
5.1 Introduction .......................................................................................................................................................77
5.2 Final Testing of the system ................................................................................................................................77

iv
 5.3 Hardware software acquisitions .........................................................................................................................81
5.4 User manual preparation ....................................................................................................................................81
5.5 Training .............................................................................................................................................................82
5.6 Installation Process ............................................................................................................................................82
5.7 Start-up strategy .................................................................................................................................................82
Chapter Six: Conclusions and Recommandation .........................................................................................................83
6.1 Conclusions .......................................................................................................................................................83
6.2 Recommandations..............................................................................................................................................83
Appendix .................................................................................................................................................................84
1.10 References .......................................................................................................................................................86

v
 List of figures

FIGURE 1:SOFTWARE DEVELOPMENT LIFE CYCLE FOR CCMS ........................................................................................9

FIGURE 2: APPOINTMENT FORM ...................................................................................................................................16
FIGURE 3: USE CASE DIAGRAM ....................................................................................................................................23
FIGURE 4: SEQUENCE DIAGRAM FOR LOGIN ..................................................................................................................37
FIGURE 5: SEQUENCE DIAGRAM FOR NEW CASE REGISTRATION....................................................................................38
FIGURE 6: SEQUENCE DIAGRAM FOR GIVE APPOINTMENT ............................................................................................39
FIGURE 7: SEQUENCE DIAGRAM FOR LOGOUT ..............................................................................................................40
FIGURE 8: SEQUENCE DIAGRAM FOR RECORDING DECISION .........................................................................................41
FIGURE 9: SEQUENCE DIAGRAM FOR VIEW APPOINTMENT ............................................................................................42
FIGURE 10: ACTIVITY DIAGRAM FOR LOGIN .................................................................................................................43
FIGURE 11: ACTIVITY DIAGRAM FOR CREATE ACCOUNT .............................................................................................44
FIGURE 12: ACTIVITY DIAGRAM FOR GIVE APPOINTMENT ...........................................................................................45
FIGURE 13: ACTIVITY DIAGRAM TO VIEW CLIENT INFO ................................................................................................46
FIGURE 14: ACTIVITY DIAGRAM TO VIEW APPOINTMENT .............................................................................................47
FIGURE 15: CLASS DIAGRAM ........................................................................................................................................49
FIGURE 16: UI PROTOTYPE...........................................................................................................................................50
FIGURE 17: CLASS TYPE ARCHITECTURE .....................................................................................................................54
FIGURE 18: CLASS MODELING ......................................................................................................................................57
FIGURE 19: STATE CHART DIAGRAM CREATE ACCOUNT JUDGE ....................................................................................58
FIGURE 20: STATE CHART DIAGRAM FOR CREATE ACCOUNT ........................................................................................59
FIGURE 21: STATE CHART DIAGRAM FOR LOGIN ...........................................................................................................60
FIGURE 22: STATE CHART DIAGRAM FOR GENERATING REPORT ...................................................................................61
FIGURE 23: STATE CHART DIAGRAM FOR ASSIGNING CASE ...........................................................................................62
FIGURE 24: STATE CHART DIAGRAM TO VIEW APPOINTMENT ........................................................................................63
FIGURE 25: COLLABORATION DIAGRAM FOR REGISTER CLIENT ....................................................................................64
FIGURE 26: COLLABORATION DIAGRAM FOR LOGIN .....................................................................................................65
FIGURE 27: COLLABORATION DIAGRAM FOR GENERATE REPORT .................................................................................66
FIGURE 28: COLLABORATION DIAGRAM FOR REGISTER CASE .......................................................................................67
FIGURE 29: COMPONENT DIAGRAM ..............................................................................................................................68
FIGURE 30: DEPLOYMENT DIAGRAM ............................................................................................................................70
FIGURE 31: UI FOR ADMINISTRATOR ............................................................................................................................71
FIGURE 32: UI FOR JUDGE ............................................................................................................................................72
FIGURE 33: UI FOR COURT REGISTRAR .........................................................................................................................73
FIGURE 34: UI FOR LOGIN.............................................................................................................................................74
FIGURE 35 UI FOR MANAGE ACCOUNT .........................................................................................................................75
FIGURE 36 UI FOR REGISTER ADVOCATOR ...................................................................................................................76

vi
 List of tables

TABLE 1:TEAM COMPOSITION ........................................................................................................................................3

TABLE 2:TANGIBLE COST...............................................................................................................................................7
TABLE 3:COST OF PROJECTS ...........................................................................................................................................7
TABLE 4:PROJECT SCHEDULE .........................................................................................................................................8
TABLE 5: DEVELOPMENT TOOLS ..................................................................................................................................12
TABLE 6: USE CASE DOCUMENTATION FOR LOGIN TABLE ...........................................................................................23
TABLE 7:USE CASE DOCUMENTATION FOR LOGOUT TABLE ...........................................................................................24
TABLE 8: USE CASE DOCUMENTATION FOR GENERATE REPORT TABLE .........................................................................25
TABLE 9: USE CASE DOCUMENTATION FOR CREATE ACCOUNT TABLE ..........................................................................26
TABLE 10: USE CASE DOCUMENTATION FOR UPDATE ACCOUNT TABLE ......................................................................27
TABLE 11: USE CASE DOCUMENTATION FOR UPDATE ACCOUNT TABLE ......................................................................28
TABLE 12: USE CASE DOCUMENTATION FOR VIEW INFORMATION TABLE ......................................................................29
TABLE 13: USE CASE DOCUMENTATION FOR SEARCH CUSTOMER INFORMATION TABLE ...............................................30
TABLE 14: USE CASE DOCUMENTATION FOR GIVE APPOINTMENT TABLE .....................................................................31
TABLE 15: USE CASE DOCUMENTATION FOR GIVE APPOINTMENT TABLE .....................................................................32
TABLE 16: USE CASE DOCUMENTATION FOR VIEW ASSIGNED CASE TABLE ...................................................................33
TABLE 17: USE CASE DOCUMENTATION FOR RECORD DECISION TABLE ........................................................................34
TABLE 18: USE CASE DOCUMENTATION FOR VIEW DECISION TABLE............................................................................35
TABLE 19: USE CASE DOCUMENTATION FOR GIVE COMMENT TABLE ..........................................................................36
TABLE 20: APPENDIX ...................................................................................................................................................85

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

1|P a g e
 1.1 Background of Organization

The Judiciary is the system of courts of justice in a country, the arm of government charged
with the responsibility to administer justice. The Judiciary is independent from other
government functions and provides a forum for the just resolution of disputes in order to
preserve the rule of law and to protect the rights and liberties guaranteed by the Constitution of
Ethiopia. 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. The court can now electronically manage a case from the
filing state and assigning cases to judges.

1.1.1 Vision
A single, transformed and independent judicial system that guarantees access to justice for all.

1.1.2 Mission
To provide support to the Judiciary to ensure effective and efficient court administration
services.

1.2 Background of the project

The system based on the court case management system that improves the manual data
processing. Court case 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. 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.
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
2|P a g e
 following things will be the result after the implementation of the new proposed system we are
going to develop.

1.3 Team Composition

Project Title Court Case Management System(CCMS)

Prepared By S.No. Name ID. No. Email/Mobile Responsibility
1. Tadesse Samuel RAMIT/ 1900/09 0926395631 Leader
2. Zelalem zewde RAMIT/ 2560/09 0963994968 Designer
3. Tebkew Yirsaw RAMIT/ 1904/09 0921911645 Data collector
4. Mekuanint Tarko RAMIT/1849/09 0915628263 Programmer
5. Mohammed Ibrahim RAMIT/2267/09 0964925773 Programmer
6. Addisu Fisseha RAMIT/1742/09 0929465755 Documenter

Date 12, December, 2019

Advisor Mr. Mohammed Ali
Table 1:Team composition

3|P a g e
 1.4 Statement of the Problem
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 time, files may be destroyed by natural disasters like fire , flood,
difficulty of retrieving needed document timely, recording examination, cross examination and
reexamination may difficult while collecting evidence from witness and difficulty of giving
appointments case postponement for customers.

4|P a g e
 1.5 Objective of the project
1.5.1 General objective
The aim of this project is to develop and implement the web-based Court Case Management
System (CCMS) to control and allow complete registration of all court case which are related
to the court by the domain user thus registrar, who can register, update, delete, and search case
and create report. The flow of information provides communication and notification between
the courts and public.

1.5.2 Specific Objective

➢ To store all data of the accuser and accused person into the database, the system “Event”
and “Scheduling” is to determine new case arrivals, session appointments, case deadline
and the judge who will head the case, 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 create an administrator page that will show statistical analysis.

5|P a g e
 1.6 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
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.6.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.6.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.6.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.6.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.

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

➢ 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
6|P a g e
following table lists the different miscellanies costs that have been used in the process of the
development of the system.

# Item Name Quantity Cost

1 Paper 250 50 birrs
2 Flash 16GB 1 250birr
3 Document print 20 40 birrs

Table 2:Tangible Cost

➢ Intangible Cost
Intangible cost 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

➢ Cost of projects

Item Price /Birr

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

Table 3:Cost of projects

➢ Cost Breakdown
Beside tangible and intangible costs, we breakdown cost of system development into two: one-
time 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.

7|P a g e
 ❖ 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.

PROJECT SCHEDULE

S.No Phases 1st quarter 2nd 3rd quarter 4th quarter 5th quarter
quarter

Dec5- Jan20- Feb7- March12- May18-

Dec13/201 Jan28/2 March7/2020 May15/202 June6/2020
9 0220 0
1 Project
Proposal
2 Requirement
Analysis and
Modeling
3 Design
4 Implementat
ion
5 Installation&
Project
Closure

Table 4:project Schedule

8|P a g e
 Project Proposal Requirement
analysis

Installation and
document System design

Implementation
and system testing
Figure
Figure 1:Software development life cycle for CCMS

1.7 Scope and Significance of the Project

This project will illustrate how open source tools can be used for the development of web-
based applications thereby making the academia aware of the benefits of using cheaper tools.
This project in future will allow other students to review the application and to think of new
ways in which some components of the application will be improved or think of ways of adding
new components to meet more needs.
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 any customer that wants to open new case and assigned cases to judges, View
assigned cases that law officers are assign to Judges, register appointment dates that
judges give for customer.
➢ Generate reports.
➢ Make the system high secure, efficient and effective
➢ To avoiding the data redundancy of the system.
➢ Search the files in short times.
➢ View assigned cases that law officers are assign to Judges
➢ Register any customer that wants to open new case and assigned cases to judges.
➢ Register Any Advocator with full address that wants to give service for customer
➢ Register appointment dates that judges give for customer.
➢ Generate reports.
➢ Make the system high secure, efficient and effective
➢ To avoiding the data redundancy of the system.
➢ Search the files in short times.
➢ Update employee’s information.

9|P a g e
 ➢ Record examination, cross examination and reexamination in the database while
collecting evidence from witness.
➢ Accept comment that customers are writing for court offices.

1.7.1 Significance of the project

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

➢ The system will be used by the registrar for case registration and data processing (data
storage and data retrieval), which involves creation, modification and updating
information through user interface.

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

1.8 Target Beneficiaries of the project

❖ Judiciary
❖ Society
Project team:
❖ Will acquire experience and knowledge
Will acquire satisfaction

10 | P a g e
 1.9 Methodology

1.9.1 Data collection

For the development of the proposed system we will uses different data sources such as
documents, interviewing, and observation.

1.9.2 Fact finding techniques

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.
C) Document Analysis:-It is used to understand how the current system is working. We used
this method to know all about current sale case registration, function and overall of their work
in short and brief.

1.9.3 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 build, 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.

11 | P a g e
 ➢ 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.

➢ Development Tools

Activities Tools/ Programs

Client side coding HTML
Client side scripting JAVASCRIPT
Platform WINDOWS
Database server MYSQL
Web server XAMMP
Server-side scripting PHP
Browsers Google Chrome, Mozilla Firefox, Safari and explorer
Editors SUBLIME,NOETPAD++
Documentation MICROSOFT WORD 7/10
Diagram EDRAWMAX
Table 5: Development Tools
1.9.5 Limitation of the project
➢ Following decision by customer online is not allowed.

12 | P a g e
 Chapter Two

Description of the Existing System

2.1 Introduction of 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.

13 | P a g e
 2.2 Player’s in the existing system.
➢ 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.3 Major functions/activities in the existing system

➢ Case registration.
➢ Giving appointment.
➢ Assigning case to Jude.
➢ Decision making.
➢ Case hearing.

14 | P a g e
 2.4 Business rules
There are some rules and constraint to prevent any violation during process.
➢ The client must be come to the court on the appointment day.
➢ 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.
➢ 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.5 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.

15 | P a g e
 2.6 Forms and other documents of the existing systems

Figure 2: Appointment Form

16 | P a g e
 Figure 2.1 Appointment Form

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

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

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

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

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

17 | P a g e
 2.7.5Economic
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.

2.8 Practices to be preserved

➢ New case registration form.
➢ Generating report.

2.9 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.10. 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.10.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 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.

18 | P a g e
 ➢ 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.)

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

19 | P a g e
 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

Use Case Diagram captures the system's functionality and requirements by using actors and use
cases. Use Cases model the services, tasks, function that a system needs to perform. Use cases
represent high-level functionalities and how a user will handle the system. Use-cases are the core
concepts of Unified Modeling language modeling. A use case diagram at its simplest is a
representation of a user's interaction with the system that shows the relationship between the user
and the different use cases in which the user is involved. The following use cases have been
identified from the system specification

20 | P a g e
 ➢ 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.

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

➢ Admin
➢ Registrar
➢ Judge
➢ Client

21 | P a g e
 Court Case Management System
View Creare Update
Decision Account Account

<<Extend>>
<<Extend>> <<Extend>>

Manage Account

Search Client
Information

View Dicision
Admi

Assign case

Registr
Generat report
ar

New case
Registration
<<Include>>

Login
Judge

Logout

Client
View assined case

Record Dicision

Give Appointment

View
Appointment

Give comment

22 | P a g e
 Figure 3: Use Case Diagram
3.2.2 Use case documentation
Use case name Login
Actor’s Administrator, Registrar, Client 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 Step 1: The users want to login into the system.
action: Step 2: The system displays Login form.
Step 3: The user fills his/her username and password.
Step 4: click login button.
Step5: The system verifies the username and password.
Step 6: The system displays the appropriate home page.
Step 7: The use case ends
Alternate course The username/password is invalid.
of action: 1. The system displays error message.
2. The system continues at step 2 to fill user name and password again.

Table 6: Use Case Documentation for Login table

23 | P a g e
 Use case name Logout
Actors Registrar, Admin, Judge, and client.
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

24 | P a g e
 Use case Name Generate Report

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.

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

Step3. Select link he/she want to generate a report.

Step4. The system displays the selected report.

Step5. The use case ends

Table 8: Use case documentation for generate report table

25 | P a g e
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.

Basic course of Step 1. Open the manage account page.

action:
Step2. The system Displays the Manage account page.

Step3. Open create account link.

Step4. The system display create account page.

Step5. Administrator fill create account form and click create button.

Step6. The system displays 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

26 | P a g e
 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 displays successfully updated account.

Basic course of Step 1. Open the manage account page.

action:
Step2. The system Displays the Manage account page.

Step3. Open update account link.

Step4. The system display update account page.

Step5. Administrator fill update account form and click create button.
Step6. The system displays 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

27 | P a g e
 Name View Appointment

Actor/s Administrator, Judge, 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 Step 1. Open the view appointment form from menu.
action
Step2. The system Displays the view appointment page.

Step 3. Enter appointment date and click search button.

Step4.The system Displays selected information.

Step5. The use case ends

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 11: Use Case Documentation for Update account table

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

Basic course of Step 1. Open the view information page.

action
Step2. The system Displays the View information page.

Step3. Select one from lists link.

Step4. The system display information.

Step 5 The use case ends

Alternate No information yet to display

course of
action:

Table 12: use case documentation for view information table

29 | P a g e
 Name Search Client Information

Actor/s Administrator and Registrar

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.

Basic course of Step 1. Open the search Customer Information page.

action:
Step2. The system Displays the search customer information page.

Step3. Enter input and Click Search Button.

Step4. The system displays the selected user information.

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 13: Use case documentation for search customer information table

30 | P a g e
 Name Give Appointment

Actor/s 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.

Basic course of Step 1. Open the give appointment page from menu.
action:
Step2. The system Displays the give appointment page.

Step 3. Judge fills the form.

Step4.The system Displays success or fail.

Step5. The use case ends

Alternate Invalid information entry

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

2 Go to step3 and fill again

Table 14: Use case documentation for Give appointment table

31 | P a g e
 Name New case Registration

Actor’s Client

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 Step 1. Open the new case registration link from menu.
action:
Step2. The system Displays the Registration form.

Step3. Fill the new case registration form and click Register button.

Step4. The system displays registration successfully or failed.

Step5. The use case ends

Alternate Invalid information entry.

course of
action: 1 The system displays error message.

2 Go to step 3 to fill again

Table 15: Use case documentation for Give appointment table

32 | P a g e
 Name View Assigned Case

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

Basic course of Step 1: Open view assign case page from menu
action:
Step2: The system Displays the View assigned case page.

Step3: Enter the date and Judge ID in the view assigned case page form and
click view button.

Step 4: The system displays assign case or no assigned case.

Step 5: The use case ends

Alternate A3 Invalid information entry.

course of
action: 3.1 The system displays error message.

3.2. Go to step 3 to fill again

Table 16: Use case documentation for view assigned case table

33 | P a g e
 Use 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 Step 1. Open the record page from menu

action:
Step2. The system Displays the Record Decision page.

Step3. Record the decision in the record page and click Save button.

Step 4: The system display record successfully or failed.

Step 5: The use case ends

Invalid information entry.

Alternate
course of action 1 The system displays error message.

2.Go to step 3 to fill again

Table 17: Use case documentation for record decision table

34 | P a g e
 Use case 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 Step 1: Open the view decision page from menu
action:
Step2: The system Displays the View decision page.

Step 3: Enter input to view decision and click search button.

Step4: the system display list of cases.

Step5: Select cases and click view button.

Step6: The system displays selected case information in details.

Step7: The use case ends

Alternate Invalid information entry.

course of
action: 1 The system displays error message.

2.Go to step 3 to fill again

Table 18: Use case documentation for View Decision table

35 | P a g e
 Use case Name Give Comment

Actor/s Client

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 Step 1. Open the give comment page

action:
Step2. The system Displays the give comment page

Step 3. Customer write comment and click send button.

Step4.The system Displays success or fail.

Step5. The use case ends

Table 19: 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 logon
without valid usernames or password.

➢ Registration
36 | P a g e
The user must meet Office of the Clerk to register in the system. There is no online registration.
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.
Home page
<<Actor>> login page Login
Database
<<Link>> vallidator

Open Home
page

Click login page link

Displays login
form

Enter username
and password

Click login
button
Check

Incorrect un
Valid user
and pw

Displays
successfully
message

Figure 4: Sequence diagram for login

37 | P a g e
 New case Case
<<Actor>> Main page registration Database
reistration form
<<controler>>

Login to system
Click
registration
form
Displays
Registration
form
Fill form click
register button Check validity
If valid
Invalid

Display
message
successfully
saved

Figure 5: Sequence diagram for new case registration

38 | P a g e
 Figure 6: Sequence diagram for Give Appointment

39 | P a g e
 <<Actor> Home Page Logout
Logout Link Confirmation
<<UI>> controller

Login

Click Logout
button
Logout request

Redirect
Displays Login
page

Figure 7: Sequence diagram for Logout

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

Login

click record
decision link

Displays record
decision
Fill form and
Click save
button

Check

Fill form

Failed to
Valid user
record
Decision
recorded
successfully

Figure 8: Sequence diagram for recording decision

41 | P a g e
 Figure 9: Sequence diagram for view appointment

3.2.4 Activity Diagram

An activity diagram portrays the control flow from a start point to a finish point showing the
various decision paths that exist while the activity is being executed. We can depict both
sequential processing and concurrent processing of activities using an activity diagram.

42 | P a g e
 Login Form

Enter uname &

pass

Check validity

Display Error
invaild
message

valid

Displays main
page

Figure 10: Activity diagram for Login

43 | P a g e
 Open
manage

Open create
account page

Fill form &

click create
button

Display error
message

Created
successfully

Figure 11: Activity diagram for Create Account

44 | P a g e
 Open home
page

Open give
appointment
page

Fill in the
form and

Fill form again

Error
Correct
message

Incorrect

Displays
successfuly
saved

Figure 12: Activity diagram for Give Appointment

45 | P a g e
 Open client
info page

Enter case_Id
then click
search button

Error
Invalid
message

Valid

Figure 13: Activity diagram to view client info

46 | P a g e
 Open home
page

Click view
appointment

Displays
message

Figure 14: Activity diagram to view Appointment

47 | P a g e
 3.2.5 Analysis level class diagram (conceptual modeling)
Another technique that is applied to support the conceptual analysis effort is the use of Class
diagrams.

The UML Class Diagram is used to support both the analysis and the design phase. Classes are an
important aspect of object-oriented software.
Implementation issues are dealt with during the design phase as we refine our class diagrams
during our development process. Developing at the conceptual level means to keep a perspective
that is language and platform neutral and focus on the essential pieces needed to make our software
system work.

CRC is collection of standard index cards that have been divided in to three sections.

A class: represents a collection of similar objects. The name of the class appears across the top
of the card.

A responsibility: is something that a class knows or does. Responsibilities are shown on the left-
hand column of a CRC card.

A collaborator: is another class that a class interacts with to fulfill its responsibilities. A class will
have a responsibility to fulfill but will not have enough information to do it. When this happens, it
has to collaborate with other classes to get the job done. The collaborators of a class are shown in
the right-hand column of a CRC card.

48 | P a g e
 Figure 15: Class diagram

49 | 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 page

Judge page Client page

Administrator Registrar
page page

Login
Login Login
Login

Create
Account
Home Home Home Home
Update
Account
Manage Case View Assigned View
Account Registration case Appointment
View Decision
Generat Lawyer Give
Report Registration Appointment

Delete
View client Account
Record
info Generate Decision
Report

View
Comment
View
Appointment

Figure 16: UI Prototype

50 | P a g e
 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.

51 | 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 4.1 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
52 | 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.

53 | P a g e
 User Interface Layer

Process Layer

System Layer

Domain Layer

Persistence Layer

Data
Sources

Figure 17: Class Type Architecture

54 | P a g e
 ➢ 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.
➢ 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

55 | P a g e
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
➢ 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.

56 | P a g e
 Figure 18: Class modeling

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

57 | P a g e
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 19: State chart diagram create account judge

58 | P a g e
 Figure 20: State chart diagram for create account

59 | P a g e
 Figure 21: State chart diagram for login

60 | P a g e
 Figure 22: State chart diagram for generating report

61 | P a g e
 Figure 23: State chart diagram for assigning case

62 | P a g e
 Figure 24: state chart diagram to view appointment

63 | P a g e
 4.5 Collaboration Modeling
A collaboration diagram resembles a flowchart that portrays the roles, functionality and behavior of individual objects
as well as the overall operation of the system in real time. Objects are shown as rectangles with naming labels inside.
These labels are preceded by colons and may be underlined. The relationships between the objects are shown as lines
connecting the rectangles. The messages between objects are shown as arrows connecting the relevant rectangles along
with labels that define the message sequencing.
Collaboration diagrams are best suited to the portrayal of simple interactions among relatively small numbers of
objects.

Figure 25: Collaboration diagram for register client

64 | P a g e
 Figure 26: Collaboration diagram for login

65 | P a g e
 Figure 27: Collaboration diagram for generate report

66 | P a g e
 Figure 28: Collaboration diagram for register case

4.6 Component Modeling

The component diagram shows the relationship between software components, their dependencies,
communication, location and other conditions.
A component represents a modular part of a system that encapsulates its contents and whose
manifestation is replaceable within its environment.
In UML 2, a component is drawn as a rectangle with optional compartments stacked vertically. A
high-level, abstracted view of a component in UML 2 can be modeled as:
1. A rectangle with the component's name
2. A rectangle with the component icon
67 | P a g e
3. A rectangle with the stereotype text and/or icon

Figure 29: Component diagram

68 | P a g e
 4.7 Deployment modeling
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.

69 | P a g e
 Figure 30: Deployment diagram

4.8 User Interface design

User interface is a visual platform for users which support them, and also enabling them to interact with the
system. The interface is the crucial aspect which needs more attention.

70 | P a g e
 Figure 31: UI for administrator

71 | P a g e
 Figure 32: UI for Judge

72 | P a g e
 Figure 33: UI for court registrar

73 | P a g e
 Figure 34: UI for login

74 | P a g e
 Figure 35 UI for Manage account

75 | P a g e
 Figure 36 UI for Register advocator

76 | P a g e
 Chapter Five: Implementation and Testing

5.1 Introduction
The implementation phase is the most crucial phase in which it transforms the design and analysis
of the system into a tangible system by writing the code to the system to be developed and make
it operational and applicable by testing and debugging the functionalities that are done. This phase
involves the construction of the actual project result. during this phase that the project becomes
visible to outsiders, to whom it may appear that the project has just begun. This makes the
implementation stage more essential step to develop the required system. So, it is the most vital
and necessary stage in achieving a successful system and in giving the users confidence that the
new system will work and be effective by testing the system that is already implemented. In this
phase, the production system is installed, initial user training is completed, user documentation is
delivered, and the post implementation review meeting is held. When this phase is completed, the
application is in steady state production. Once the system is in steady-state production, it is
reviewed to ensure that we met all of the goals in the project plan for a satisfactory result. The
result of this phase consists of source code, together with documentation to make the code more
readable. This is what we call software implementation. The purpose of these activities is to
convert the final physical system specification into working model with reliable software and
hardware, document the work that has been done, and provide help for current and future users
and take care of the system.

5.2 Final Testing of the system

Testing the system is means as it ensured that the intended system generated the required output
given the necessary input. Also, to determine if the system is able to complete actions in relation
to its functional and non-functional requirement. During the system test and implementation, the
system as a whole is tested to ensure that all its components work well together otherwise the
project cannot be said to be complete. There are various web application testing methods.
➢ Functionality Testing: This involves validating if an application conforms to its
specifications and correctly performs all its required functions.
➢ Usability Testing: This involves verifying how the application is easy to use.

77 | P a g e
 ➢ Performance Testing: This testing involves verifying the server response time and
throughput under various load conditions.
➢ Unit Testing: The primary goal of unit testing is to take the smallest piece of testable code
or software in an application/system, isolate it from the remainder of the code and
determine if it behaves as it should.
➢ Integration Testing: Integration testing is a form of testing in which software components,
hardware components or both are combines and tested to evaluate the interaction between
them.
Testing can be done either black box or white box methodologies.

Black box testing: To test our system, the tester may use black box testing, if he/she has not
enough time to check internal modules or codes. By looking only input /output or user interface,
the tester can test our systems functionalities without looking the internal code. We used this
testing technique for the following reasons: -

➢ This testing type is more effective on larger units of code

➢ Tester needs no knowledge of implementation, including specific programming languages
➢ Tester and programmer are independent of each other
➢ Tests are done from a user's point of view
White box testing: In this type of testing, skilled man in different programming languages tries
to test the logic of our system. If the person who tests the system is not skilled, it is difficult to
understand our systems functionality. If any failures occur while testing the system in all of the
above testing methods, the team will take immediate correction where this fault occurred before
jumping to next work. So, that it will meet the goal.

Sample php code for login

<?php

//Start session

session_start();

include'connection.php';

if(isset($_POST['login'])){

78 | P a g e
 $errors=array( );

$uname=" ";

$pword=" ";

if (empty($uname)) {

$errors[]='you forgot to enter username';

else{

$uname=$_POST['uname'];

if (empty($pword)) {

$errors[ ]='you forgot to enter password';

else{

$pword=$_POST['pword'];

if (empty($errors)){ // If everything is OK!

$qry="select * from account where username='".$uname."' and password='".$pword ."' and

status='on'";

$results=mysqli_query ($conn, $qry)or die(mysqli_error( ));

$count=mysqli_num_rows($results);

// Check the result:

if ($count==1) {

// Fetch the record:

79 | P a g e
 $row=mysqli_fetch_array($results,MYSQLI_ASSOC);

// Return true and the record:

$_SESSION['un']=$row['User_id'];

$_SESSION['username']=$row['username'];

$_SESSION['fname']=$row['Fname'];

$_SESSION['lname']=$row['Lname'];

$user=$row['role'];

if($user=="admin"){

header('location:startbootstrap-sb-admin-2-gh-pages/AdminPage.php');}

//echo "admin";

else if($user=="law_officer"){

header('location:registrar/registrar.php');

//echo "keeper";

else if($user=="judge"){

header('location:judge/judge.php');

else if($user=="customer"){

header('location:customer/customer.php');

else { // Not a match!

echo'<p style="color:red;text-align:center;">The username and password entered do not

match.</p>';

80 | P a g e
 }

} // End of empty($errors) IF.

// End of check_login( ) function.

?>

5.3 Hardware software acquisitions

For the proper functioning of the system the following hardware and software are required
❖ Hardware’s

➢ Computer

➢ Hard Disk

➢ Server

➢ Network devices

❖ Software’s

➢ Browsers

➢ MSQL server
➢ Windows operating system

5.4 User manual preparation

Since the system is web based, everything important for the users will be explained and
implemented while giving short training when the system is deployed. There is no need of
preparing full user manual because it is only hosted on a single machine that is server. So anyone
who can access the internet can also access the system easily within the given permission by the
system administrator.

81 | P a g e
 5.5 Training
Training manuals serve the important purpose of providing a consistent way to communicate
instructions to employees about how to perform essential functions of their jobs by using the
system. They benefit ICT officer responsible for educating workers about the system as well as
employees themselves, by providing content and structure necessary to train new hires and to
manage the performance of incumbent workers. To be effective, training manuals is based on
functionalities and instructional objectives. Information should be provided about the processes
and procedures employees are required to follow as well as tasks that form the basis of the jobs
they are charged with performing.

5.6 Installation Process

➢ Buying a domain name from a company with its corresponding IP address for the server.
➢ Hosting the database server
➢ Finally, available internet connection for users.

5.7 Start-up strategy

Once the system is hosted, the startup strategy is the system home page. If you have an account
(username/password) click login button to login into your system else if you are new user you can
create your own account in case of you are client.

82 | P a g e
 Chapter Six: Conclusions and Recommandation

6.1 Conclusions
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 mainly 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 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.

6.2 Recommandations
The main objectives of Project have been achieved we feel more additions can be made to the this
Project, like online payement. We would like to recommend that the system is open for all
interested groups or individuals who wish to add new functionalities on the system especially
online payment. Next, the team would recommend that further work should be done on the system
in order to make the system fully functional like official website.

83 | P a g e
 Appendix
Symbol/Abréviation Description

CCMS Court Case Management System

DB Database

SD Sequence Diagram

UC Use Case

UI User Interface

UML Unified Modeling Language

SRS System Requimpent Specifications

Actor

Use Case

Message line extend from the lifeline, Entity

Attribute relationship
Starting point of activity/state diagram

Ending point of activity/state diagram

Dependency line

Return message extend from the lifeline of

one object
Decision

Note

Activity

84 | P a g e
 Database

Database

Activation

Table 20: Appendix

85 | P a g e
 1.10 References
1. B., L., 2002. Courts of the future’ Law and Information Technology. p. 225–238.
2. Beal, V., 2017. Entity-Relationship Diagram (model). [Online] Available at:
http://www.webopedia.com/TERM/E/entity_relationship_diagram.html [Accessed 10 May 2017].
[3]. B., L., 2002.Courts of the future’ Law and Information Technology. p. 225–238.
[4].Beal, V., 2017. Entity-Relationship Diagram (model). [Online] Available at:
http://www.webopedia.com/TERM/E/entity_relationship_diagram.html [Accessed 10 jan 2020].
[5.]https://www.geeksforgeeks.org/unified-modeling-language-uml-sequence-
diagrams/[Accessed 20 Jan 2020].
[6].http://en.wikipedia.org/wiki/Class_diagram
[7].http://www.smartdraw.com/resources/tutorials/uml-statechart-diagrams/
[8].http://creately.com/blog/diagrams/uml-diagram-types-examples/
[9].http://edutechwiki.unige.ch/en/User_interaction_and_user_interface_design
[10].http://www.codeproject.com/Tips/351122/
[11].www.ambysoft.com/essays/classTypeArchitecture.html
[12].https://www.visual-paradigm.com/guide/uml-unified-modeling-language/uml-class-
diagram-tutorial/
[13].https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-
component-diagram/
[14].https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-
deployment-diagram/

86 | P a g e