COLLEGE OF

DEPARTMENT OF INFORMATION TECHNOLOGY

INDUSTRIAL PROJECT-I

PROJECT TITLE:. Web based court information management system

Group members

Name Id number

1. ASEBE ESUBALEW ------------------------------------ ITK/P/310/05

2. ASNAKCH NIGUSSIE-----------------------------------ITK/P/311/05
3. ATALE TAMENE------------------------------------ITK/P/312/05
4. BAPEO NANGE ------------------------------------ ITK/314/05

SUBMITTED TO: - Information Technology Department

August 2016

Debre Berhan, Ethiopia

Contents
Chapter One................................................................................................................................................................ 7
1. Introduction.............................................................................................................................................................7
1.1 Background of the organization.........................................................................................................................7
1.2. Background of the project................................................................................................................................7
1.3 Statement of the problem.................................................................................................................................8
1.4. Objective...........................................................................................................................................................9
1.4.1. General objective.......................................................................................................................................9
1. 4.2. Specific Objective......................................................................................................................................9
1.5. Methodology..................................................................................................................................................10
1.5.1 Data collection..........................................................................................................................................10
1.5.2 System analysis and design.......................................................................................................................10
1.5.3 System Development Tools......................................................................................................................11
1.6 Scope and Limitation of the Project.................................................................................................................12
1.6.1 Scope........................................................................................................................................................12
1.6.2 Limitation of the project...........................................................................................................................13
1.7 Significance of the project...............................................................................................................................13
1.7.1 Benefits for court......................................................................................................................................13
1.7.2 Benefits for society...................................................................................................................................13
1. 8. Feasibility.......................................................................................................................................................14
1.8.1 Economic feasibility..................................................................................................................................14
1.8.2 Technical feasibility...................................................................................................................................16
1.8.3 Time feasibility..........................................................................................................................................16
1.8.4 Operational feasibility...............................................................................................................................16
1.9 Task breakdown and deliverables....................................................................................................................16
1.10 Communication plan......................................................................................................................................17
1.1 Time Schedule...........................................................................................................................................17
Chapter Two..............................................................................................................................................................18
Description of the existing system.............................................................................................................................18
2.1 Introduction.....................................................................................................................................................18
2.2 Existing System................................................................................................................................................18
2.2.1 Existing System Description......................................................................................................................18
 2.2.2 Why describe the existing system.............................................................................................................19
2.2.3 .Problems of the existing system..............................................................................................................20
2.2.4 Alternative options to address the problems of existing system..............................................................20
2.3. Supplementary Requirements........................................................................................................................20
2.3.1. Business Rule...........................................................................................................................................20
2.4 The New Proposed System..............................................................................................................................21
2.4.1 Software Requirement Specifications (SRS................................................................................................22
Chapter Three............................................................................................................................................................24
Analysis deliverables of new system..........................................................................................................................24
3.1 Introduction.........................................................................................................................................................24
3.2 use case diagram.............................................................................................................................................24
3.3 System Use case diagram................................................................................................................................25
3.3.1 Use Case Documentation..........................................................................................................................27
3.4 Analysis level of class diagram.........................................................................................................................36
3.5 Sequence diagram...........................................................................................................................................39
3.6 Activity diagram...............................................................................................................................................43
3.7 Conceptual modeling using class diagram.......................................................................................................52
3.8 Essential User Interface Prototyping................................................................................................................53
3.8.1 User Interface Prototyping as Flow Chart Diagram...................................................................................53
3.9 Change cases...................................................................................................................................................54
Chapter 4................................................................................................................................................................... 55
New system design....................................................................................................................................................55
4.1 Introduction.....................................................................................................................................................55
4.2 Design goals.....................................................................................................................................................55
4.3 Current software architecture.........................................................................................................................56
4.3.1 Architecture of the System.......................................................................................................................56
4.3.2 Proposed software architecture...............................................................................................................56
4.4.4 Subsystem decomposition........................................................................................................................57
4.4 Class Diagram...................................................................................................................................................57
4.5 Persistence modeling for object oriented database.......................................................................................59
4.6 Component Diagram........................................................................................................................................61
 4.7 Deployment diagram...................................................................................................................................62
Chapter Five..............................................................................................................................................................63
Conclusions and recommendations.......................................................................................................................63
5.1 Conclusions:.................................................................................................................................................63
5 .2 Recommendations:.....................................................................................................................................63
Reference.................................................................................................................................................................. 64

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

Name signature Date

1. ASEBE ESUBALEW _____________ _____________
2. ASNKECH NIGUSSIE _____________ _____________
3. ATALE TAMENE _____________ _____________
4. BAPEO NANGE _____________ _____________
This is to certify that I have read this project and that in my opinion it is fully adequate, in
scope and quality, as a project for the degree of Bachelor of Science.

Advisor Name: Signature Date

Sofonias. ………………… …....................

Examiner’s Name Signature Date

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

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

DEBER BERHAN UNIVERSITY COLLEGE OF COMPUTING

DEPARTMENT OF INFORMATION TECHNOLOGY
 Acknowledgement
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 Ato Sofoneys for his continuous 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. Again we
want to thank the Manger of debre birhan town court office Mr. Habetamu and who gives us enough
information about the court system and we thank other employers of that court who gives us extra
information. 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.
 Abstract
The purpose of this project is to full fill the requirement of bachelor degree of Information System as final
year project in order to graduate.
Now days, using computers to simplify tedious manual work is significance. Because using computer
gives many benefits like speed, accuracy, storage capacity, security, flexibility, cost reduction and
minimizing tedious manual work. debre birhan court office was limited on manual works. This has a
limitation for customers wasting large amount of time in front of the office to register and high
consumption of resources.
To overcome this problem we are proposing the new web base system for debre birhan Court
Information management System. Customer can find advocators by using online system. So that no needs
waste the time and resource to find advocators
This system is developed based on two-tier approach with step by step from planning, analysis,
design, and then implementation. With the Unified Modeling Language (UML) diagram such as use case,
activity diagram and sequence diagram is drawn. The system flow and the actor are drawn to understand
how the system works does and who the actors that interact the system are.
The programming language used to develop this project is PHP and HTML .Database
application is MySQL.

Apendex

DBCIMS…………………………………………. debre birhan court information management system

CRC…………………………………………….class responsibility collaboration
DBCIMSCA …………………………………… debre birhan court information management system
create account
DBCIMSCL…………………………………… debre birhan.. court information management system
login
UC…………………………………………… Use Case
 Chapter One

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

1.1 Background of the organization

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

1.2. Background of the project

The system based on the court information management system that improves the manual data processing.
Court Information Management System is document management system or handling of data, dataflow
system, court fee, appointment and also concern with a customers’ comment. There are two major types of
cases. Those are civil law and criminal law. Each of them contains their own sub branches. In order to
execute those cases some process takes place.
As we visited the work place of; how the court information management system takes place; we have seen
some problems in data processing DebreBirhan town and handling. During the process there may be
many difficulties of manual processing of files/data. Not only this but also giving comment for one court
may be difficult because of distance. This means there is no online giving comment service before for the
court found on the distance.
Now we are going to develop software that can solve problems of data processing, data handling, give
appointment ,assign case ,registering case and view assigned case etc. we can achieve our aim by using
hardware (pc) and software (programming language). The main purpose of doing this project is that to
save person’s file from damage, store files forever, secure files that must be secured, reduce costs and
time. There will be data communication from one office to the other. There will be many advantages after
the end of our project. The following things will be the result after the implementation of the new
proposed system we are going to develop.
• protect the data from damaging

• prevent the data from the thieves, robbers

• Save the data in secure way if needed

• Giving appointment for customer in simple way

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

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

• Giving comment online for court Administrator is possible

1.3 Statement of the problem

Court information management system of DebreBirhan town does on both criminal and civil case type. As
mentioned above these major types contain so many sub branches. Criminal case is initiated when crime is
committed, then investigation held to collect information and evidence about what is happened to
determine who committed the crime. After that the accused is charged with the crime and taken into
custody.

Based on evidence, then the judge determine whether he/she guilty or not guilty. At the end the decision is
presented. This process is done manually. Also Civil court cases arise where an individual or a business
believe their rights have been attacked in some way. All these processes and documentation system is
takes place manually. By this system the following problems are identified.
 • Difficulty of storing the documents neatly

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

• Files may be fade because of long life

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

• Giving comment may be difficult for customers on distance place

• Difficulty of data store in secure way.

• Difficulty of retrieving needed document timely..

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

• Difficult to giving appointments for customers.

• Difficult to evaluate every judge decisions.

• Difficult to assign cases to judges.

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

1. 4.2. Specific Objective

The specific of this project is to develop software that controls court information Management system.
This system includes Specific Objective.
• Analyze the existing system and design better system for the organization

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

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

• To develop a secured Data base syste

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

• To develop the court information management system

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

1.5.1 Data collection

Data collection was one of the important tasks to analyze how activities done in existing system and
developed the new system. Data for developing this system obtained  fromdifferent sources.
A)InterviewTechniques:is one of the primary ways analysts gather information on information systems.
During interviewing the team will gather facts, opinions, and speculation and observe body language,
emotions, and other signs of what people want and how they assess current systems. Interviews are good
tools for collecting rich and detailed information.
B) Observation: Observing current system users is a more direct way of seeing how an existing system
works. By watching what people do or by obtaining relatively objective measures of how people behave in
work situation, the team can have firsthand and accurate appreciation of what they really do or how they
do it observing work flow at the work place. Though this technique is cost effective we hoped to achieve
the target.

