Court Management System: Department of Information Technology

Court management system
Table of Contents
2013
Chapter one ..................................................................................................................................... 3 Project proposal .............................................................................................................................. 3 1.1 1.2. 1.3. 1.4. Introduction .......................................................................................................................... 3 Background .......................................................................................................................... 4 Statement of the problem ..................................................................................................... 5 Objective of the problem ..................................................................................................... 5 General objective .......................................................................................................... 5 Specific objective ......................................................................................................... 5
1.4.1 1.4.2 1.5. 1.6. 1.7. 1.8.
Scope of the project ............................................................................................................. 6 Constraints/limitation........................................................................................................... 6 Alternative solution .............................................................................................................. 6 Feasibility study ................................................................................................................... 7 Economical feasibility .................................................................................................. 7 Operational Feasibility ................................................................................................. 8 Technical Feasibility..................................................................................................... 8 Schedule feasibility....................................................................................................... 9
1.8.1 1.8.2 1.8.3 1.8.4 1.9.
Proposed solution ................................................................................................................. 9
1.10 Methodology ........................................................................................................................ 9 1.11 Specification for hard ware and soft ware ......................................................................... 10 1.12 Significant of the study ...................................................................................................... 11 1.13 Overall cost estimation ...................................................................................................... 11 1.14 Schedule ............................................................................................................................. 13 Chapter two ................................................................................................................................... 15 Analysis phase .............................................................................................................................. 15 2.1 2.2 2.3 2.4 2.5 2.6 Introduction ........................................................................................................................ 15 Detail study of the current system ..................................................................................... 15 Problem of the current system ........................................................................................... 15 Over view of the new system ............................................................................................. 17 Input and output requirements ........................................................................................... 17 Requirement analyzing of the new system ........................................................................ 18 Functional requirement ............................................................................................... 18
2.6.1
1 Department of information technology

2.6.2 2.7 3.1 3.2 3.3 3.4 3.5 3.6 4.1 4.2 4.3
2013
Non functional requirement ........................................................................................ 19
Data flow diagram (DFD) .................................................................................................. 19 Introduction ........................................................................................................................ 24 Logical database design ..................................................................................................... 24 E-R-Model: description ..................................................................................................... 24 Normalization: ................................................................................................................... 30 Physical database design .................................................................................................... 35 Relational database ............................................................................................................ 35 Introduction ........................................................................................................................ 39 Implementation and testing ................................................................................................ 39 User interface ..................................................................................................................... 39 Login form .................................................................................................................. 40 Case form .................................................................................................................... 41 Payment form ............................................................................................................. 42 Judgment form ............................................................................................................ 42
Design phase ................................................................................................................................. 24
Chapter four .................................................................................................................................. 39
4.3.0 4.3.1 4.3.2 4.3.3 4.4 4.5
Sample code of the system ................................................................................................. 43 Testing................................................................................................................................ 46 System testing ............................................................................................................. 46 Unit testing ................................................................................................................. 47 Integration testing ....................................................................................................... 47 Acceptance testing: ..................................................................................................... 47
4.5.1 4.5.2 4.5.3 4.5.4 4.6 4.8 5
Error Handling ................................................................................................................... 47 Installation.......................................................................................................................... 49 CONCLUSION ..................................................................................................................... 52
Chapter five ................................................................................................................................... 52

Chapter one Project proposal 1.1 Introduction
2013
Throughout history, people have had disputes and have needed some means to settle their disputes. As civil societies develop, they need an orderly system of conflict resolution. One system that developed in "Ethiopia" cultures is the "law court" or court of law. In Ethiopia, those early law courts developed a "body of law" called the common law, which defined both the rights of the people and the government and the duties people owe each other and their government. The Gondar high court is one of the only and oldest court located in the northern part of the city. The court examines multiple cases of individuals coming from different part of the country. In our propose system we will develop desktop application for north Gondar high court. Now a day the court is uses a partial computerized recording system and besides to that they records customer record by MSExcel but this is not effective to facilitate their work. Therefore developing this system has great advantage. For example if we take one system in this court we develop a system using VB 6.0 which tells the appointment date of customer when they enter case number. This system facilitates their work and effectively shows the appointment of plaintiff or defendant. So developing computerizing recording system of the court has such advantage like easily searching and generates reports.

1.2. Background
2013
The year 1943E.c was conspicuous for the continuation of the administrative reforms which aimed at the modernization of the country. The medieval system of taxation and the toll gate were abolished; legal reforms introduced education and public health improved. During this period Ethiopia has experienced in modern constitution .to apply the constitution there were an idea of sharing the governmental power in to legislative, executive and judiciary. The judiciary system of Ethiopia is also divided in to different levels to facilitate the judiciary system all over the country state were given power to serve their people giving a fair decision among these state Gondar is one of them. Gondar high court was built in the region of emperor Haileslasie in 1949E.c having almost 20 employees when it was established it have mission and vision .its mission was to provided a fair decision according to the low and its vision is to insure that rule of low is obeyed. At that time people who go far different purpose were so much sophisticated become of the very slow process of the court system.
The north Gondar high court
performs different kind of activities which are focused on the
criminal and civil case .in addition it also facilitate the work flow of the organization and minimize the work load of the employee.

