DEPARTMENT OF COMPUTER SCIENCE

PROJECT TITLE:- CASE FLOW MANAGEMENT SYSTEM

IN CASE OF OROMIA SUPREME COURT
 Outline
1. Background of the project

2. Requirement Analysis

3. System Model

4. System Design

5. Implementation

6. Conclusion and recommendation are the main outline of top

chapters in this presentation.
 1. Background of the project

• The Supreme Court of OROMIA states is the largest region in Ethiopia as

comprising of other 10 regions courts.

• Supreme Court of Oromia has 3 standing benches.

• In each year about more than 1 million dockets added to courts. b/se of

this.

• There is an issues to improve the services given to Litigants.

 Background of the project…
• As the great British William E.Gladstone said in nineteenth century,

“Justice delayed is justice denied“.

• Delay reduction has been one of the primaries focuses of twentieth-

century court reform efforts.

• To reduce and avoid delay, American courts have developed a set of

principle and techniques since the 1970s that we refer to as Case

flow management.[1]

• In Oromia, to improve the service there is an initiative that trying to

introduce case flow management system.

 Statement of the Problem, and justification
• Paper-based working activities face many challenges.

• It decreases the quality of court in judicial and reduces customer

satisfaction in services delivery.

• Currently, In Oromia, there is a desktop-based application to control

information about litigant.

• The system running on outdated software and not supporting new version
windows.

• The system does not distribute cases each user. Not role based
 Objective and Scop of the project
General objectives:

• To develop and implement Case Flow Management system (CFMS).

Specific Objectives:

• To provide the flow of court information smooth communication and

assigned case between the court’s users.

Scope of the project:-

• Focuses on functionalities such as Case registration, add appointment,

Update appointment, Case Status, case Decision and assigned case b/n
user based on their role.
 System Development Methodology

• The nature of the project recommended the agile system development. why

agile?

• The agile methodology gives the need to develop a system based on the requirements

of the users,

• it provides face-to-face conversation between the developer and the clients

• It provides a breakdown of a project into manageable units, where the team can focus

on high-quality development, testing, and collaboration.

• Active participation with clients to be aware of every detail and step of the
 Feasibility of the Project
• The project is legally and technically feasible as well as economically

justifiable. They can be many reasons for this,

• Economic Feasibility:- Additional cost such as purchasing new hardware or

Software.(Cost benefits analysis)

• Operational Feasibility:-New system is simple and reduce jobs from employee

• Technical Feasibility:-The technical elements in the system will be confirmed

and verified.

• Time Feasibility:- a project will fail if it is not completed on time

 2. Requirement analysis

• The requirement is mandatory steps to review their operations.

• Requirements must accepted by the client.

• Requirement’s engineering includes two main activities.

• Requirement specification: specification of the system that the client

understand

• Requirements analysis- an analysis model that the developer can

unambiguously interpret[3]
 Current System, and Existing System Problems.
• .In Ethiopia, Court case management system was established in
2002 by CIDA (Canada foundation support).

• Customization done by Cyber soft Company PLC for Federal

Supreme Court of Ethiopia.

• Supreme Court of Oromia also customize from Federal Courts.

• The system is not web-based

• The system is running with outdated software and even not

support new windows application such as win-10,win-11.
Requirements Gathering, Methods, and Business
Rule
• Document Analysis-
• Creating an AS-IS process document.

• Observation-:
• Done by observing users and identify a process flow.

• Business rule:-
• The graphical representation of a company’s workflow.

• Prototyping:-
• Modern method for gathering requirements
 Proposed System, Function, and non-
Requirement
• The proposed CFM System are comprehensively accepted as a
court tool to control cases from filing to disposal.

Function requirements:-

• Describes how the system will work in terms of its inputs. the behavior,
and outputs.

Non-functional requirement:-

• Defines the major system attributes such as security, reliability,

performance, maintainability, scalability, and usability.
 3. System model
• A successful software development organization can satisfy their
customer by providing them with quality software that solves the main
problem domain.

• Models help the analyst to understand the functionality of the system.

They are used to communicate with the customers [2].

• A use-case model is a model of how different types of court users

interact with the system to solve a problem.

• Use case diagram : It describes the functionality of the system from

 System model…
• Activity Diagram:- Can be described as a flowchart and shows control
flows from activities to activities.

• Object model- Represent in UML with class diagram, describes the

structure of the system in terms of objects, attributes, associations, and
operations [3].

• Class Model:-It describes the system in terms of objects,

attributes, and operation with their inheritance, aggregation,
and association.

• Dynamic Modeling:-is defining sequence of object communicating

 4. System design

• It’s process of transforming user requirements into suitable form.

• This helped programmer in software coding and implementation.

• Design is a highly creative stage in software development.

• Where the designer plans how the system should meet the customer’s

needs to make the system effective and efficient.

Current, and Proposed software Architecture
• The Current SA is high development cost and deployment cost.

• The proposed system flow MVC architecture that is separation concern.

• System Decomposition - It shows the system into manageable parts.

• Persistent Data Modeling - Every communication and activity in the

system generates different data.
 Current, and Proposed software Architecture..

Access Control and Security:-

• From an organizational perspective, security has to be considered at

three levels.

• Infrastructure security:- all system and networks infrastructure.

• Application security: security of individual app or group related.

• Operational security: secure operation and use of the org. system.

Current, and Proposed software Architecture…

Deployment:

• Deployment diagram, nodes are represented by boxes containing

components icons.

• Nodes can be stereotyped to denote physical devices or execution

environment.
 5. Implementation

• Unidirectional one-to-one association:- only one side navigation

is possible. Eg: One judge disposal one Case.

• Bidirectional one-to-association:- each entity has a relationship field or

property that refers to the other entity. Eg: One Case disposal by one

Judges.

• A one-to-many association: commonly happens when the primary

key of one table becomes a foreign key in another table.

 Implementation…
• Example:-one litigant can have many cases.

• Many-to-many associations: A many- to- many association

between two classes. Eg: Judge and Case detail is many- to-

many association in this document.

 Testing, Validation, and System Maintenance

• System Testing- Is tested with different real data collected

from SCO to meet the functional requirements which are
identified in the requirement analysis.

• Validation is done by find any kind of error that existed in

the entire system development and correct them.

• System maintenance criteria deal with the difficulty of

changing the system such as adding new functionality, revising
existing functionality, portability of the system.
 Conclusion and recommendation
Conclusion:
 The system administrator configuration and add lookup data.
 The system will allow multiple court users to login with its role

based from dedicated computer.

 The system also enables selected courts users to add new Case,

edit, view, and update case information about appointment reasons,

appointment condition and appointment date in a database.

 The chief judges assigning case to judges and make decisions.
 Recommendation
• If this system is applied the following parts of the system are
likely added for future work:
 The case flow management system to included online case and
application with payment system.
 The case flow management system to included high court and
district courts
• Adding SMS notification, e-filing system and email notification
Thanks