1.5.2 System analysis and design

The team plan to use the Object Oriented Software Development Methodology (OOSD) for the
development of the system among the different methodologies. Because it is better way to construct,
manage and assemble objects that are implemented in our system. We used OOSD because of the
following important features:
• Increase reusability: - the object oriented provides opportunities for reuse through the concepts of
inheritance, polymorphism, encapsulation and modularity.
• Increased extensibility: -when you to need to add new feature to the system you only need to
make changes in one part of the applicable class.
• Improved quality: - quality of our system must be on time, on budget and meet our exceeded the
expectation of the users of our system, improved quality comes from increased participation of
users in the system development.
 • Financial benefits: - reusability, extensibility and improved quality are all the financial benefits,
because they led to the business benefits of the object- oriented from the point of view of the users,
the real benefits are we can built, system faster and cheaper.
• Reduced maintenance cost: - Software organizations currently spend significant resources
maintain operating system so the object oriented development methods helps us to overcome this
problem.
• Managed complexity:-The object-oriented methods solve software complexity in the following
way, design your software the expectation that it will need to be modified and being able to
respond quickly when your environment changed.
Object oriented design methodology has two phases:-
Object Oriented Analysis (OOA): During this phase the team will look at the problem domain and with
the aim of producing a conceptual model of the information that exists in the area which will be analyzed.
And this model the functions of the system (use case modeling), identifying the business objects, organize
the objects and also the relationship between them and finally model the behavior of the objects.
Object Oriented Design (OOD): During this phase the model interactions and behaviors that support the
use case scenario, and finally update object model to reflect the implementation environment. And also
transforms the conceptual model produced in object-oriented analysis to take account of the constraints
imposed to our system format, so that we will use this phase to refine the use case model to reflect the
implementation environment.
State chart diagram, component diagram and deployment diagram to model our system.

1.5.3 System Development Tools

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

• Secondary storage device

• flash disk(8 GB)

• Memory :2GB RAM

• Hard disk:300GB

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

• mysql server 2005 – to develop database application

• Microsoft office word 2010 for documentation.

• Microsoft Visio – to design Gantt chart

• Edraw Max-– todesignUse case Diagram, design Sequence Diagram, design Activity
Diagramand. Class Diagram, Deploy Diagram and other diagram

• Programming Language: - PHP and HTML

1.6 Scope and Limitation of the Project

1.6.1 Scope
Scope of the system identifies the problem to be studied, analyzed, designed, constructed and
ultimately improved. It is specifically concerned with what problem the proposed system addresses.
The project can cover the following activities:-
• Register finished cases decisions and the eviden Register finished cases decisions and
the evidence of the witness.

• View assigned cases that law officers are assign to Judges

• Register any 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.

• ce of the witness.

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

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

collecting evidence from witness.

• Accept comment that customers are writing for court offices.

1.6.2 Limitation of the project

 time
 cost
 resource
 experience

1.7 Significance of the project

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

1.7.1 Benefits for court

• Save time.

• It reduces the work load for workers.

• Decrease Error in filing the client document.

• Employers will have confidence on handling data.

• Searching documents when it is needed is easy.

• They can secure active files and dead file as they want.
 • Information about court can be accessed any time from any place based on given privilege.

• Data communication is possible

• To know the appointment date is very easy.

• Calculating court fee depending on cases become simple

1.7.2 Benefits for society

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

• Save their time

• Reduce the complexity.

• Can save their financial budget.

• Customers will give their comment online without going there.

1. 8. Feasibility
Feasibility study is 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.8.1. Economic Feasibility
1.8.2. Technical Feasibility
1.8.3. Time Feasibility
1.8.4. Operational feasibility

1.8.1 Economic feasibility:-

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

A. Software cost

Item Price
Microsoft window 7 30
MSVisio2010 35
Microsoft word 2010 30
SQL Server 2005 25
Microsoft power point 2007 30
Macromedia Dreamweaver 30
Visual basic studio 30
Total 210

Table 1.1 software cost

B. Hardware costs
Item Quantity Unit price Total
PC 1 12000 12000
Flash disk 1 120 120
Other material --- ---- 300
Total 12,420

Table 1.2 hardware cost

• So the first year total cost can be calculated like this:-

Total cost=hardware cost +software cost =12420 +210=12,630

Tangible benefits
Benefits Price
failure reduction 4,500
Cost reduction 10,000
Service Value 2,500
Total benefit 17,000

Table 1.3 tangible benefits

Net cost benefit

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

Total benefits Total cost Net benefit

17,000 12,630 4,370

Table 1.4 net cost benefit

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

1.8.2 Technical feasibility

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

1.8.3 Time feasibility

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

1.8.4 Operational feasibility

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

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

3. Design-in this stage that we will make the layout that shows how the new system will do at its
implementation stage. These are user interface, sequence diagram, etc.
4. implementation-it is the last stage that we will run and test the new system according to the layout
in the design phase and requirements specified in the analysis stage.
NO NAME ROLE
1 AsebeEsubalew In All activity
2 AsnakechNigussie In All activity
3 AtaleTamene In All activity

Table 1.5 Task Breakdown

1.10 Communication plan