1.3. Statement of the problem
2013
The currently used manual file system is not reliable depending on:- The north Gondar high court have many problem it need high amount of time and human power, Luck of security the file stores in different are may attack by different like rat, tedious and time consuming to find the file and Because of the work load and the capacity of the organization this type file system cannot be efficient to serve the user. The data used by this organization need to be maintained at time if necessary but the manual file system is not easily to maintain the data because of time and The organization work on same secured process which need access control but the currently
used system does not have high security from an authorized access and data can be corrupted.
1.4.
Objective of the problem 1.4.1 General objective
The main objective of this study is to develop a desktop application court recording system in to the north Gondar high court.
1.4.2 Specific objective
When the project finish the new system will solve the following: Data collection of the organization of the high court. Enabling the employee in the court to be familiar with developing soft ware as well as it makes the client to be user of the result behind the technology. database design implement of the system testing
Enabling the court functionality to be effective

Study the existing system of the organization Giving traing to the users about the new system how it work

1.5. Scope of the project
2013
The scope of the project is highly focused on the court recording system and client problem. Providing a well organized report consisting all of the necessary information about each individual customer. Searching of data easily Storing data for longer time Register of the data in court Delete of unnecessary records Adding of record Update of customers records
1.6.
Constraints/limitation
There seems to be a lot of constraint that exist during the work on this project. The following are some of them: Luck of budget(transportation, phone communication) Luck of time we are takes different course and other projects Luck of communication gap with the organization manager and the employees Team group is formed from different section due to this there is aleck of communication gap. The power on and off in our campus really made the speed of our projects completion very slow.
1.7.
Alternative solution
Some of the alternative solution to working the system and manage the court record system are listed below:1. desktop application 2. web based application 3. semi automation

4. full automation
2013
Desktop application:-all tasks are applicable on the desktop like window-XP. Desktop application is easily understand for the user to uses different services. Also for the designer will easily develop and easily maintain and install and test error etc.
1.8.
Feasibility study
Feasibility study is designed to determined wither or not the project is feasible on some aspects like economically, operationally, technically and schedule is feasible. The feasibility study concerned on the determination and description of court record system how the project feasible on these aspects.
1.8.1 Economical feasibility

Our team has found that the desktop assumption is economically feasible because here we have suggested only on single computer to be used the implement the new system. Tangible benefits are items which can be quantified in monetary terms and with certainty such as equipment, salary of staff/personnel, and materials (hardware and software) The tangible benefit estimated about 10,000 birr. Intangible benefit are items for which a value cannot be precisely determined and where the value may be the result of subjective judgment such as how much money is saved by completing a project earlier. Increase flexibility and speed of the system Minimization of data redundancy Error reduction Employee satisfaction Improve of employee moral
This intangible benefit estimated about 5,000 birr. To wind up the project has a benefit of 15,000 birr benefit. The total cost Developing this project is 19555 birr.

economically feasible because 19,555- 15,000=4,555 birr of net benefit.
2013
Therefore when the tangible and intangible benefit with the total project cost the project is
1.8.2 Operational Feasibility

The purpose of the operational feasibility is to gain understanding of which the proposed system will likely solve the north Gondar high court problems. o High security of the record of the customer o It give more satisfaction to the employee and customers of the organization o It is fast to do the tasks or the operation In the manual system there is no secure data that means when one client or customer needs to know the appointment date it was observed by the other but not in the new system .the new system helps to avoid this action. In the new system the data can observed only by the owner of the case(file) it is not observed by other people that means it is secure to access. Hence this operational feasibility is feasible.
1.8.3 Technical Feasibility

This is concerned with specifying equipment and software that will successfully satisfy the user requirement. The technical needs of the system may vary considerably, but might include: - The facility to produce outputs in a given time - Response time under certain conditions. - Ability to process a certain volume of transaction at particular speed. The employees of the organization need training to easily access and store customer information in the new system. The proposed system put in consideration on supplying the adequate performance by any means as possible including select the best combination of hardware and software. Hence the technical feasibility is feasible.

1.8.4 Schedule feasibility
2013
Time evaluation is the most important consideration in the development of project. The time schedule required for the developed of this project is very important since more development time effect machine time, cost and cause delay in the development of other system.
1.9.
Proposed solution
Our group member selects a Desktop application to solve the problem of the organization of north Gondar high court. Desktop application:-all tasks are applicable on the desktop like window-XP. For the sake of having satisfactory system we are going to develop software which is well designed desktop application (data base) that has greater positive impact according to time, labor cost, storage space and security.
The role of data base according to the labors cost once the data base is developed the only labor that is needed is one who is operating the database. And the role of the database according to storage space compared to the manual one the space that the develop database offer is unambiguously preferable because the system hard disk can possibility store large amount of data rather than the manual system. The role of data base according to security since the database is only designed to be accessed by authorized users who will have their own password and user name and the role of the data base according to time currently since the existing recording system of north Gondar high court is manual based it takes great amount of time which in turn delay other kind of operation so the data base that we proposed to develop will reduce unneeded time.
1.10 Methodology
1.Over view:- we tried to interview the organization manager of the north Gondar high court
and employees to give information when the organization was started (opened), what type of system they uses and we are try to ask what problem can occur in their organization.

In the interview we are used an open ended questioners.
2013
2. Observation:-we observe the organization work place to have a business oriented

perception. We observed the sated data and the manual system of the organization. This methodology is easily to understand the work flow of the organization.
3. Document analyses:-the business records like the printed paper or organizational form
(sample) were the source of our project specially to design the interface of the new system the project. Like background of the court organization system, court recording system structure and different form of the organization.
1.11 Specification for hard ware and soft ware Hard ware
CD-R: - used to store data Flash: - used to holding backup data and Printer: - used to print a document Personal computer:-: - used to do a project Projector: - used to present our project
Software
MS Access 2003:- used to store database information MS Word 2003:- used to write the document of the project
Visual Basic 6.0:- used to design, coding, and the interfaces of the for(GUI)
Window-XP: - it is the system of the computer that we used
2013
1.12 Significant of the study

After this system is developed it will give the following benefits to the court organization. Reduce error time required in managing the data of its thousands of clients Improves recording, updating and retrieving customer document. Providing timely information /service for clients/employees. Improve customer satisfaction Decrease data redundancy Increase security Increase speed to generate fast and easy report Reduce the human power needed for searching purpose
1.13 Overall cost estimation Hardware

Item CD-R Flash(8GB) Printer Projector Personal computer quantity 1 1 1 1 1 Total Price 15.00birr 150.00birr 8000.00birr 2000.00birr 9000.00birr 19,165.00birr
2013
Table 1.1
Software
Item MS Access 2003 1 MS Word 2003 1 Visual Basic 6.0 1 40.00birr 50.00birr 40.00birr 50.00birr 40.00birr 40.00birr quantity Unit price Total
Total cost = 130.00birr Table 1.2
Other
Item Communication Statitionary Transportation Total price 150.00birr 60.00birr 50.00birr 260.00birr
Table 1.3
2013
1.14 Schedule
NO 1 1.1 1.2 Task Planning phase Estimate date 14 Begging date 13/07/05 13/07/05 16/07/05 Ending date 27/07/05 15/07/05 16/07/05
Background of study 3 Statement problem of the 1
1.3 1.4 1.5 1.6 1.7 1.8
Objective of study Scope of the project Constraints Feasibility study Proposed solution Specification hardware software
2 1 1 2 2
17/07/05 19/07/05 20/07/05 21/07/05 23/07/05 25/07/05
18/07/05 19/07/05 20/07/05 22/07/05 24/07/05 25/07/05
for 1 and
1.9
Significant of the 1 study
26/07/05
26/07/05
1.10
Overall estimation
cost 1
27/07/05
27/07/05
2 2.1
Analysis phase Study system of
15
1/08/05 1/08/05
15/08/05 4/08/05
current 4
2.2 2.3
Input and output
5/08/05 9/08/05
8/08/05 11/08/05
Over view of the 3

new system 2.4 3 3.1 3.2 3.3 Process modeling Design Logical design Data model 4 13 5 4 12/08/05 17/08/05 17/08/05 22/08/05 26/08/05 15/08/05 30/08/05 21/08/05 25/08/05 30/08/05
2013
Physical data base 4 design
4 4.1 4.2 4.3 4.4 4.5 4.6 5
Implementation Interface design Coding Testing Functionality Error handling Installation Conclusion References Appendix
15 2 3 2 2 3 3 2 2 2
3/09/05 3/09/05 6/09/05 9/09/05 11/09/05 13/09/05 16/09/05 20/09/05 22/09/05 24/09/05
18/09/05 5/09/05 8/09/05 10/09/05 12/09/05 15/09/05 18/09/05 21/09/05 23/09/05 25/09/05
Table 1.4

Chapter two Analysis phase 2.1 Introduction
2013
In analysis phase more emphasis is given to understanding the details of an existing system or a proposed one and then deciding whether the proposed system is desirable or not and whether the existing system needs improvements. Thus, analysis phase is the process of investigating a
system, identifying problems, and using the information to recommend improvements to the system. Analysis phase of the new system describes the problem of the organization and it can identify the functional and non-functional requirement of the system. It can also shows how the system can works it means it shows the data flow diagram of the organizations
2.2 Detail study of the current system