Communication plan describes the schedule of group member or the time of communication plan to
develop project. The group member communicates four days in each week. While the member meets on
specified time at least communicate for 3 hours.
1.1 Time Schedule
ID Task Name Start Finish Duration

1 Proposal 10/08/2016 15/08/201 1 week

6
2 Documentation 16/08/2016 03/09/201 2 week
6
3 Design 03/09/2016 13/11/201 2 month
 6
4 Implementation 13/11/2016 05/02/201 3 month
7
5 Presentation 19/07/2017 20/07/201 2 days
7

Chapter Two

Description of the existing system

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

2.2 Existing System

2.2.1 Existing System Description
In Debrebirhantown has providing many services. But the development team concentrates to Court
information management system. That how to hold data or file. So this description contains two major
cases. Those are civil case and criminal case including their sub branches according to our scope.
Civil case proceeding is case among or between two individuals. Types of civil case are family issue,
property and succession. Since civil case takes place between two individuals; the accuser opens the case
to the court. The court registered the case. This is done by law officer or registrar office. The law officer
verifies the case. In this case or during verification; the case may be accepted or rejected. If the case
accepted the law officer receive court fee. The amount of the court fee depends on the case type. Then
he/she register court fee on the paper. After that the database administrator records the amount of the court
fee into the database including plaintiff details. The judges give appointment to accuser. Then the law
officer write the summon for the accuser. The accuser sends summon to the accused person. On the day of
appointed the law officer collects the case and give to the judge on manually. All information record on
paper 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 give appointment on the other days. The appointment date is recorded on
paper. The process repeated in the manner starting from hearing to rendering decision.
The criminal case is the same process like civil case what makes it different is that it can be conducted
between state and individuals. Public prosecutor investigates, collect information and evidence and so on.
The summon send to the accused when the accused is present on the appointment he/she can defense the
case. In both civil and criminal case all information, detail of accuser and accused as well as advocator
detail and also their words registered on the paper.
If the customers want to appeal, the law officer gives the appeal. There is limitation date to ask appeal
after decision made by judges. Then if one asks appeal, the hard copy of all his/her document including
words of witnesses given to him/her within a given time.
The other is if customer wants to give his/her comment for employees or for organization; he/she
writes and put it in comment box. In order to give comment for them one must go there. On the holding of
data; the file saved in two ways active files and dead files. Those files handle manually. Also searching
document is takes place manually. If the law officers want to assigned case, they search by case card in the
shelf. this is very difficult to find the accuser document.

2.2.2 Why describe the existing system

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

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

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

• To identify problem of the existing system.

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

2.2.3 .Problems of the existing system

Problems are undesirable situations that hinder the organization from fully achieving its purpose, goals or
objectives.
Performance
The performance of the existing system does not provide fast response time because it is difficult to access data
from the stored document. And also, it is slow /time and energy consuming.
Security and Controls
Every record of document in the existing in Debrebirhan Court Information Management System is stored in the
manual way, so, it is difficult to control and secure these manual records, since it doesn’t have any authentication
and authorization system.
Economic
• Due to the operation that is done by the hand most of the activities are causes to high consumption of
resources like papers, man power, time, pen etc. This makes the existing system costs are too high.
Data storage problem
• Data are not easily accessible due to place in different location.

• Difficult to change and edit.

• Data redundancy that leads to inconsistency

2.2.4 Alternative options to address the problems of existing system

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

2.3. Supplementary Requirements

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

2.4 The New Proposed System

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

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

• Speed:-regarding on the speed the system will generate output within short times.
 • Reliability:-the system is reliable by analyzing each business rule set by the organization

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

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

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

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

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

2.4.1 Software Requirement Specifications (SRS)

2.4.1.1 Functional Requirements

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

2.4.1.2 Non-functional requirements

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

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

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

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

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

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

Analysis deliverables of new system

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

3.2 use case diagram

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

3.3 System Use case diagram

Use Case represents interaction between the user and the system.

The following use cases have been identified from the system specification

• Login
 • Manage account

• Generate report

• New case registration

• Advocator registration

• View appointment

• Give appointment

• Record decision

• Search Customer Information

• View assigned case

• View decision

• Give comment

• View information

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

• :Actors

• Administrator
 • Criminal Law Officer

• Civil Law Officer

• Judge

• Customer

Fig 3.3 System use case

3.3.1 Use Case Documentation

Use case Name Login

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

Alternate course A3. The username/password is invalid.

of action: 3.1. The system displays error message.
3.2. The system continues at step 3 to fill user name and password again.

Table 3.3.1 Use Case Documentation for Login

Table 3.3.2 Use case documentation for generate report

Use case Name Generate Report

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

Basic course of Actor action System response

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

Step3. Select link he/she want to Step4. The system displays the selected report.
generate a report. Step5. The use case ends
Use case Name Create Account
Actor/s Administrator
Description It allows administrator to create for new user accounts.
Precondition He/she must login in to the home page.
Post condition The system successfully created account.
Basic course of Actor action System response
action: Step 1. Open the manage Step2. The system
account page. Displays the
Manage account page.
Step3. Open create account Step4. The system display create account page.
link. Step6. The system display successfully created
message.
Step 7. The use case end.
Step5. Administrator fill
create account form and click
create button.
Alternate A5. Invalid information entry
course of
5.1. If enter incorrect ID error message display for the user
action:
5.2. Go to step3 and fill again

Table 3.3.3 Use case documentation for Create account

Use case Name Update Account

Actor/s Administrator
Description It allows administrator to update user accounts.
Precondition He/she must login in to the home page.
Post condition The system display successfully updated account.
Basic course of Actor action System response
action: Step 1. Open the manage Step2. The system
account page. Displays the
Manage account page.
Step3. Open update account Step4. The system display update account page.
link. Step6. The system display successfully updated
message.
 Step 7. The use case end.
Step5. Administrator fill update
account form and click create
button.
Alternate A5. Invalid information entry
course of
5.1. If enter incorrect ID error message display for the user
action:
5.2. Go to step3 and fill again

Table 3.3.4 Use Case Documentation for Update account

Name View Appointment

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

Alternate 1.Invalid information entry

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

Table 3.3.5 Use Case Documentation for View Appointment

Use case Name View Information

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

Basic course of Actor action System response

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

Alternate • Unknown the website.

course of
action:

Table 3.3.6 Use case documentation for view information

Name Search Customer Information

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

Table 3.3.7 Use case documentation for search customer information

Name Give Appointment

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

Alternate A3.Invalid information entry

course of
3.1 If enter incorrect date error message display for the user
action:
3.2 Go to step3 and fill again
Table 3.3.8 Use case documentation for Give appointment

Name New case Registration

Actor/s Civil Law and criminal Law Officer
Description It allows the law officer to register new case.
Precondition he or she must login in to the home page.
Post condition Successfully registered.
.
Basic course of Actor action System response
action: Step 1. Open the new case Step2. The system
registration link from menu. Displays the
Step3. Fill the new case Registration form.
registration form and click Step4. The system displays registration successfully
Register button. or failed.
Step5. The use case ends

Alternate A3. Invalid information entry.

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

Table 3.3.9 Use case documentation for new case registration

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

Table 3.3.10 Use case documentation for advocator registration

Name View Assigned Case

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

Alternate A3 Invalid information entry.

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

Table 3.3.11 Use case documentation for view assigned case