The current system of north Gondar high court is functioning manually because of this reason the organization is suffered for data lose and the system does not have the ability of to serve the applicant properly in time and space. In addition, data accessing of the client/customer of the court and searching of records is very difficult and time taken as well as it needs high manpower of the organization to facilitating the functions. The current system is secure that means not deleted or difficult to modified the paper but not in the new system data can modified in the database
2.3 Problem of the current system

The existing system of the organization of the court is used manually as we have discussed in the above by this reason the organization faces various problem which makes the judicial system slow .User cannot get services easily and data security of the organization is slow this means the records of the customer is stored in a ware house it may attack by any means and it is visible /accessed /by any people this is illegal store of data.

The following are the problem of the current system Information and data
2013
Input:-customer information of the North Gondar High Court (NGHC) is not correctly captured, it contains some error, there is a redundancy of records that means the same information of customers data is captured more than ones. Output:-the system generates any information about the customer of the organization is done manually it is difficult to produce needed information from the manual based system and not time efficient. Data Store information Data/record/ of customers like (plaintiff and defendant)are not well organization Searching of information recorded data are difficult Data of the clients of the north Gondar high court are stored manually it needed have high storage space. Economically Cost:-the existing system of the court recording system takes much cost for buying pen, paper (forms) of the customer information and others.
Efficiency There is a wastage of human power There is no way knowing if the person is repeatedly recorded or not.
Service Some systems are difficult to change or modify The system is inflexible to know or exceptional situation
Back up:-this refers to making copies of data so that these additional copies may be used to restore the original values after the data lose event occurs but not supported by the current system.

2.4 Over view of the new system
2013
The new system is complete to a desktop application which contain service requirement. It is effective and efficient performance and it able to be providing more suitable to working environment to the recorder and customer of the court system. When the new system complete it used for: It will manage the system easily It will store information in a limited spaces It will easily searching the record of the customer by case no or by others searching methods It will computerized the manual system of the organization It makes customer satisfaction It reduce employee of the organization
2.5 Input and output requirements

Input Record of plaintiff file name, detail explanation of the case, assigning case number, appointment date, judgment ,judges who charge the of the case. Record of the defendant file name of the defendant, address of the defendant, appointment of date, reason of the appointment and others. Process
Identify the case type weather is it appeal or first instance and others Identify status of the case , closed, active ,passed to other organization (court) Identify type of the court, who is charge of the case. Identify if the case has been observed in other court or not Update, delete, save existing records. Identify plaintiff file weather it is an organization ,governmental and person Identify the plaintiff weather it is teacher, doctor, or professor and others. Identify the defendant weather it is teacher, doctor, or professor and others.

Save the customer information like (plaintiff defendant)
2013
Output Maintain client dependant information or report generate Providing fast information (searching) of the files like case number, appointment date. Access the information securely Appointment date Judge decision Judgment date
2.6 Requirement analyzing of the new system

Requirement analyzing helps to understand the behavior of the system. This describes various task of the new system .the new system requirement determination to understand the current system problem and opportunity as well as what is needed and desired in the new system .the new system have a database which contain all requirement information entry.
2.6.1 Functional requirement

A new system accommodates some function requirement that must include in the customer information (plaintiff and defendant) recording system to achieve the record objective which helps to create acceptable system by the user. After complete the new system it will provide the following service to the organization and to the customer of the organization. Save the customer information. Easily searching customer record (like plaintiff and defendant) by case no/name. Delete unnecessary records. It is more secure Reporting the information records

Updating of records
2013
2.6.2
Non functional requirement
Non functional requirement is a requirement that specify criteria that can be used to judge the operation of a system, rather than specific behavior (characteristic and behavior). Non-functional requirement can be divided in to different category; the following are some of them. The performance of the new system can be seen according three ways.
Computer performance:-is characterized by the amount of use full work accomplish by a computer system compared to the time and resource used. Security :-the new system compared to the existing system the database is only designed to be accessed by authorized user who will have their own password and user name their will not be a question of security indicating that all data stored in the data base. Speed:-when compared to the current system response time for searching of customer file, the new recording system play great role .this means easily searching file of the client in a short period of time. Storage Space: - when to compare the current system to the new system the current system holds large storage space to store the records.
Process model description:
process model is a technique for the organization and
documenting the structure and flow of data through a systems process and/or the logic, policy and procedure to be implemented by a system process.
2.7 Data flow diagram (DFD)

It Is a tool that depicts the flow of data through a system and the work or processing performed by the the north Gondar high court system. We are tried the organizational structures look like we are discussed on the main flow of the organizational structure 2.7.1
Context diagram
Represents the entire system and general structure of the organization.

Employee
2013
Order customer data
Request service Customer Providing service Court management system
perform cases Judge Activity file
Report customer records
President
Context diagram
Level 0 diagram represent the major process, data flow and data store of the system at high level of detail
2013
Employee
Accept Pays Payment Order customer data
Request service
Perform case 0 Court management system
Customer
Provides services
Judge
Activate file
Activate customer file 0.1 Criminal data Store data D3 criminal records D1 judgment records D2 Data store civil records Activate criminal data 0.2 Judgment Activate civil data 0.3 Civil data
Generate criminal data
Generate civil data
0.4 Produce report
Report Customer information
President
Level 0 data flow diagram Fig 2.2

Employee
2013
Accept Pays Payment Order customer data Activate file 0.1 Court management system Provide Service
Customer
Request service
Judge
Asking of witness
perform cases
Giving witness Activate criminal data
1.0 Judgment D1 store judgment record Make decision
Higher court D2 appeal records
1.2 Criminal law
1.3 Civil law Appeal
Innocent Decides innocent Decides monetary Prison 1.4 Decision decision records Disagree D8 disagree rec Agree D9 agree fiel D4 decision records Produce report Generate decision records
D7 Monetary Sentences D4: prison d5: monetary d6: sentence file File file
President 22 Department of information technology
Report customer data
2013
Level 1 diagram Fig 2.3
N.B description of symbols that used in the above diagrams Symbol Name Process Function Set by steps instruction as followed that transform input to output Data flow Data following from place to place such as input or output to process External agent Data store Line The source or destination of data outside the system Data at rest, being stored for later use Used to connect entity with attributes
Table 2.1
2013
Chapter 3
Design phase
3.1 Introduction
This design phase is established based on the common database designing model which is relational database model. Relational database model is organizing stored data into structure called table or relation. Relational database table are that can stored in the form of column and row. Each table has a unique key (primary key) attribute that is used to differentiation each record in one relation or table a single row of table is used to represents a record of the respective instance and the column are used to represent the field values or attribute value which are used to represent the field value of attribute values which are useful to describe the behavior of the instance. At this phase we are try to normalize the entity of which described in chapter 2 and also we are try to created the physical database of them.
3.2 Logical database design
Logical database in order to understand the relationship among different data objects involves in the system we need an entity relationship data model, which are commonly used diagrams that show how data is organized in a system. E-R model is based on apperception of the real world that consists of a set of basic objects called entity and of relationship among these objects. Its developed to facilitate database design by allowing the specification an enterprise schema which represents an overall structure of the database.
3.3 E-R-Model: description

Entity relationship modeling is used to represent conceptual view of the database. We used the data element include in the data flow on the DFD as a procedures to identify the possible entity with their corresponding attribute and relationship among the system

The main components of ER-Modeling used in this system are:Entity:-represents real world physical or logical objects like (person, place) It represents by rectangle shape Attribute:-used to describe each entity or a real world object It can represented by oval(ellipse) shape Relationship: - represent the association that exist between entities It can represented by Diamond shape Primary key:-used to describe a tuple uniquely identify It can represent by underline like (case no). Multi values:-used to represent the attribute which have more than one value It can represented by double circle Derived value:-used to represent the value of the attribute is which calculated value It can represented by dotted line(circle)
2013
Weak entity:-used to represent the entities which have more than one value It can represented by double rectangle
Degree of relationship of the system
Cardinality interpretation Exactly one One or more Zero or more More than one Zero or one
Minimum instance
Maximum instance
Graphical representation
1 1 0 Many 0
1 Many Many Many 1

Age Sex F name
2013
Bag no.
Employee L name
Master Status
Professor
Diploma Degree
PHD Figure 3.1 ER-diagram for employee
First instance Appeal Defendant fname Civil Case type status Appointment date Case status Closed Judgment date Criminal Active Case condition Case no Case
Plaintiff lname
2013
Figure 3.2 ER-diagram for case entiy Payment reason Payment date
Case no
Payment
Payer name Receipt no
Figure 3.3 ER-diagram for payment entity and its attribute
In the ER diagram below different weak entity and there are relation with strong entity are show House no Kebele Plaintiff Address Woreda
Region
City
Phone no
2013
Figure 3.1.E-R diagram of plaintiff and address relationship
Degree Professor Defendant Status Diploma
PhD
Master
Figure 3.2 E-R diagram of defendant and status relationship
Appeal Case Status First instance
Figure 3.3
E-R diagram of case and status relationship
2013
1) One plaintiff can process at least one or many case at a time, one plaintiff can charge one or more defendant, one or more defendant provide a court and one or more cases can upload to the court.
Plaintiff
Process
Case
Charge Upload
Defendant
Provides
Court
Figure 3.4E-R diagram for plaintiff and case relationship
2) A Plaintiff can pay zero or many money
Plaintiff
Pays
Payment
Figure 3.5 E-R diagrams for judge and case relationship