Name Record decision

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

Basic course of Actor action System response

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

Table 3.3.12 Use case documentation for record decision

Name View Decision

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

Basic course of Actor action System response

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

Alternate A3 Invalid information entry.

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

Table 3.3.13 Use case documentation for View Decision

Name Give Comment

Actor/s Customers
Description It allows customer to give comment about court office.
 Precondition He/she must know court office website.
Post condition give comments
Basic course of Actor action System response
action: Step 1. Open the give comment Step2. The system
page Displays the give comment page.
Step 3. Customer write comment Step4.The system
and click send button. Displays success or fail.
Step5. The use case ends

Table 3.3.14 Use Case Documentation for Give Comment

3.4 Analysis level of class diagram

A Class Responsibility Collaborator (CRC) model is a collection of standard index Cards that have
been divided into three sections; this is class name, responsibility and collaborator. A class represents a
collection of similar objects, a responsibility is something that a class knows or does, and a collaborator is
another class that a class interacts with to fulfill its responsibilities. [5] Those can be shown in the
following table.

Class name

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

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

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

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

Name

Age

Sex Law officer form

Address

Phone no

Case type

Case id

Court fee

Register()

Reset()

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

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

Give Appointment

Case ID Law officer form

Date

Judge ID

Submit()

Search

CaseID Registration
Form
Date

JudgeID

Search()

Comment
Name

Address

Administrator
Date
Form
Comment

Submit()
Table 3.4 Analysis level of class diagram

3.5 Sequence diagram

A sequence diagram in a unified modeling language (UML) is a kind of interaction diagram that
shows how processes operate with one another and in what order. It is a construct of a Message Sequence
Chart. A sequence diagram shows object interactions arranged in time sequence

Fig 3.5.1 Sequence diagram for login

 Fi
g 3.5.2 Sequence diagram for new case registration
Fig 3.5.3 Sequence diagram for Give Appointment
Fig 3.5.4 Sequence diagram for View Information
3.6 Activity diagram
An Activity diagram is similar to a flowchart to represent the flow from one activity to another activity.
Activity diagrams and State chart diagrams are related. While a State chart diagram focuses attention on
an object undergoing a process (or on a process as an object), an Activity diagram focuses on the flow of
activities involved in a single process. The Activity diagram shows how these single-process activities
depend on one another.

Fig3.6.1 Activity diagram for login

Fig 3.6.2 Activity Diagram for Advocator Registration
Fig 3.6.3Activity Diagram for View Appointment
Fig 3.6.6 Activity Diagram for View Information
Fig 3.6.7 Activity Diagram for Search Customer Information
Fig 3.6.8 Activity Diagram for Create Account
Fig 3.6.9 Activity Diagram for Give Comment
3.7 Conceptual modeling using class diagram

Fig 3.7 Conceptual modeling Class Diagram

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

3.8.1 User Interface Prototyping as Flow Chart Diagram

Fig 3.8. UI Flow Chart Diagram

3.9 Change cases

Change case will used to describe potential modifications requirements to the system.
There are many cases that change the content of the project. From these:-
• Missing activities: -Where there the important activities missed in each project development
phase and the developing team latterly understood them, they should include them.
• Important comments: - When crucial comments are raised from the advisor, teachers and
examiners that should be included and excluded the developing team assess the project again.
• Lack of resources: - If there is scarcity of resources occurred to develop many system activities,
the developing team also restructured the contents of the project.
 Chapter 4

New system design

4.1 Introduction
This chapter mainly concerned with the design part of web based Court Information management System.
In order to make the implementation easy the design is very important.
In this chapter we will see the different type of class type architecture such as user interface layer,
process/control layer, business/domain layer, persistence layer and system layer and also different types of
system modeling techniques that are used for the implementation of the system such as class modeling,
state chart modeling and also some system design techniques such as user interface design are also to be
covered in this chapter.
Generally this chapter is describes how the project is designed, what tasks done under this project.

4.2 Design goals

Design goal describes the quality of the system that developers should be optimize such goal are normally
derived from non-functional requirement of the system. Those are:-
• Performance

• Security

• Reliability

• Usability

• Error Handling

• Performance

The part of the system to be used for the customer should have a fast response time (real time)with
maximum throughput. Furthermore, the system should not be taking up too much space in
memory. The users of the system have chosen fast response time over throughput and hence the
system should try to be more interactive.

• Security: For security issue, only authenticated or authorized user can visit the system. An
 authorized user can create, update, delete, maintain the system and do other work. But customers
can give their comment without login to the system. Knowing website is enough to give comment.

• Reliability: The application which runs of the desktop can work on computer if the computer is
working properly. This means can work on every pc.

• Usability: - is the extent to which a product can be used by any user to achieve specified goal with
effectiveness, efficiency and satisfaction in specified context of use from the end user perspective
the system should be designed in such a way that it’s easy to learn and use efficient and having few
errors if any Trade-off is in evitable in trying to achieve a particular design goal.

• Error handling: The system can handle error of the user and display error message for the user to
correct that error.

4.3 Current software architecture

4.3.1 Architecture of the System

The existing system of the Dbcims is manual system and hence there is no current software architecture
that will be considered. As a result, we only describe the software architecture of the newly proposed
system.

4.3.2 Proposed software architecture

The proposed system is expected to replace the existing manual system by web based system which is all
aspects of dbcims. It is mainly based on the system Analysis document (chapter 3).
The architecture used for the system is a 3 tier Client/Server Architecture where a client can use Internet
browsers to access the online report provided by the system using the Internet or LAN.
Three tier architectures consist of three components distributed in 3 layers: client (requester of services)
the business logic (data handler) and server (provider of services). The three components are
User System Interface (such as session, text input, dialog, and display management services)
Processing Management (such as process development, process enactment, process monitoring, and
process resource services)
Database Management (such as data and file services)
4.4.4 Subsystem decomposition
Subsystem decompositions will help reduce the complexity of the system. The subsystems can be
considered as packages holding related classes or objects. The DBCIMS under consideration is
decomposed in to subsystems as shown by the following diagram. These subsystems are further
decomposed into other subsystems. The major sub systems identified are Manage Account,
Registration, judge process, and Search Customer information, View Information, Generate Report
and Give Comment. Those major subsystems also have Its own subsystem

4.4 Class Diagram