3) Many employees can manage one court and one court has many employees.
2013
Employee
Manages
Court
Has
Figure 3.5 E-R diagrams for employee and its relationship
3.4 Normalization: -
the normalization is a process which we identify and correct inherent
problem and complexity in our record database design. A database record specifies the field and identifies the primary key, if any for all records in a particular situation working with a set of initial records design we use normalization to develop an overall database design that is simple, flexible and free of data redundancy. There are three normalization first normal form, second normal form, and third normal form.
I. First normal form: - a relation is in first normal form if it is simple value and atomic this means simple value is one single value that does not have further component. II. Second normal form: - relation is second normal form if every non primary key attribute is functionally dependent on the whole primary key thus no non functionally dependent on part but not the entire primary key. primary key attribute is
2013
III. Third normal form: - a relation is third normal form if it is in second normal form and there is not functionally dependency between two or more non primary key attribute. Third normal form represents the best database design.
Relational database model

Relational data schema can be interested as declaration or type of assertion each topple in the relation can then be interpreted as a fact or particular instance of the assertion some relations may represented facts about entities where as other may represent the relationship.
Table: Case
UN normalized case entity
case no Case type Plaintiff full name Defendant full name Age Sex Case status Case condition
First normal form for case entity Case no Civil Criminal Plaintiff name 10001 10002 10003 Defendant Full name Civil Civil Judgme nt Date Abiyot Alem Adise Emunetu Kebede Abaye 12/05/05 12/05/05 19/03/05 19/03/05 19/03/05 19/03/05 First instances First instances Appeal Criminal Appointment date Abebe getu Amsale yechale Desaleg abebe First instance 20 38 38 Appeal Male Male Male full Age Sex
This is first normal form for case it is simple and atomic attributes

Second normal form case type Case no 10001 10002 10003 Civil Civil Criminal Criminal criminal
2013
Case no- civil, criminal, are functionally dependent on the primary key
Second normal form for case status

Case no 10001 10002 10003 First instance First instance First instance Appeal Appeal -
Second normal form for case condition

Case no 10001 10002 Active Active Closed Closed
Second normal form case Case no Plaintiff Full name Defendant Full name Age Sex Appoint ment Date 101 Abebe Getu Abiyot Alem 102 Amusalu Yechale 103 Desaleg abebe Adise Emunetu Kebede Abaye 38 Male 19/03/05 19/03/05 38 Male 19/03/05 19/03/05 20 Male 12/05/05 12/05/05 Judgment date
Case no -
plaintiff full name, age,sex, Defendant full name, appointment date, judgment
date are functionally dependent on the primary key

Third normal form case type Case no 101 101 103 Civil Civil Civil Criminal Criminal -
2013
Case no- civil, criminal are not functionally dependent on the non primary key attributes
Third normal form case Case no Plaintiff Full name 101 Abebe Getu Defendant Full name Abiyot Alem 102 Amsale Yechale Adise Emunetu 103 Desaleg abebe Kebede Abaye Attribute of the above table are not functionally dependent on the non primary key attributes this is third normal form for case entity 38 Male 19/03/05 19/03/05 38 Male 19/03/05 19/03/05 20 Age Sex Appointment Date Male 12/05/05 12/05/05 Judgment date
Table: Employee:
in this normal form is employee can president, judge or other
employee of the organization.
First normal form for employee Employee bag no Zone Employee Employee Employee Sex Fname House no Mname Phone no Lname Doctor Professor Degree Master Diploma Age Region Wereda Keble
2013
Employee bag no- employee Fname, employee Lname, employee Mname, age, sex, salary, wereda, kebele, zone, house no, phone no, doctor, master, diploma degree, professor are simple value and atomic the it is first normal form.
Second normal form for employee Employee no bag Employee Fname Employee Mname Employee Lname Sex Age Salary
Employee bag no- employee Fname, employee Lname, employee Mname, age, sex, salary are functional dependent on the primary key
Second normal form for employee address Employee Region bag no Employee bag no- wereda, kebele, zone, house no, phone no are functional dependant on the primary key Employee bag no, house no, phone no are partial functional dependant on the primary key Wereda Kebele Zone House no Phone no
Second normal form for employee status Doctor Professor Degree Diploma Master Employee bag no
Employee bag no-doctor, master, diploma degree, professor are functional dependent on the primary key
Third normal form for employee Employee bag Employee no Fname Employee Mname Employee Lname Sex Age
Attributes of the above tables are - employee Fname, employee Lname, employee Mname, age, sex, salary are not functional dependent on the non primary key attribute

Third normal form for employee address Employee Region bag no Wereda Keble Zone House no
2013
Phone no
The above table employee address is wereda, Keble, zone, house no, phone no are functional dependant on the non primary key attribute
not
Third normal form for employee status Employee bag no Doctor Professor Degree Diploma Master
Attributes of the above table doctor, master, diploma degree, professor are not functional dependent on the non primary key attribute
Table: payment
This is a normal form for payment Receipt no Payer name Payment date Payment reason Case no
Attributes of the above tables are not functional dependency on the non primary key attributes the payment table
3.5 Physical database design

This part of data base design requires a brief understanding of the deferent between logical database and physical records and an understanding of data storage format, including special characteristics of data field ,in order to the database system more efficient and protected from same accidental error.
3.6 Relational database

A database structured to recognize relations between stored items of information. A relational database is a database that has a collection of tables of data items, all of which is formally described and organized according to the relational model. The term is in contrast to only one table as the database, and in contrast to other models which also have many tables in one

identifying a row called the primary key.
2013
database. In the relational model, each table schema must identify a primary column used for
Table: case
Fields Case no Plaintiff full name Criminal Civil Sex Age Defendant full name Appointment data Judgment date Appeal First instance Data type Number Text Text Text Text Number Text Number Number Text Text Field size 7 10 7 7 5 3 10 10 8 7 1 Default value Primary key Not null
Table 3.1 case

Table: employee
2013
Field Employee no Employee name Employee middle name Employee name Sex Age Salary House no Phone no Keble Woreda Region Master Degree PHD Doctor Professor
Data type bag Number
Field size 7
Default value Primary key Not null
first Text
15
Text
15
last Text
15
Text Number Number Number Number Text Text Text Text Text Text Text Text
5 3 5 10 10 5 10 8 8 8 8 8 8
03 -
Table 3.2 employee
Court management system Table: payment

Field Receipt no Payer name Payment date Payment reason Case no Data type Number Text Number Text Number Field size 7 15 8 30 8 Default value Primary key Not null
2013
Table 3.3 payment

Chapter four
4.1
2013
Introduction
This chapter is focused on the implementation and testing of the program of the system. That means how the user can interact with the system, in this chapter it also how can search customer information and report customer data are described. It also discussed on the error handling of the system, how can install the software after it completed and the flow of the system.
4.2
Implementation and testing
In this chapter we mainly focuses on the implementation part, implementation concerned with the type of material (Hardware and software required), techniques to develop the system, code samples of the system, features to be testing , some testing techniques and testing case
specifications system are described in this part of documentation.
4.3User interface
The user interface, in the field of humanmachine interaction, is the space where interaction between humans and machines occurs. The goal of this interaction is effective operation and control of the machine on the user's end, and feedback from the machine, which aids the operator in making operational decisions. A user interface is the system by which people (users) interact with a machine. The user interface includes hardware (physical) and software (logical) components. User interfaces exist for various systems, and provide a means of:

Input, allowing the users to manipulate a system Output, allowing the system to indicate the effects of the users' manipulation

4.3.0 Login form
2013
As we shown in the figure below form allows the user to login in by entering a user name and filling the password inside the available text box, this form protects the database from unauthorized user. In order to use the system a user must enter the user name and a password in this log in interface. The user interface should be considered to connect with the system will interface to be organize on the computer.
Fig 4.1
Login form

4.3.1 Case form
2013
As shown below form the information is filled belong to a case it holds the information of plaintiff and defendant information with the case type, case status and case condition of the files.
Fig 4.1
Case form

4.3.2 Payment form
2013
The form which shows in the below that describes the payment amount, payer name and payment reason of the cases.
Fig 4.3 Payment form
4.3.3 Judgment form

As we shown in the below form it shows the decision of the judges of the case type, appointment date, and case no. and appointment reason of the cases. Also this form is the main references for the report generated and displayed when the button report is clicked and it mainly focus on judgments.
2013
Fig 4.4 Judgment form
4.4
Sample code of the system
Login code: used to enter the user to the main form Private Sub Command1_Click () If (Text1.Text = "CMS" And Text2.Text = "123") Then Form3.Show Me. Hide Else MsgBox ("please enter valid user name and password") End If End Sub

Search code: used to search records in the short period of time Private Sub Command1_Click () Dim x as String Dim Y as Integer x = Input Box ("search by case number", "search", " ") Adodc1.Recordset.MoveFirst If x = " " Then Else Do While Not Adodc1.Recordset.EOF If x = Text5.Text Then MsgBox ("you are searching the data by case No., click to see") Exit Sub Else Adodc1.Recordset.MoveNext End If Loop End If If Y = 0 Then MsgBox "sorry, the number is not available", vbExclamation, "results" End If End Sub
2013
Next command: used to navigate the records Private Sub Command4_Click () If Adodc1.Recordset.BOF = True Then Adodc1.Recordset.MoveLast Else Adodc1.Recordset.MovePrevious End If End Sub
2013
Previous command: Private Sub Command5_Click () If Adodc1.Recordset.BOF = True Then Adodc1.Recordset.MoveLast Else Adodc1.Recordset.MovePrevious End If End Sub
Delete command: used to delete unnecessary records Private Sub Command9_Click () Dim x as Integer x = MsgBox ("are you sure? you want to delete the data.", vbYesNo) If x =vbyess Then Adodc1.Recordset.Delete Text2.Text = " " Text3.Text = " " Text4.Text = " " Text5.Text = " " Text1.Text = " " End If End Sub
Clear command: Private Sub Command11_Click ()