Model is the main stages of object domain modeling: class model shows the relationship including
inheritance, aggregation & association, operation and attribute of the class.
It shows the static structure of an object class. Their internal structure and relationship are participating.
The main action that shows on class diagram is class, object, operation, and dependencies. This model is
derived from the analysis class diagram. The only difference is system class diagram include access
modifier. There are three main access modifier and public. (-) symbol describes private (#) protects
attribute or method. (+) symbol used to describe the method or attribute is accessible for all (public).
Class diagram is the class that is involved in the system. There are some classes that have been identified
in this system
Fig.4.4 class Diagram
4.5 Persistence modeling for object oriented database
Persistent information management deals with how the persistent data (file, database, etc) are stored and
managed and it outlives a single execution of the system. Information related to court basic information,
case registration judge processes comment and management information produced and other related
information are persistent data and hence stored on a database management system. This allows all the
programs that operate on the DBCIMS data to do consistently.

appointment
case_id int
judge_id int
chilot varchar(255)
giving_date varchar(255)
appointment_date varchar(255)
newcase
date varchar(255)
first_name varchar(255)
middle_name varchar(255)
last_name varchar(255)
sex varchar(25)
Age int
Email varchar(255)
address varchar(255)
Phone_number int
case_id int
case_type varchar(255)
case_description varchar(21255)
Judge_ID varchar(255)
advocator_ID varchar(255)
Createaccount
User_id int
first_name varchar(255)
last_name varchar(255)
sex varchar(25)
Age int
Email varchar(255)
Phone_number int
Password varchar(255)
Re_password(255)
username(255)
user type(255)
Decision
Accuser (first_name varchar(255)
middle_name varchar(255)
last_name varchar(255)
sex varchar(25))
Defender (first_name varchar(255)
middle_name varchar(255)
last_name varchar(255)
sex varchar(25))
case_id int
case_type varchar(255)
Decision varchar(500078)
Judge_ID varchar(255)
DecisionDate varchar(255)
advocator
register_date date
advoctor_id int
first_name varchar(255)
Middle_name varchar(255)
last_name varchar(255)
sex varchar(25)
Age int
Email varchar(255)
Phone_number int
advocator_information varchar
(2555)
status varchar(255)
Fig 4.5 data base design
appointment
case_id int<fk>
judge_id int<fk>
chilot varchar(255)
giving_date varchar(255)
appointment_date varchar(255)
newcase
date varchar(255)
first_name varchar(255)
middle_name varchar(255)
last_name varchar(255)
sex varchar(25)
Age int
Email varchar(255)
address varchar(255)
Phone_number int
case_id int<<PK>>
case_type varchar(255)
case_description varchar(21255)
Judge_ID varchar(255)<<FK>>
advocator_ID varchar(255)<<FK>>
Createaccount
User_id int<PK>
first_name varchar(255)
last_name varchar(255)
sex varchar(25)
Age int
Email varchar(255)
Phone_number int
Password varchar(255)
Re_password(255)
username(255)
user type(255)
Decision
Accuser (first_name varchar(255)
middle_name varchar(255)
last_name varchar(255)
sex varchar(25))
Defender (first_name varchar(255)
middle_name varchar(255)
last_name varchar(255)
sex varchar(25))
case_id int<<FK>>
case_type varchar(255)
Decision varchar(500078)
Judge_ID varchar(255)<<FK>>
DecisionDate varchar(255)
advocator
register_date date
advoctor_id int<PK>
first_name varchar(255)
Middle_name varchar(255)
last_name varchar(255)
sex varchar(25)
Age int
Email varchar(255)
Phone_number int
advocator_information varchar
(2555)
status varchar(255)
4.6 Component Diagram
Component diagram are used to provide physical view of current model. The purpose of Component
diagram is to visualize the components of a system and relationships of the components.

Fig.4.6 component diagram

4.7 Deployment diagram
Deployment diagram are used to visualize the topology of the physical components of a system when the
software components are deployed. The purpose of the deployment diagrams are used for describing the
hardware component where the software components are deployed. This diagrams show the hardware
system, the software that is installed on that hardware, and the middleware used to connect the disparate
machines to one another

case
registration

Manageacco
Client unt
Application HTTP Wamp Persistence
Interface server
Generate
web Server DataBase
Report

Database
Server
Search
information

View
Information

Fig 4. 7 Deployment diagram

CHAPTER FIVE
OBJECT DESIGN
5.1 Introduction
It describes object design trade-offs made by developers, guidelines they followed for subsystem
interfaces and the class interfaces. The object design document is used to exchange interface information among
teams and as a reference during testing. This document discusses the object
design as per the current status of the implementation phase

5.2 Object design trade-offs

Deployment diagram is a UML diagram that used for describing how the hardware components
are deployed. We used to visualize the topology of the physical components of our system where
the mentioned software component diagrams are deployed. In the object design phase some
trade-off decisions may needed to be made:

 Development Cost Versus Functionality

Court Information Management provides a lot of functions for users such as record final decision, register
accuser and defender information., etc. Each function of the system requires extra design and this causes an
extra cost for the development.
 Understand ability versus Cost
Understand ability of the code is too important especially during the testing phase. Each class and
method must be readable, so number of methods increase in the system and functions must be
implemented in a clear way. Writing comments into the source code increases the
understand ability of the code.
 Security versus Cost
In Electronic shopping, users must be authorized to connect system from web, and unauthorized
people should not be able to access the system. Each user will be able to login to the system by
using the username and password that is assigned by super user.

5.3 Interface documentation guidelines

This section we will define rules or guidelines for naming variables, class attributes, interface,
exception, methods.
Interface documentation guidelines and coding conventions are the most important factors that can
improve communications between developers during object design.

Naming conventions make programs more understandable by making them easier to read. They can also
give information about the function of the identifier-for example, whether it's a constant, package, or
class-which can be helpful in understanding the code.

 Naming and Coding Conventions

 Packages: lowercase.
 Files: The java compiler enforces the convention that file names have the same base name as the
 public class they define.
 Classes: Capitalized with Internal words also capitalized
 Private or protected: first Word Lower Case but Internal Words Capitalized
 Static private or protected: first Word Lower Case but Internal Words Capitalized
 Local variables: lower case with underscores
 Methods: lower case with underscores

5.4 Packages

Package diagram is a graphical representation of the logical structure of the system as a set of
packages combined with dependencies and decomposed. These diagrams are used for grouping and
organizing complex project documentation. Our system has the following packages.
1. Database Package: This package contains classes used for making database connections and executing
queries on the database. Ex Database
2. User interface package: This package represents the user interface for employee. Example Admin
3. User Management Package: This package represents the User interfaces for administrator and contains
classes which perform user management related functions. Example Customer
4. Authentication Package: The package name is user Authentication package, and it contain class that
perform user Authentication functions.

CHAPTER SIX
IMPLEMENTATION AND TESTING

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

6.2 Testing
The test plan is designed to analyze the logic used in the implementation of the online shopping system.
The tests will allow us to ensure correct program flow, and to determine the error-handling capability of
the system.

Once coding has begun, the testing process can be beginning and proceed in parallel. As each program
module is produced, it can be tested individually, as a part of larger program, and then as a part of larger
system.

 Unit testing: Unit test is a way of testing each of the system functionality independently. Accordingly,
the team has tested each one of the major activities and the rest accompanying activities independently
using different user input, different login mechanisms and any technique of fault finding so that an
incorrect functioning of the activities was corrected at the right time.
 Integration Testing: Integration testing is testing in which a group of components are combined to
produce output. Also, the interaction between software and hardware is tested in integration testing if
software and hardware components have any relation.

 System testing: It is the final step of testing. In this system tested the entire system as a whole with all
forms, code, modules. In this we tested all the functionalities in the System. All errors in the forms,
functions, modules have been tested. Finally, System testing ensures that the entire integrated software
system meets the desired requirements. It tests a configuration to ensure known and predictable
results.

6.3 Hardware software acquisitions

To implement (develop) this project we shall use HTML, JavaScript for front end (developing
Graphic user interface).
Tools we will use additional software to different tasks.
Microsoft word 2010/2013
Microsoft PowerPoint 2010/2013
Xamp Web Server

6.4 User manual preparation

User manual preparation since the system is web based application everything important for the
user will be explained and implemented while preparation of short training document when the
system is deployed.

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

6.6 Start-up strategy

 The start-up strategy will be:
 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.

Sample Users Interface

The goal of user interface design is to make the user's interaction as simple and efficient as possible, in terms of
accomplishing user goals what is often called user-centered design. Good user interface design facilitates finishing
the task at hand without drawing unnecessary attention to it.
The following interface design pictures describe the logical characteristics of some interfaces
between the system and the users. So the sample interfaces are shown as follows:
Home Page
Admin Home Page
Law Officer Home Page
Judge Home Page
Sample Code
Login

<?php

//Start session

session_start();

include'connection.php';

//Unset the variables stored in session

unset($_SESSION['un']);

unset($_SESSION['fname']);

unset($_SESSION['lname']);

?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">

<head>

<title>Web Based Court Information Management System</title>

<meta name="description" content="free website template" />

<meta name="keywords" content="enter your keywords here" />

<meta http-equiv="content-type" content="text/html; charset=utf-8" />

<meta http-equiv="X-UA-Compatible" content="IE=9" />

<link rel="stylesheet" type="text/css" href="css/style.css" />

<script type="text/javascript" src="js/jquery.min.js"></script>

<script type="text/javascript" src="js/image_slide.js"></script>

<style type="text/css">

<!--

.style8 {color: #000000; font-weight: bold; font-style: italic;}

.style10 {font-style: italic; color: #00FFFF; font-weight: bold; }

.style11 { color: #0000CC;

font-size: 12px;

-->

</style>

</head>

<body>

<div id="main">
 <div id="header">

<!--close banner-->

<img src="images/clogo2.jpg" alt="image1" width="1202" height="118"/></div>

<!--close header-->

<div id="menubar">

<ul id="menu">

<li ><a href="index.php">Home</a></li>

<li><a href="about.php">About Us </a></li>

<li><a href="cntct.php">Contact Us</a></li>

<li><a href="viewappc.php">View Appointment </a></li>

<li><a href="givecomment.php">Give comment</a></li>

<li class="current"><a href="login.php">Login</a></li>

</ul>

</div><!--close menubar-->

<div id="site_content">

<div class="sidebar_container">

<div class="sidebar">

<div class="sidebar_item">

<body bgcolor=#9494B8>

<script type="text/javascript" src="http://www.24webclock.com/clock24.js"></script>

<table border="0" bgcolor=#0000FF cellspacing=2 cellpadding=4 class="clock24st" style="line-height:50px; line-

width:215px; padding:0;">

<tr><td bgcolor=#000000 class="clock24std" style="font-family:bold; font-size:26px;"><a href=" ">

</a>

<b><a href="http://www.24webclock.com/" style="text-decoration:none;"><span class="clock24s"

id="clock24_48332" style="color:white;"></b> </span></a></td></tr>

</table>

<script type="text/javascript">

var clock24_48332 = new clock24('48332',180,'%HH:%nn:%ss %P','en');

clock24_48332.daylight('ET'); clock24_48332.refresh();

</script></body>

<ul id="menu">

<li><a href="mission.php">Our Mission </a></li>

</ul>

<ul id="menu">

<li><a href="vission.php">Our Vission </a></li>

</ul>

<table width="200" height="250">

 </table>

<p>&nbsp;</p>

<div id="menubar1">

</div>

</div><!--close sidebar_item-->

</div><!--close sidebar-->

<!--close sidebar-->

<!--close sidebar-->

<!--close sidebar-->

<!--close sidebar-->

</div>

<!--close sidebar_container-->

<div>

<ul class="slideshow">

<li><img width="975" height="350" src="images/4.jpg"/></li>

<li><img width="975" height="350" src="images/3.jpg"/></li>

<li><img width="975" height="350" src="images/2.jpg"/></li>

<li><img width="975" height="350" src="images/1.jpg"/></li>

</ul>

</div>

<div id="content1">
<div class="content_item">

<form action='loginn.php' method='post'>

<table width="367" height="98">

<tr>

<th height="92" scope="row"><img src="images/loooogg.jpg" alt="" width="296" height="80" /></th>

</tr>

</table>

<table width="392" height="124">

<tr>

<th width="238" align="right" scope="row">User Name </th>

<td width="142"><label>

<input name="uname" type="text" id="uname" />

</label></td>

</tr>

<tr>

<th align="right" scope="row">Password</th>

<td><label>

<input name="pword" type="password" id="pword" />

</label></td>

</tr>

<tr>

<th height="30" colspan="2" align="right" scope="row"><label>

<input type="submit" name="Submit" value="Login" />

 </tr>

</table>

</form>

<a
href="forget.php">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

<font color="red">Forget Password?</font></a>

</div>

</div>

<ul id="menu">

<li class="style9 style18">

<h2 class="style19" align="center">Copyright©2017 Debre Berhan University Court Management System

</h2>

</li>

</ul>

<!--close sidebar_container-->

</div>

<!--close sidebar-->

</body>

</html>

<?php

session_start();
if(!isset($_SESSION['id']))

header('location: login.php');

$uname=$_POST["uname"];

$pword=$_POST["pword"];

$db = mysql_connect("localhost","root","") or die ("Error connecting to database.");

if(!$db){

$message= "no connection established"; }

mysql_select_db("court",$db) or die("Couldn't select the database.");

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

$results = mysql_query($qry,$db) or die(mysql_error());

$count=mysql_num_rows($results);

// If result matched $myusername and $mypassword, table row must be 1 row

if($count<='0'){

//if(!$results) {

$message="<center>Username or password was incorrect! Please try again </center>";

//include("log.php");

else

while ($row = mysql_fetch_array($results)) {

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

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

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

$user=$row['role'];

if($user=="admin"){

header('location:AdminPage.php');}

//echo "admin";

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

header('location:officer.php');

//echo "keeper";

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

header('location:judge.php');

$message="sorry,you are not amember";

mysql_close($db);

?>
Case Registration

<?php

require_once('auth.php');

include 'connection.php';

?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">

<head>

<title>Web Based Court Information Management System</title>

<meta name="description" content="free website template" />

<meta name="keywords" content="enter your keywords here" />

<meta http-equiv="content-type" content="text/html; charset=utf-8" />

<meta http-equiv="X-UA-Compatible" content="IE=9" />

<link rel="stylesheet" type="text/css" href="css/style.css" />

<script type="text/javascript" src="js/jquery.min.js"></script>

<script type="text/javascript" src="js/image_slide.js"></script>

<SCRIPT language=Javascript>

<!--

function isNumberKey(evt)

var charCode = (evt.which) ? evt.which : event.keyCode

if (charCode > 31 && (charCode < 48 || charCode > 57))

return false;

return true;

//-->

</SCRIPT>

<style type="text/css">

<!--

.style17 {
 color: #FFFFFF;

font-weight: bold;

font-style: italic;

font-size: medium;

.style18 {font-weight: bold}

.style19 {font-style: italic}

-->

</style>

<style>

ul {

list-style-type: none;

margin: 0;

padding: 0;

overflow: hidden;

background-color: #000000;

li {

float: left;

font-size:large;

li a, .dropbtn {

display: inline-block;

color: white;
 text-align: center;

padding: 16px 18px;

text-decoration: none;

font-size:20px;

li a:hover, .dropdown:hover .dropbtn {

background-color: #ffffff;

color:#000000;

text-decoration:none;

font-size:21px;

li.dropdown {

display: inline-block;

.dropdown-content {

display: none;

position: absolute;

font-size:medium;

background-color: #000000;

min-width: 160px;

box-shadow: 0px 8px 16px 0px rgba(0,0,0,0.2);

 z-index: 1;

.dropdown-content a {

color: white;

padding: 12px 16px;

text-decoration: none;

display: block;

text-align: left;

.dropdown-content a:hover {background-color: #f9f9f9

color:red;}

.dropdown:hover .dropdown-content {

display: block;

</style>

</head>

<body>
<div id="main">

<div id="header">

<!--close banner-->

<img src="images/clogo2.jpg" alt="image1" width="1201" height="118"/></div>

<!--close header-->

<div id="menubar">

<ul id="menu1">

<li ><a href="officer.php">Home</a></li>

<li class="dropdown">

<a href="javascript:void(0)" class="">Registration</a>

<div class="dropdown-content">

<a href="regcase.php">New case registration</a>

<a href="regadvocator.php">Register Advocator</a>

</div>

</li>

<li><a href="viewappo.php">View Appointment </a></li>

<li><a href="generaterepo.php">Generate Report </a></li>

<li><a href="searchinfo.php">Search customer Information </a></li>

<li><a href="login.php">logout</a></li>

</ul>
 </ul>

</div><!--close menubar-->

<div id="site_content">

<div class="sidebar_container">

<div class="sidebar">

<div class="sidebar_item">

<body bgcolor=#9494B8>

<script type="text/javascript" src="http://www.24webclock.com/clock24.js"></script>

<table border="0" bgcolor=#0000FF cellspacing=2 cellpadding=4 class="clock24st" style="line-height:50px; line-

width:215px; padding:0;">

<tr><td bgcolor=#000000 class="clock24std" style="font-family:bold; font-size:26px;"><a href=" ">

</a>

<b><a href="http://www.24webclock.com/" style="text-decoration:none;"><span class="clock24s"

id="clock24_48332" style="color:white;"></b> </span></a></td></tr>

</table>

<script type="text/javascript">

var clock24_48332 = new clock24('48332',180,'%HH:%nn:%ss %P','en');

clock24_48332.daylight('ET'); clock24_48332.refresh();

</script></body>

<div id="menubar1">
 <table width="212" height="36">

<tr>

<th width="204" bgcolor="#330066" scope="row"><span class="style17">Judge and court</span></th>

</tr>

</table>

<div class="sidebar">

<div class="sidebar_item">

<table width="222" height="384">

<tr>

<th height="28" colspan="2" bgcolor="#999999" scope="row"><p><marquee behavior="scroll"

direction="up" onmouseover="this.stop();" onmouseout="this.start();">

1. Judges should approach their judicial duties in a spirit of collegiality, cooperation and mutual
assistance..</p>

<p>2. Judges should conduct court business with due diligence and dispose of all matters before them
promptly and efficiently having regard, at all times, to the interests of justice and the rights of the parties before
the court..</p>

<p>3. Reasons for judgment should be delivered in a timely manner.</p>

<p>4. The primary responsibility of judges is the discharge of their judicial

duties.</p>

<p>5. Judges have a duty to maintain their professional competence in the law.</marquee></p></th>

</tr>

<tr>

<th width="230" height="347" colspan="2" scope="row"><marquee direction="up">

 </marquee>

<marquee direction="up">

<p>&nbsp;</p>

</marquee></th>

</tr>

</table>

<p>&nbsp;</p>

<p>&nbsp;</p>

<p>&nbsp;</p>

<p>&nbsp;</p>

<ul id="menu">

<li></li>

</ul>

</div><!--close sidebar_item-->

</div>

</div>

<!--close sidebar_item-->

</div>
 </div><!--close sidebar-->

<!--close sidebar-->

<!--close sidebar-->

<!--close sidebar-->

<!--close sidebar-->

</div>

<!--close sidebar_container-->

<div id="content">

<p>

<!--close content-->

</p>

<td valign="top">

<br>

<div style="width:480px; height:510px; margin:0 auto; position:relative; border:2px solid rgba(0,0,0,0); -webkit-
border-radius:5px; -moz-border-radius:5px; border-radius:25px; -webkit-box-shadow:0 0 18px rgba(0,0,0,0.4);
-moz-box-shadow:0 0 18px rgba(0,0,0,0.4); box-shadow:0 0 18px rgba(0,0,0,0.4); margin-top:20px;
color:#000000;">

<!--Form Validation-->

<script type='text/javascript'>

function formValidation(){

//assign the fields

 var firstname=document.getElementById('fname');

var middlename= document.getElementById('mname');

var lastname= document.getElementById('lname');

var user_id = document.getElementById('user_id');

var phone = document.getElementById('phone');

var username = document.getElementById('username');

var password = document.getElementById('password');

var cpassword = document.getElementById('cpassword');

if(isAlphabet(firstname, "please enter Your First name in letters only")){

if(lengthRestriction(firstname, 3, 30,"for your First name")){

if(isAlphabet(middlename, "please enter Your Middle name in letters only")){

if(lengthRestriction(middlename, 3, 30,"for your Middle name")){

if(isAlphabet(lastname, "please enter Your Last name in letters only")){

if(lengthRestriction(lastname, 3, 30,"for your Last name")){

if(isAlphanumeric(user_id,"Please Enter the Correct ID No (!@#$%^&*()*+=~`) Not allowed")){

if(lengthRestriction(user_id, 3, 15,"for your ID No")){

if(isAlphanumeric(password,"Please Enter the Correct Password (!@#$%^&*()*+=~`) Not allowed")){

if(lengthRestriction(password, 5, 10,"for your Password")){

if(isAlphanumeric(cpassword,"Please Enter the Correct Confirmation Password (!@#$%^&*()*+=~`) Not allowed"))

{

if(lengthRestriction(cpassword, 5, 10,"for your Confirmation Password")){

if(isAlphanumeric(username,"Please Enter the Correct Username(!@#$%^&*()*+=~`) Not allowed")){

if(lengthRestriction(username, 5, 10,"for your username")){

if(isNumeric(phone, "please enter Number only For Phone Number")){

if(lengthRestriction(phone, 10, 10,"for your Phone number")){

return true;
 }}}}

}}

}}}}

}}}}

return false;

function isAlphabet(elem, helperMsg){

var alphaExp = /^[a-zA-Z]+$/;

if(elem.value.match(alphaExp)){

return true;

}else{

alert(helperMsg);

elem.focus();

return false;

function emailValidator(elem, helperMsg){

var emailExp = /^[\w\-\.\+]+\@[a-zA-Z0-9\.\-]+\.[a-zA-z0-9]{2,4}$/;

if(elem.value.match(emailExp)){

return true;

}else{

alert(helperMsg);
 elem.focus();

return false;

function isNumeric(elem, helperMsg){

var numericExpression = /^[0-9]+$/;

if(elem.value.match(numericExpression)){

return true;

}else{

alert(helperMsg);

elem.focus();

return false;

function lengthRestriction(elem, min, max, helperMsg){

var uInput = elem.value;

if(uInput.length >= min && uInput.length <= max){

return true;

}else{

alert("Please enter between " +min+ " and " +max+ " characters" +helperMsg);

elem.focus();

return false;

function isAlphanumeric(elem, helperMsg){

var alphaExp = /^[0-9a-zA-Z\/]+$/;

 if(elem.value.match(alphaExp)){

return true;

}else{

alert(helperMsg);

elem.focus();

return false;

function isAlphabet(elem, helperMsg){

var alphaExp = /^[a-zA-Z]+$/;

if(elem.value.match(alphaExp)){

return true;

}else{

alert(helperMsg);

elem.focus();

return false;

</script>

<form id="form1" name="login" method="POST" action="regcase.php" onsubmit='return formValidation()'>

<div style="background-color:#000000;border-radius:5px;font-family:Arial, Helvetica, sans-serif; color:#000000;

padding:5px; height:22px;">

<div style="float:left;" ><strong><font color="white" size="2px">Register New Case</font></strong></div>

<div style="float:right; margin-right:20px; background-color:#cccccc; width:25px; text-align:center; border-

radius:15px; height:12px;">

<a href="adminpage.php" title="Close"><img src="img/close_icon.gif"></a></div>

</div><br>

<?php

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

if('$_POST[fnumber]'!=""||'$_POST[aname]'!=""||'$_POST[pname]'!=""||'$_POST[ctype]'!
=""||'$_POST[ftype]'!=""||'$_POST[odate]'!=""||'$_POST[chierarchy]'!=""||'$_POST[amount]'!
=""||'$_POST[fund]'!=""||'$_POST[bill]'!=""){

$sql=mysql_query("INSERT INTO newcase

(file_number,accuser_name,plaintif_name,case_type,file_type,open_date,judge_id,advocator_id,payment
,case_hierarchy,amount_money,bill_number,file_status)

VALUES

('$_POST[fnumber]','$_POST[aname]','$_POST[pname]','$_POST[ctype]','$_POST[ftype]','$_POST[odate]','$_POST[j
id]','$_POST[advocatorid]','$_POST[amount]','$_POST[chierarchy]','$_POST[fund]','$_POST[bill]','open')");

if($sql){

echo '<p> <font size=4 color=#008080>data inserted sucesfully</font></p>';

echo'<meta content="3;regcase.php" http-equiv="refresh" />';

else{

echo mysql_error();

mysql_close($conn)

?>
 <table width="550px" align="center">

<br><br><h2>Fill all required information below</h2>

<tr>

<td > File Number:</td><td><input type="text" onKeyPress="return isNumberKey(event);" required

name="fnumber" id="fnumber" required x-moz-errormessage="Enter file number" ></td>

</tr>

<tr>

<td> Plaintif Name:</td><td><input type="text" name="pname" id="pname" required x-moz-

errormessage="Enter palintif name" ></td>

</tr>

<tr>

<td> Accuser Name:</td><td><input type="text" name="aname" id="aname" required x-moz-

errormessage="Enter accuser name" ></td>

</tr>

<tr>

<td> Case Type:</td><td><input type="text" name="ctype" id="ctype" required x-moz-

errormessage="Enter case type" ></td>

</tr>

<tr>

<td>File Type :</td>

<td style="padding-top:12px;"><select name="ftype" required >

<option value="" >select..</option>

<option value='crime'>crime</option>

<option value='justice'>Justice</option>

<option value='Work dispute'>Work dispute</option>

 </select></td> </tr>

<tr>

<td> Open Date:</td><td><input type="text" readonly name="odate" id="odate" value="<?php echo

date('Y-m-d');?>"required x-moz-errormessage="Enter date" ></td>

</tr>

<tr>

<td>Case Hierarchy :</td>

<td style="padding-top:12px;"><select name="chierarchy" required >

<option value="" >select..</option>

<option value='Primary level'>Primary level</option>

<option value='Appeal'>Appeal</option>

</select></td> </tr>

<tr>

<td> Judge ID:</td><td>

<select name="jid" required>

<option value="">--select--</option>

<?php include('connection.php');

$query = mysql_query("SELECT User_id from account where role='judge'");

while($row = mysql_fetch_assoc($query)){?>

<option><?php echo $row['User_id']; ?></option>

 <?php } ?>

</select></td></tr>

<tr>

<td> Advocator ID:</td><td>

<select name="advocatorid" required>

<option value="">--select--</option>

<?php include('connection.php');

$query = mysql_query("SELECT ID from advocator");

while($row = mysql_fetch_assoc($query)){?>

<option><?php echo $row['ID']; ?></option>

<?php } ?>

</select></td></tr>

<tr>
 <td> Amount of the debt(Birr):</td><td><input type="text" onKeyPress="return isNumberKey(event);"
name="amount" required x-moz-errormessage="Enter amount" ></td>

</tr>

<tr>

<td> Dedidated Fund(Birr):</td><td><input type="text" name="fund" onKeyPress="return

isNumberKey(event);"required x-moz-errormessage="Enter dedicated fund" id="fund"></td>

</tr>

<tr>

<td> Bill Number:</td>

<td><input type="text" onKeyPress="return isNumberKey(event);" name="bill" required x-moz-

errormessage="enter bill number" id="bill"></td>

</tr>

<tr>

<td>&nbsp;</td>

<td ><input type="submit" name="save" value="Save"

class="button_example"/>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<input type="reset" name="cancel"
value="Cancel" class="button_example"/></td>

</tr>

</table>

</form>

</div>

<!--close sidebar_container-->

</div>

<ul>

<li>
 <h3 align="center">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

<font color="white" face="Time New Roman"><i>Developed By Summer Information Technology

Students</i></font></h3>

</li>

</ul>

<!--close sidebar-->

</body>

</html>

Chapter Seven
Conclusions and recommendations

7.1 Conclusions:
This project mainly focuses on the Web Based Information management system of debre birhan court
Office. It includes, Case Registration, Generate report, view information, record decision, giving
appointment, view appointment, etc.as stated in the various sections of the document. We have faced
many problems while we have been working. The first is the willingness of the court office managers,
workers, and to provide the required information. The second one is virus and the limitation of light,
connection working on.

7.2 Recommendations:
According to scope of our project the team develops web application .Because of the time constraint we
cannot do beyond to our scopes, but in the future the team believes that this system can be fully
operational by having enough time and full information. Neatly, the team would recommend that further
work should be done on the system. Based on the preceding information in our project, we believe that the
following recommendation will help the organization to improve their system more reliable and available
as they want. The organization should be inter connect with zonal court Office communicate online. Be
able to use more acceptable and available system to internal as well as external system users. It should be
interesting to give full information to those who develop system. It is better to adapt and use software
based system operations (business process action) in each sub system of the organization.

Reference
[1].http://en.wikipedia.org/wiki/Sequence_diagram
[2].http://www.foruse.com/articles/euc-responsibility.pdf
[3].http://www.agilemodeling.com/artifacts/essentialUI.htm
[4].http://leanagilechange.com/leanagilewiki/index.php?title=Class_Responsibility_Collaboration
[5].http://www.ambysoft.com/essays/classTypeArchitecture.html
[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] Linda Dawson & Paul Swatman, (1998). The Use of Object-Oriented Models In Requirements
Engineering: A Field Study.
[12] Rumbaugh, J., Jacobson, I., &Booch, G. (2003). The Unified Modeling Language Reference
Manual: the definitive reference to the UML from the original designers, Pearson Education Inc.,
Singapore.
[13] Scott W. Ambler’s book, The Object Primer 2nd Edition

[14] Greenspan, J., Wall, D. and Bulger, B. (2004) Mysql/PHP Database Applications. Wiley.