Text1.Text = "" Text2.Text = "" Text3.Text = "" Text4.Text = "" Text5.Text = "" Text6.Text = "" Combo1.AddItem "" End Sub
2013
4.5
Testing
Software testing is a critical element of the ultimate review of specification design and coding. Testing of software leads to the uncovering of errors in the software functional and performance requirements are met .Testing also provides a good indication of software reliability and software quality as a whole. The result of different phases of testing are evaluated and then compared with the expected results. If the errors are uncovered they are debugged and corrected. Testing is a process of executing a program with the intent of finding an error. A successful test is one that uncovers an as yet undiscovered error. Our Objective is to design test processes that systematically uncover different classes of errors and do so with minimum amount of time and effort.
4.5.1
System testing
The system can control any incorrect data input by comparing the data inserted with the registered data on database. If there is any mismatch it display at an interface showing that an incorrect text has been entered or an incorrect record has been set. It also assures weather the action user take is needed to be performed. The above is a sample interface that will be displayed while a user mismatches the user name and password in the login form.
2013
Fig 4.5 system testing
4.5.2 4.5.3
Unit testing: testing performed on each module or block of code during development.
Unit testing is normally done by the programmer who writes the code.
Integration testing: testing done before, during and after integration of a new module
into the main software package. This involves testing of each individual code module. One piece of software can contain several modules which are often created by several different programmers. It is crucial to test each modules effect on the entire program model.
4.5.4
Acceptance testing: the testing of the product done by the actual end users.
4.6
Error Handling
1. Should report any Out of Range values on numeric fields 2. Should report any data type mismatches any field on the forms.

3. Should report any violation of authorization of rights 4. Should report any invalid Login errors
2013
The form which shows sorry the number is not available this message displays by the system when the user enters invalid data or when to try searching by invalid data.
Fig 4.6 error handling
4.7
. System
Flow
Here the court management officer controls the whole court system process by generate court management system and accepting requests to different sections that are directly related to the process of the users contact the court management officer when ever needed. The system flow of this system is, whenever the database manager want to enter the system he/she begin with start, all program, court management system, login with in user name and password, main form, enter the sub form you want. Under main forms of court management system, there are three interfaces of court management. These interfaces are:

Case Judgment Payment
2013
Therefore the system follows sequence of all the system and which is shown as the following diagram:
Start
All programs
Sub forms ( Case Judgment Payment )
Main form
Login user name and password
Fig 4.7 flow system
4.8
Installation
The software product is going to be protected by copy right laws and international copyright treaties, as well as other intellectual property laws and treaties. Users manual: its easy-to- use installation software places safely onto your PC. Court management system is extremely friendly, with little or no training, anyone who has basic knowledge of windows XP. Compatibility: the software is compatible with Ms Office 2003 XP and other standard windows based on word processors. Installation procedures
2013
This section provides step-by-step instruction on how to install court management system on to your computer. However, its critically important to follow installation instruction precisely. Failure to do so may result in the malfunctioning of the software.
Court management system Installation Turn on your computer and get ready to install court management system. Close all programs before running setup. Make sure you have inserted the court management system CD inside your computer CD-ROM before you run setup.
For the newly developed court management system the computers with appropriate software specification (VB.6.0 operating system of windows XP and Ms Access server 2003) should be purchased. Then the system is installed into the computers and the old system will be replaced by the newly developed system. This means the spread sheet system of existing system that the court management officer used for generating court management for items is converted to the developed automated system.
Installation Turn on your computer and get ready to install court management system. Close all programs before running setup. Make sure you have inserted the court management system CD inside your computer CD-ROM before you run setup. Note To install follow the following steps:

Turn your PC and start windows. Open my computer.
2013
First you have an option to install main software then you have the option of installing framework if not installed before. Set up program will guide you through the set up process. Then follow the on screen installation guides. At any time you may choose to abort the setup by clicking on CANCEL button. At the end, setup program will show you success notice.
Installation is finished after the application has been installed and tested the system is ready to be functional and then preparation could begin to place the new system in to operation. Hence, in order the new system to be operational the new system should be loaded with the existing data from the old system. The start-up strategy used is parallel conversion strategy, means the old system and the new system will operate simultaneously for some time, because the defect of the new system will be identified if any, before the old system is abandoned and until get user acceptance.
2013
Chapter five
5 CONCLUSION
Summarizing our documentation we conclude that newly developed has dynamic feathers of managing and manipulating information in such a way that it reduced data redundancy inconsistency and invalid output result and also make the whole system more convenient and give fast and reasonable service to client. And we the system team members totally believe that

working environment will be produce our proposed system is put on work.
2013
the existing problem of the north Gondar high court will be resolved and sustainable and flexible

Court Management System: Department of Information Technology

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Court Management System: Department of Information Technology

Uploaded by

Copyright:

Available Formats

Court management system

1.4.1 1.4.2 1.5. 1.6. 1.7. 1.8.

1.8.1 1.8.2 1.8.3 1.8.4 1.9.

Proposed solution ................................................................................................................. 9

1 Department of information technology