Developing An Automated System Fordebre Markos Woreda Legal

DEBRE MARKOS UNIVERSTY
COLLEGE OF TECHNOLOGY
DEPARTMENT OF IT
Title
Developing an automated system

forDebre markos Woreda Legal
system
Prepared by Abatneh Shiferaw
Advisor: Ahimed G.
June 2004
DEBRE MARKOS UNIVERSTY
ACKNOWLEDGEMENT
First and for most I would to thanks my advisor Ahimed Ghe help me by giving his advice and
correction until I finish the project. I thanks to friends whose supports are always with me. I
thanks to our department, staff, and its environment where they fulfilled my thoughts.
DMU
Chapter 1 ....................................................................................................................................................... 5
Introduction ................................................................................................................................................... 5
1.1 Background the organization .............................................................................................................. 5
1.1.1 Establishment ............................................................................................................................... 5
1.1.2 Vision ........................................................................................................................................... 5
1.1.3 Mission......................................................................................................................................... 5
1.1.4 Objective of the organization ....................................................................................................... 5
1.1.5 General objective of the organization .......................................................................................... 5
1.1.5 Specific objective of the organization .......................................................................................... 5
1.1.6 Organizational structure ............................................................................................................... 6
1.1.7 Tasks under taken by the organization ......................................................................................... 7
1.2 Statement of the problem .................................................................................................................... 7
1.3. Objective of the project ...................................................................................................................... 8
1.3.1 General objective ......................................................................................................................... 8
1.3.2 Specific objective ......................................................................................................................... 8
1.4. Significance of the new system .......................................................................................................... 8
1. 5. Scope and limitation of the project ................................................................................................... 9
1.5.1 Scope ............................................................................................................................................ 9
1.5.2 Limitation ..................................................................................................................................... 9
1.6. Methodology ...................................................................................................................................... 9
1.6.1 System Development Methodology ............................................................................................. 9
1.6.2 Programming and Database Tools ............................................................................................. 10
1.6.3 Data collection methodology ..................................................................................................... 11
DMU
1.7 Feasibility Analyses ...................................................................................................................... 11

1.7.1 Economic feasibility .................................................................................................................. 11
1.7.1.1 Costs.................................................................................................................................... 12
1.7.1.1.1 Tangible cost ................................................................................................................ 12
Table 1. Budget schedule .................................................................................................................... 12
1.7.1.1.2 Intangible cost .............................................................................................................. 12
1.7.1.2 Benefits ............................................................................................................................... 13
1.7.1.2.1 Tangible benefit ........................................................................................................... 13
1.7.1.2.2 Intangible benefit ......................................................................................................... 13
1.7.2 Technical feasibility ................................................................................................................... 13
1.7.3 Operational feasibility ................................................................................................................ 13
1. 7.4 Schedule feasibility ................................................................................................................... 13
Chapter 2 ..................................................................................................................................................... 15
2 Business Area Analysis and Requirement Definition .............................................................................. 15
2.1 Business Area Analysis..................................................................................................................... 15
2.1.1 Study of the activities ................................................................................................................. 15
2.1.2 Problems of the current system .................................................................................................. 15
2.1.3 Forms and Reports Currently Used ............................................................................................ 17
2.1.4 Users of the existing system....................................................................................................... 17
2.1.5 Business Rule Identification ...................................................................................................... 18
2.1.6 Use Diagrams ............................................................................................................................. 19
2.1.7 Essential use case diagrams ....................................................................................................... 20
2.1.8 Essential use case description .................................................................................................... 22
2.2 Requirements definition .................................................................................................................... 25
2.2.1 Functional Requirements ........................................................................................................... 25
2.2.2 Non-Functional Requirements ................................................................................................... 26
2.2.3 Essential user interface prototyping ........................................................................................... 28
Chapter 3 ..................................................................................................................................................... 31
3 OBJECT ORIENTED DESIGN ...................................................................................................... 31
3.1 System Use Case ............................................................................................................................... 32
3.1.1. User Interface Identification ..................................................................................................... 32
DMU
3.1.2 Business Rule Identification ...................................................................................................... 32

3.1.3. Actors Identification ................................................................................................................. 34
3.1.4. Use Case Identification ............................................................................................................. 34
3.1.5. Designing the System Use Case Diagram................................................................................. 35
3.1.6. Use Case Description ................................................................................................................ 37
3.2. Sequence Diagramming ................................................................................................................... 39
3.3. Activity Diagrams ............................................................................................................................ 43
3.4. Class Diagram .................................................................................................................................. 45
3.4.1. Description of Class Diagram ................................................................................................... 46
3.5. User Interface Prototyping ............................................................................................................... 51
Chapter 4 ..................................................................................................................................................... 56
4.1. Conclusion ....................................................................................................................................... 56
DMU
Chapter 1
Introduction
1.1 Background the organization
1.1.1 Establishment
The court was established In 1987 E.C by two judges and four supportive officers. At that time
they perform 1738 cases. Due to the government policies and proclamations, to attain the justice
easy and to improve the service, increased the trained employees. The employee become thirteen
judges and thirty eight supportive officers totally fourty six employees. In 2003 E.C the court
perform 3921 cases and also it tries to achieve its vision and mission.
1.1.2 Vision
To see the rule of law is assured and justice is override in this woreda.
1.1.3Mission
To prevail the justice

To establish democracy and good governance
Give efficiency and fair decision/judgment
1.1.4 Objective of the organization
1.1.5General objective of the organization
IS to rehabilitate those who have violated the law. However, anyone who has experienced it from
the punitive side can attest that rehabilitative services available to offenders are minimal or
cursory at best.
1.1.5 Specific objective of the organization
1)Maintain good governance in which effectiveness, transparency and accountability, to the

residents, prevail; make the City one in which expedient and equitable municipal services and
reliable security and social harmony are ensured.
DMU
2)Create favorableconditions of living and work as well as to facilitate conditions in which

residents determine the overall operations of the City and become beneficiaries of its
development.
3) Make the City a Centre where Ethiopian Nations, Nationalities and Peoples reside in equality
and express their cultures.
4) Make the City a place where the well-being and comfort, of residents are safely kept and
particularly where children, women, the disabled, the elderly and other disadvantaged segments
of society avail themselves of special support;
5) Make the City a naturally balanced, clean, green and favorable spot through the prevention of
environmental pollution
6) Give fair judgment for peoples
1.1.6 Organizational structure
Leader of judges
DMU
Supporter manager
Main manager
Supporter
professionals
Case worker
Judges
HRM
Finance
Record office
Law officer
Civil case
writing team
Civil case
technique
supportive
team
Civil case
document
team
Figure 1. Organizational structure

1.1.7 Tasks under taken by the organization
The legal system is engaged the following main activities.

Record new case and give appointment such as
Conflict between wife and husband
Ask food request and also d/t types of civilcase
Judge the case and give judgment
Record case related to crime and give appointment
1.2 Statement of the problem

The following are the main problems of Debre markos city woreda legal system:
DMU
Information
Desk
The system works manually and the data handling and processing system creates problem
on summarization and integration of data for decision making.
The system couldnt generate needed report
It is difficult to give appointment timely it asks refer huge manual documents
It takes time to accomplish one task
Wastage of resource example paper:-since the files are maintained manually, it consume
more paper
1.3.Objective of the project

1.3.1General objective
The general objective of this project is to develop automated system that is applicable in
improving the manual legal system for Debre Markos city woreda legal system.
1.3.2 Specific objective
1. Speed up the legal system by providing convenient file handling

2. Generate reliable report
3. Give reliable search facility
4. Create easy and user friendly environment
5. Create attractive user interface
1.4.Significance of the new system

The benefits of the projects are listed below
Makes information easily accessible

Reduce resource wastage
Fast decision making by generating report easily
Creates satisfaction to the employee
Easy to know the record customers
Save time to accomplish one task
Implementation of this project will lead the
organization to a better performance that can highly
reduce the workload of employee and customers
DMU
1.5.Scope and limitation of the project

1.5.1 Scope
As the project title indicates the scope of the system to make computerized system for Debre
Markos City woreda legal system.
They are stated below
Record newly arrived civil cases

Record newly arrived criminal cases
Generate different report
Display the necessary information by search facility
Setting appointment for the available cases
1.5.2 Limitation
There is shortage of time to accomplish the project. If I have more time then I can
analyze, design, and implement the system more effectively.
Inadequate reference books and internet
Lack material such as computer
Poor cooperation of users to provide enough information
Lack of experience in solving real life problems
Absence of sample project done before
1.6. Methodology
1.6.1 System Development Methodology
In my project I used object oriented development methodologies because it has the following
advantages:
Encourages re-use ,not only of modules but also of entire designs
o In particular it allows the recognition of a class hierarchy form which
classes required in a new application can either be re-used (inheritance).
o This greater amount of re-use should lead to reduced development
maintenance costs.
Object oriented system tend to be based upon stable forms which are easy to change
o This means that object oriented system are more likely to be allowed to evolve
time, rather than have to be abandoned or completely re-designed in response to
major changes in the customers/users requirements.
DMU
1.6.2 Programming and Database Tools
1. The graphical interface (front end) of the application is prepared by the usage of visual
basic.net.
Because visual basic.net has the following advantage:
VB.NET provides managed code execution that runs under the Common Language
Runtime (CLR), resulting in robust, stable and secure applications
The .NET framework comes with ADO.NET, which follows the disconnected paradigm,
i.e. once the required records are fetched the connection no longer exists.
It also retrieves the records that are expected to be accessed in the immediate future. This
enhances Scalability of the application to a great extent.
Another great feature added to VB.NET is free threading against the VB single-threaded
apartment feature. In many situations developers need spawning of a new thread to run as
a background process and increase the usability of the application. VB.NET allows
developers to spawn threads wherever they feel like, hence giving freedom and better
control on the application.
Security has become more robust in VB.NET. In addition to the role-based security in
VB6, VB.NET comes with a new security model, Code Access security.
The CLR takes care of garbage collection i.e. the CLR releases resources as soon as an
object is no more in use.
[http://dev.fyicenter.com/Interview-Questions/dotNet-1/Advantages_of_VB_NET.html]
2. The back end of the application is maintained in MySQL database.
o Ease of use and maintenance.
o Many SQL servers are intended for use with large data sets and to handle many
users. When you are dealing with multiple users and huge amounts of data, you
need a system that is reliable (meaning it doesn't crash much) and safe (meaning it
is difficult for unauthorized access). In the 2008 release of SQL, a new feature is
Performance Studio. This collection of tools, writes Schlichting, can be used
together to troubleshoot, monitor and tune your system to prevent problems that
lead to system crashes. Also, in SQL Server, you have tools such as Policy-Based
Management that allows database administrators to define policies for the data
and to receive alerts when the policies are violated. You can also encrypt the
entire database, including your data and log files, making your server safer from
attacks. There are External Key Management features that allow you to support
third-party certificates and encryption information in a separate section, so you
10
DMU
can handle credit-card processing and remain compliant with current laws for the
credit card industry.
o Support Amharic.
[httphttp://www.ehow.com/list_5993393_advantages-sql-server-2008.html]
3 Microsoft Office Visio
Used to make UML diagrams
3. Power Geez
4. Microsoft word 2010 for documentation
1.6.3 Data collection methodology
Data sources: - To understand the internal working of the legal system I have used the
following sources:
Various users
Employees
Data Gathering tools:
Interview technique: During interview I got the necessary information from the
employees.
Document analysis: I tried to discover all the written documents about the
organization areas relevant to the system such as
Organizational structure
Different forms used on the current system
1.7 Feasibility Analyses
They are four key consideration involved in this feasibility analysis each consideration has
reviewed to depict how it relates to the system effort.
They are as follows:Economic feasibility
Technical feasibility
Operational feasibility
Schedule feasibility
1.7.1 Economic feasibility
Analysis in this procedure I determine the benefits that are expected from the proposed system
and compare the cost, I take a decision and implement the new proposed system.
11
DMU
1.7.1.1 Costs
1.7.1.1.1 Tangible cost
These costs are those that can be estimated in money terms. The table shows tangible costs.
No
Material name
Type
Quantity
Total
1
1
Price/birr
Each
12,000
100
1
2
Computer
Software
Toshiba
Vb.net
SQL server
100
100
Power Geez
50
50
Microsoft word
50
50
50
50
Microsoft Visio
3
4
5
6
7
8
9
Paper
Pen
Printer
Flash
CD
Transport
Bic
Cruzer blade 8GB
DVD
Taxi
1 packet
1 packet
1
1
7
6 round
90
36
400
1
12,000
100
90
36
2500
400
140
6
Total 15922
Table 1. Budget schedule
1.7.1.1.2 Intangible cost
These costs can be estimated in money terms

Time wasted while the project is undertaken
Loss of employee moral
12
DMU
1.7.1.2 Benefits
1.7.1.2.1Tangible benefit
These benefits can be estimated in terms of money which means the benefit is real or actual
rather than imaginary or visionary .For instance improving response time ,producing error free
out put such as report are all tangible benefit.
These benefits can be:Cost reduction (less use of paper)
Increase the speed of activities
1.7.1.2.2 Intangible benefit
These benefits cannot be estimated in money terms

Faster decision making
Increase accuracy
Increase information processing efficiency
1.7.2 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.
Facility to generate report
The system will be compatible in all types of operating systems especially current version
operating systems i.e windows.
1.7.3Operational feasibility
The employees were happy and generous to give information about everything I
asked them about the organization I did not get any negative things while collecting
information in the organization. This indicates that the project is operationally
feasible.
1.7.4Schedule feasibility
Tasks may not be accomplished during the stated schedule dueto many obstacles. I
will try to resist problems as much as I can or amend the schedule if possible and
finish our project as scheduled. The scheduled as follows
Tasks
Month
Mar
13
Apr
May
Jun
DMU
Topic selection
20
23
Proposal writing
24
Analysis
8
24
Design
15
24
Implementation
1
Presentation
11
12
Table 1.1 project time table
14
DMU
Chapter 2
2 Business Area Analysis and Requirement Definition
2.1 Business Area Analysis
Business area analysis evaluates how well business process, business rules, business data,
organizational structure, and people skills match the mission of the organization unit. It develops
recommended process improvement actions which can include quick fixes for serious problems,
modification of existing automated system or the initiation of a business process reengineering
project.
Citation:[http://www.requirementssolutions.com/BusinessAreaAnalysis_JAD.html]
2.1.1 Study of the activities
Record new civil cases

Record new criminal cases
Give appointment for different cases
Evaluate the cases and give decision
2.1.2 Problems of the current system
The system works manually and the data handling and processing system creates problem on
summarization, updating and integration of data for decision making. The problems of the
existing manual based system are described using the PIECES from work. Where
P is performance
I is information
E is economics
C is control,
E is efficiency and
S is service
Performance
Throughput
The current working system has a low level of throughput because it can only handle
limited number of customer at a time.
Response time
15
DMU
The response time to a given task in the current working system is significantly low due to
The time taken to get the accurate information of customers and prepare different
reports
Information (and Data)
Outputs
It is difficult to produce needed information form the manual documentation
Inputs
Data is not accurately captured, contain errors
Data is captured redundantly, example appointment date
Stored data
Since the file handling system is manual there is no any security
Data is not organized
Economics
Costs
The current system takes more costs to perform its tasks
Profit
The current system does not design at producing profit when it compares with the
cost it expense.
Control and security
Data is not adequately edited
Data privacy regulations or guidelines can be violated
Efficiency
Information is redundantly generated
o There is no way of knowing if customers repeatedly come for
insured purpose
Service
16
The system is inflexible to change
DMU
2.1.3 Forms and Reports Currently Used
There are different forms and reports used by the court for various purposes. All the forms are
used Amharic form
Number
Forms
1
2
3
4
5
6
/ Statement ofcrime claim from

/ loan money Statement of claim from
/Claim for divorce request form
/Successor certificate claim form
/Maintenance request claim form
/Divorce by agreement and
effects of divorce approved claim form
Table 2.1 Forms of the existing system

2.1.4 Users of the existing system
Since I mainly concerned only the legal system of Debre markos City Woreda legal system, I will deal
only with persons involved on this service.
Users
Manager
Criminal case Judges
Civil case Judges
Record office
Information desk
Customer
Is part of the computerized system?

NO
NO
NO
Yes
NO
NO
Table 2.2 Users of the existing system
Manager
The Manager gets reports from the case workers manually. The reports help the manager to see
how services are given to the customer and manage the organization.
Criminal Case Judges
They interact with customers and record office. They judge the case concerned with criminal
cases and give decision.
Civil Case Judges
They interact with customers and record office. They judge the case concerned with civil cases
and give decision.
Record office
17
DMU
This record officer only interacts with some services at one computer. Particularly the file that
received from information desk the form manual document. They generate report to case
workers.
Information Desk
This record officer only interacts with customers by any types of case. Particularly new case
arrived from the customer. Here the record officer asks the customer every information needed,
gather the information and fill manually on a paper then finally send the file to record office.
Customer
The customer does not interact with the computerized system rather he/she requests a service
from the information desk. The customer then gives necessary information based the case. The
customer gets his/her requested service from the information desk.
2.1.5 Business Rule Identification
Name:-loan money Statement of claim

Id: - BR1
Description:
The claim person must have real evidence to loan money to him/her
The claim person must came the file that contains the agreement of between them about
the loan of money
Name:-Claim for divorce request

Id: - BR2
Description:
Husband and wife came their profile that describes the marry of contract
Duration of time they live together
Amount of capital they have
Name:-Successor certificate claim request

Id: - BR3
Description:
Successor have evidence that checks the child of died person

Him/her show when and where the father and mother die
18
DMU
They should come person that knows the child of the died person
Successor/s should signed
Name:-Maintenance claim request

Id: - BR4
Description:
Maintenance requester have evidence the relationship between maintenance requestor

and maintenance give person
The maintenance request age should be under 18
Maintenance request should signed
Name:- Divorce by agreement and effects of divorce approved claim request

Id: - BR5
Description:
Attach their divorce by agreement document
Both of them should be signed
Name:-Appeal request from

Id: - BR6
Description:
Him/her case is should have been closed

Ask the appeal by their signature
2.1.6 Use Diagrams
A use case diagram (B. Meyer 1997) illustrates a set of use cases for a system, the actors of these
use cases, the relations between the actors and these use cases, and the relations among the use
cases. The UML notation for a use case diagram is shown on figure 2.1, in which
An oval represents a use case,
A stick figure represents an actor,
19
DMU
A line between an actor and a use case represents that the actor initiates and/or
participates in the process.
Use cases
Informally speaking, a use case is a story or a case of using a system by some users to carry out a
process. A bit more precisely speaking, a use case describes the sequence of events of some
types of users, called Actors, using some part of the system functionality to complete a process.
Actors
An actor represents a coherent set of roles that are entities external to the system can play in
using the system, rather than representing a particular individual. An actor represents a type of
users of the system or external systems that the system interacts with.
2.1.7 Essential use case diagrams
An essential use case (Constantine and Lockwood 1999), sometimes called a business use case,
is a simplified, abstract, generalized use case that captures the intentions of a user in a
technology and implementation independent manner. A fully documented essential use case is a
structured narrative, expressed in the language of the application domain and of users,
comprising a simplified, abstract, technology-free and implementation-independent description
of one task or interaction.
20
DMU
Register Criminal and Civil Case

Information Desk
Customer
Record/store any Case

Crime Judge
Record officer
Give Appointment
Civil Judge
Generate Report
Manager
Fig 2.1 Essential Use Case Model
21
DMU
2.1.8 Essential use case description
Name:
Register Criminal and civil case
ID
UC1
Actors
Description
Information desk, Customer
Precondition
Post
condition
Basic Course
of Action
22
The customer who have case can register into the file
The customer provide the necessary data to information desk
The customer is registered
1.
2.
3.
4.
The customer request for registration.

The Information desk gives the customer registration form
The customer fills the prepared form.
The Information desk registers the customer into the file.
DMU
5. End of use case

If the information is invalid or incomplete
Alternate
Course of
Action
The Information desk asks the customer to fill the appropriate information.
The Resident fills the appropriate information on the form.
The use case continues from step 4
Table 2.3 Register Criminal Case
Name:
Register Civil case
ID
UC2
Actors
Description
Precondition
Post
condition
Basic Course
of Action
Alternate
23
1.
2.
3.
4.
5.
The customer request for registration.

The Information desk gives the customer registration form
The customer fills the prepared form.
The Information desk registers the customer into the file.
End of use case
DMU
The Resident fills the appropriate information on the form.
Course of
Action
Table 2.4 Register Civil Case
Name:
Generate Report
ID
Actors
UC3
Record officer
Description
The Record Officer generates different types of reports for the top manager.
Pre condition
A particular period of time to generate the report
Post
condition
Basic Course
of Action
Generated report
24
1.the record office collects information about the services given within some
period of time(daily, monthly, yearly)
DMU
2. the record officer generates the report

Table 2.5 Generate Report
2.2 Requirements definition

The requirement definition actually is the System Requirements Specification (SRS).In this
section I have kept the basic understanding of the requirements and dependencies of the current
system prior to any actual design or development work. Its a two way insurance policy that
assures that both the client (court) and I understand the others requirements from that
perspective at a given point in time.
A well-designed, well-written SRS accomplishes four major goals:
It provides feedback to the customer. An SRS is the customer's assurance that we have
understood the issues or problems to be solved and the software behavior necessary to
address those problems.
It decomposes the problem into component parts. The simple act of writing down
software requirements in a well-designed format organizes information, places borders
around the problem, solidifies ideas, and helps break down the problem into its
component parts in an orderly fashion.
It serves as an input to the design specification. The SRS serves as the parent document
to subsequent documents, such as the software design specification and statement of
work. Therefore, the SRS must contain sufficient detail in the functional system
requirements so that a design solution can be devised.
It serves as a product validation check. The SRS also serves as the parent document for
testing and validation strategies that will be applied to the requirements for verification.
Citation:
[http://www.techwr-l.com/techwhirl/magazine/writing/softwarerequirementspecs.html]
2.2.1 Functional Requirements
Functional requirements are capture intended behavior of the system. This behavior may be
expressed as services, tasks or functions the system is required to perform.
25
DMU
Citation: [http://www.bredemeyer.com/pdf_files/functreq.pdf]
Since I am going to develop an automating services that are given to the users , the system will
be used to manage and process data according to the rule & regulations of the organization. It
will also provide report generation facilities. The database of the system provides the following
functionality.
Data entry:
This is the functionality that data is entered to the systems. The system serves
different interface that can manage data entry mechanisms in the Debre markos city
woreda legal system.
The main data entries are the following:
Civil Case Registration
Criminal Case Registration
Data update
Login
Search information
Data processing
The system on input data will provide the following data processing:
Report generation
Validate user
Search user request
Report generation
Generate report
Total number of cases in each bench i.e Civil case and Criminal
case
2.2.2 Non-Functional Requirements
Non-functional requirement is a requirement that specifies criteria that can be used to judge the
operation of a system, rather than specific behaviors. This should be contrasted with functional
requirements that define specific behavior or functions.
In general, functional requirements define what a system is supposed to do whereas nonfunctional requirements define how a system is supposed to be. Non-functional requirements are
often called qualities of a system. Other terms for non-functional requirements are "constraints",
26
DMU
"quality attributes", "quality goals" and "quality of service requirements". Qualities, that is, nonfunctional requirements, can be divided into two main categories:
1. Execution qualities, such as security and usability, which are observable at run time.
2. Evolution qualities, such as testability, maintainability, extensibility and scalability, which are
embodied in the static structure of the software system.
Security
In order to make the system safe from an authorized access and modification, the system uses a
log in account to differentiate among the different users of the system on the organization side.
This enables the system to verify who has logged in using the correct logging account provided
and display the right form associated with that user.
Access is controlled through proper password and username verification facilities which the
database and the server require. The security service provided by the system will maintain the
security, confidentiality and integrity of the system. Users will have their own password and
username through which they could gain access to. The password with which user are provide
will protect them from potential threats, who could jeopardizing their responsibility in an
organization. Generally this system is confidentially secured.
Citation: [www.duke.edu/../authvauth.html]
The proposed system provides authorization facilities by determining whether a user is
authorized to access a resource, a user is authorized to perform an operation and a user is
authorized to perform operation on a resource.
Usability
Usability is a term used to denote the ease with which people can employ a particular tool or
other human-made object in order to achieve a particular goal. Usability can also refer to the
methods of measuring usability and the study of the principles behind an object's perceived
efficiency or elegance.
In human-computer interaction and computer science, usability often refers to the elegance and
clarity with which the interaction with a computer program or a web site is designed. The term is
also used often in the context of products like consumer electronics, or in the areas of
communication, and knowledge transfer objects (such as a cookbook, a document or online
help). It can also refer to the efficient design of mechanical objects such as a door handle or a
hammer. Usability differs from user satisfaction insofar as the former also embraces usefulness
27
DMU
The primary notion of usability is that an object designed with a generalized users' psychology
and physiology in mind is, for example:
More efficient to useit takes less time to accomplish a particular task

Easier to learnoperation can be learned by observing the object
More satisfying to use
Backup
A backup or the process of backing up refer to making copies of data so that these additional
copies may be used to restore the original after a data loss event. These additional copies are
typically called "backups."
Backups are useful primarily for two purposes. The first is to restore a state following a disaster
(called disaster recovery). The second is to restore small numbers of files after they have been
accidentally deleted or corrupted. Data loss is also very common. 66% of internet users have
suffered from serious data loss.
2.2.3 Essential user interface prototyping
The user interface (UI) is the portion of software with which a user directly interacts. An
essential user interface prototype (Constantine and Lockwood 1999), also known as an abstract
prototype or paper prototype, is a low-fidelity model, or prototype, of the UI for your system. It
represents the general ideas behind the UI, but not the exact details. Essential UI prototypes
represent user interface requirements in a technology independent manner, just as essential use
case models do for behavioral requirements. An essential user interface prototype is effectively
the initial state the beginning point of the user interface prototype for your system. It models user
interface requirements, requirements that are evolved through analysis and design to result in the
final user interface for your system, enabling you to explore usability aspects of your system.
Citation:[http://www.agilemodeling.com/artifacts/essentialUI.htm]
Defendant_full_Name
Date
date
File_number:
28
DMU
Input field
Used to identify each customer
Plaintiff_full_name
Input fields first name, middle name, last name
Defendant_address
Input field
Defendant_sex
Fig.2.2 Civil case registration
Fig 2.2 Crime case registration form
Date
Defendant_address
date
File_number:
Input
29field
Used to identify each customer
Input field
Defendant_sex
Input field
Defendant_age
Plaintiff_full_name
Input fields includes first name,
Input field
DMU
Fig 2.5 criminal case registration from
Fig.2.3 Civil case registration from
Fig.2.3 Criminal case registration
File_number
Input field
Eid
Input field
30 Prepared by Abatneh Shiferaw
Appointment_date
Input field
Summary of the decision
Input field
DMU
Fig 2.5 Give appointment
Fig.2.4Appointment registration
Password
Input field
User name
Input field
Eid
Fig 2.5 Create Account
Input field
Fig.2.5Account registration
Chapter 3
3 OBJECT ORIENTED DESIGN
During object-oriented design (OOD), a developer applies implementation constraints to the

conceptual model produced in object-oriented analysis. Such constraints could include not only
constraints imposed by the chosen architecture but also any non-functional technological or
environmental constraints, such as transaction throughput, response time, run-time platform,
31
DMU
development environment, or those inherent in the programming language. Concepts in the

analysis model are mapped onto implementation classes and interfaces resulting in a model of
the solution domain, i.e., a detailed description of how the system is to be built.
3.1 System Use Case

A System Use Case is one in which the design scope is the computer system to be designed. It is
about an actor achieving a goal with the computer system; it is about technology.
Citation:[ http://pjhobday.wordpress.com/2010/05/08/business-and-system-use-cases/]
3.1.1. User Interface Identification

ID
User Interface
Used by
UI1
UI2
UI3
UI4
UI5
UI6
UI7
Criminal case register form

Civil case register form
Login form
Give appointment form
Generate report
Judge registration form
Create Account from
Information desk
Information desk
Record officer
Judges
Record officer
Record officer
Record officer
Table 3.1 User Interface Identification
3.1.2 Business Rule Identification

Business rules (Julio Cesar Sampaio do Prado Leite) are statements about the enterprises way of
doing business. They reflect business polices. Organizations have policies in order to: satisfy the
business objectives, satisfy customers, make good use of resource, and conform to laws or
general business conventions.
Name:-loan money Statement of claim
32
DMU
Id: - BR1
Description:
The claim person must have real evidence to loan money to him/her
The claim person must came the file that contains the agreement of between them about
the loan of money
Name:-Claim for divorce request

Id: - BR2
Description:
Name:-Successor certificate claim request

Id: - BR3
Description:
Successor have evidence that checks the child of died person

Him/her show when and where the father and mother die
They should come person that knows the child of the died person
Successor/s should signed
Name:-Maintenance claim request

Id: - BR4
Description:
Maintenance requester have evidence the relationship between maintenance requestor

and maintenance give person
The maintenance request age should be under 18
Maintenance request should signed
Name:- Divorce by agreement and effects of divorce approved claim request

Id: - BR5
33
DMU
Description:
Attach their divorce by agreement document
Both of them should be signed
Name:-Appeal request from

Id: - BR6
Description:
Him/her case is should have been closed

Ask the appeal by their signature
3.1.3. Actors Identification

1.Information case
2.criminal judges
3.Customer
4 Record office
5.civil judges
6.Top manager
Table 3.2 Actors Identification
3.1.4. Use Case Identification

ID
UC1
Use Case Name

Criminal case register form
34
Include/use
UC1
DMU
UC2
UC3
Civil case register form

Login form
UC1
UC3
UC4
Give appointment form
UC4
UC5
Generate report
UC5
Table 3.2 Use Case Identification
3.1.5. Designing the System Use Case Diagram

An essential use case (Constantine and Lockwood 1999), sometimes called a business use case, is a simplified,
abstract, generalized use case that captures the intentions of a user in a technology and implementation independent
manner. A fully documented essential use case is a structured narrative, expressed in the language of the application
domain and of users, comprising a simplified, abstract, technology-free and implementation-independent description
of one task or interaction. An essential use case is complete, meaningful, and well designed from the point-of-view
of users in some role or roles in relation to a system and that embodies the purpose or intentions underlying the
interaction.
Citation:[http://www.agilemodeling.com/artifacts/essentialUseCase.htm ]
Register Criminal and Civil Case

Information Desk
Customer
Record/store any Case

Crime Judge
Record officer
Give Appointment
Civil Judge
Generate Report
Manager
Login
Fig. 3.1 System Use Case Diagram
35
DMU
36
DMU
3.1.6. Use Case Description

In this part of the project I described the use cases that are identified in the use case
identification and also drawn on Fig 3.1.
Name:
Login
ID
UC4
Record officer, Manager, Customer, Civil and crime judges

Actors
Description
Users They can login by his/her account
Pre-condition They should have account
Post
condition
They are authenticated and taken to their own user interface
Basic Course
of Action
1.They opens the system

2.The system display login interface
3.They inputs valid user name, password
4. The system validates the account and displays the required interface
5.use case ends
Alternate
Course of
Action
If the login name or password is invalid
The system displays invalid user name or password message

The user reenters the user name and password
Table 3.3 Login Use Case Description
37
DMU
Name:
Register Criminal and civil case
ID
Actors
UC1
Description
Precondition
Post
condition
Basic Course
of Action
Alternate
Course of
Action
6. The customer request for registration.

7. The Information desk gives the customer registration form
8. The customer fills the prepared form.
9. The Information desk registers the customer into the file.
10. End of use case
The customer fills the appropriate information on the form.
Table 3.4 Register criminal and civil case use case description
38
DMU
Name:
Generate Report
ID
Actors
UC3
Record officer
Description
The Record Officer generates different types of reports for the top manager.
Pre condition
The record officer collects d/t report
Post
condition
Generated report
Basic Course
of Action
1.the record office collects information about the services given within some
period of time(daily, monthly, yearly)
2. the record officer generates the report
Table 3.6 Generate Report use case description
3.2. Sequence Diagramming

UML sequence diagrams are used to represent or model the flow of messages, events and actions between the
objects or components of a system. Time is represented in the vertical direction showing the sequence of interactions
of the header elements, which are displayed horizontally at the top of the diagram.
Sequence Diagrams are used primarily to design, document and validate the architecture, interfaces and logic of the
system by describing the sequence of actions that need to be performed to complete a task or scenario. UML
sequence diagrams are useful design tools because they provide a dynamic view of the system behavior which can
be difficult to extract from static diagrams or specifications.
Citation:[http://www.sequencediagrameditor.com/uml/sequence-diagram.htm]
39
DMU
Information desk, customer

<Actor>
Register criminal case

<UI>
Validator
Fill_infprmation
Open

<UI>
validator
Submit
Criminal case details
OpenAdminpage
Alternative action:
Informatin desk,customer
<Actor>

<UI>
Validator
register criminal case

<UI>
Fiil_information
validator
submit
Open
Error
ErrorMessage
Figure 3.2 Sequence diagram for Register criminal case
40
DMU
Information desk, customer

<Actor>
Register ccivill case

<UI>
Validator
Register civil case

<UI>
Fill_infprmation
validator
Open
Submit
Criminal case details
displaysuccessMessage
Alternative action:
Information desk, Store

man
<Actor>
Register civil case

<UI>
Register civil case

<UI>
Validator
Fiil_information
validator
Submit
Open
Error
ErrorMessage
Figure 3.3 Sequence diagram for Register civil case
41
DMU
Store man
<Actor>
Login Page
<UI>
Admin_Page
<UI>
Validator
Enter(UN and PW)
validator
Open
Login
Admin_Page
OpenAdminpage
Alternative action:
Store man
<Actor>
Login Page
<UI>
Admin_Page
<UI>
Validator
Enter(UN and PW)
validator
Open
Login
Error
ErrorMessage
Figure 3.4 Sequence diagram for login
42
DMU
3.3. Activity Diagrams

In UML, an activity diagram is used to display the sequence of activities. Activity diagrams show the
workflow from a start point to the finish point detailing the many decision paths that exist in the
progression of events contained in the activity. They may be used to detail situations where parallel
processing may occur in the execution of some activities. Activity diagrams are useful for business
modeling where they are used for detailing the processes involved in business activities.
Citation:[http://www.sparxsystems.com.au/resources/uml2_tutorial/uml2_activitydiagram.html]
Fill username and password
Select user type

Click on login button
Invalid
Valid
System display
main page
Click on civil case button

/
system display civil case registration form
fill the form

Invalid
Valid
You are successfuly regsitered
Figure 3.5 Activity diagram for civil case registration
43
DMU
Fill username and password
Select user type

Click on login button
Invalid
Valid
system displays main page
Click on criminal case button/
system display criminal case registration form
fill the form

Invalid
Valid
You are successfuly regsitered
Figure 3.6 Sequence diagram for criminal case registration
44
DMU
3.4. Class Diagram

In software engineering, a class diagram in theUnified Modeling Language (UML) is a type of static
structure diagram that describes the structure of a system by showing the system's classes, their attributes,
operations (or methods), and the relationships among the classes.
Citation:[ http://en.wikipedia.org/wiki/Class_diagram]
Civil_case
Criminal_case
-+date
-+file_number
-+Plentiff_full_name
-+plentiff_address
-+pelntiff_sex
-+plentiff_age
-+Defendant_full_name
-+Defendant_addres
-+Defendant_sex
-+Defendant_age
-+Fact_of_cliam
-+Relief_sout
+Add()
+Update()
+Search()
+Delete()
m:m
m:m
1:1
Appointment
m:m
-+File_number
-+Employee_id
-+Appoinment_date
-+Summery_of_the_decision
-+New_id
+Add()
+Search()
+Delete()
+Update()
1:1
m:m
-+FIle_number
-+Plentiff_full_name
-+Plentiff_address
-+Plentiff_sex
-+plentiff_age
-+defendant_full_name
-+defendant_address
-+defendent_age
-+fact_of_cliam
-+Relief_sout
-+date
-+defendant_sex
+Add()
+Search()
+Delete()
+Upate()
1:m
1:1
Judge
-+Employee_id
-+Full_name
-+Age
-+Sex
+Add()
+Search()
+update()
+Delete()
Account
-+User_name
-+Passord
-Employee_id
+Add()
+Search()
+Delete()
+Update()
Figure 3.7 class diagram
45
DMU
3.4.1. Description of Class Diagram
Class name: account

Attributes:
Employee-id
-
Unique identification of judge.

It has character data type.
Max-size 8
User-name
- It uniquely identifies the user name of users.
- It has string data type.
- Max-size 20.
Password
-
Validate identification of user of access page.

It has string data type.
Max-size 15.
Method:
Create ()
- It is used to create password and user name of user.
- Parameter: username and password.
Delete ()
Update()
46
It is used to deletepassword of user.

Parameter: Password and user name
DMU
- Used to update users account

Class name: Judge
Attributes:
Employee-id
- Unique identification of judge.
- It has character data type.
- Max-size 8
Full_Name:
- It identify first, middle and last name of judge.
- Max-size 25.
Age:
- It tells us the age of judge.
- It has integer data type.
Sex:
- It identifies the sex of judge.
- Max-size 6.
Methods:
Add()
- Used to register judges
Delete()
- Used to delete judges
Update()
- Used to update judges
Search()
- Use to search judges
Class name: Criminal
case
Attributes:
Date
-
47
Used to specify the date that the case is started.

Date/time
DMU
File_No
- Unique identification of case.
- Max-size 8.
Plaintiff_Full_Name
- It identify first, middle and last name of plaintiff.
- Max-size 30.
Plaintiff_Address
- It identifies the address of the plaintiff
- It has character data type
- Max-size 20.
Plaintiff-Sex:
- Max-size 6.
Plaintiff-age:
- It tells us the age of plaintiff.
Defendant_Full_Name
- It identify first, middle and last name of defendant.
- Max-size 30.
defendant_Address
- It identifies the address of the defendant
- Max-size 20.
defendant-Sex:
- It identifies the sex of defendant.
- Max-size 6.
defendant-age:
-
48
It tells us the age of defendant.

DMU

Fact_of_the_claim
- It identifies clearly about the main point of the claim
- It is text-area
Relief_sout
- It is text-area
Methods:
Add()
- Used to register any civil cases
Delete()
- Used to delete the case
Update()
- Used to update the case
Search()
- Use to search cases
Class name: Civil
case
Attributes:
Date
File_No
Used to specify the date that the case is started.

Date/time

- Max-size 8.
Plaintiff_Full_Name
- It identify first, middle and last name of plaintiff.
- Max-size 25.
Plaintiff_Address
- It identifies the address of the plaintiff
- Max-size 20.
49
DMU
Plaintiff-Sex:
- Max-size 6.
Plaintiff-age:
- It tells us the age of plaintiff.
Defendant_Full_Name
- It identify first, middle and last name of defendant.
- Max-size 25.
defendant_Address
- It identifies the address of the defendant
- Max-size 20.
defendant-Sex:
- It identifies the sex of defendant.
- Max-size 6.
defendant-age:
- It tells us the age of defendant.
Fact_of_the_claim
- It is text-area
Relief_sout
- It is text-area
Methods:
Add()
- Used to register the case
Delete()
- Used to delete the case
50
DMU
Update()
- Used to update the case
Search()
- Use to search cases
Class name: Appointment
Attributes:
File_No
- Max-size 8.
Employee-id
- Unique identification of judge.
- Max-size 8
Appointment Date
- Used to specify the appointment of the case
- Date/time
Summery_of_the_decision
- It describes the decision of the case
- It has string data type
- Max-size var(max)
3.5. User Interface Prototyping

User interface (UI) prototyping (Ambler 2004) is an iterative development technique in which
users are actively involved in the mocking-up of the UI for a system.
51
DMU
D
A
C
Figure3.8 Login screen
Letter AIndicates selection of user type (record officer, manager, customer, Judge)
52
DMU
Letter Bindicates input box for user name

Letter C indicates input box for password
Letter D indicates go to the page based on the inputs
Letter E indicates close the page
Figure 3.9 Record officer page
53
DMU
54
DMU
Figure 3.10 Manager page
55
DMU
Figure 3.11 judge registration page
Chapter 4
4.1. Conclusion
In this project is aimed at developing automated system for Debre markos city woreda legal system where
ICTs intervention is required.
In chapter 1 I determined the title of the project to be Debre markos city woreda legal system. I described
the background of the organization, the problems of the existing system, the scope and limitation of the
project, feasibility and schedule of the project have been discussed including the methodology of the
project.
In Chapter 2 In business area analysis I identified the problems of the current system, the forms and
reports of the existing system. Then I used an essential use case to model the features of the existing
system by identifying actors and use cases. After business area analysis I determined the requirements of
the proposed system in terms of functional and non-functional requirements. Finally, I did a user interface
prototyping that describes the user interface requirements in a technology independent manner.
The third chapter of the project discussed about the object oriented analysis which tries to produce the
conceptual model of information for the problem domain that raised on the chapter one of the existing
system and solve that problem. To accomplished this, I used different types of object oriented analysis
tools like system use case, different diagram such as sequence diagram , class diagram and activity
diagram.
References
1.
2.
3.
4.
5.
6.
http://www.techwr-l.com/techwhirl/magazine/writing/softwarerequirementspecs.html
http://www.bredemeyer.com/pdf_files/functreq.pdf
www.duke.edu/../authvauth.html
http://www.agilemodeling.com/artifacts/essentialUI.htm
56
DMU
7. http://pjhobday.wordpress.com/2010/05/08/business-and-system-use-cases
8. http://www.sequencediagrameditor.com/uml/sequence-diagram.htm
9. http://www.sparxsystems.com.au/resources/uml2_tutorial/uml2_activitydiagram.html
57
DMU

Developing An Automated System Fordebre Markos Woreda Legal

Uploaded by

Document Information

Original Description:

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

Developing An Automated System Fordebre Markos Woreda Legal

Uploaded by

Copyright:

Available Formats

DEBRE MARKOS UNIVERSTY

Developing an automated system

Prepared by Abatneh Shiferaw

Prepared by Abatneh Shiferaw

Prepared by Abatneh Shiferaw

1.7 Feasibility Analyses ...................................................................................................................... 11

Prepared by Abatneh Shiferaw

3.1.2 Business Rule Identification ...................................................................................................... 32

Prepared by Abatneh Shiferaw

To prevail the justice

1)Maintain good governance in which effectiveness, transparency and accountability, to the

Prepared by Abatneh Shiferaw

2)Create favorableconditions of living and work as well as to facilitate conditions in which

1.1.6 Organizational structure

Prepared by Abatneh Shiferaw

Figure 1. Organizational structure

The legal system is engaged the following main activities.

1.2 Statement of the problem

Prepared by Abatneh Shiferaw

1.3.Objective of the project

1. Speed up the legal system by providing convenient file handling

1.4.Significance of the new system

Makes information easily accessible

Prepared by Abatneh Shiferaw

1.5.Scope and limitation of the project

Record newly arrived civil cases

Prepared by Abatneh Shiferaw

1.6.2 Programming and Database Tools

Prepared by Abatneh Shiferaw

Used to make UML diagrams

Prepared by Abatneh Shiferaw

Table 1. Budget schedule

1.7.1.1.2 Intangible cost

These costs can be estimated in money terms

Prepared by Abatneh Shiferaw

These benefits cannot be estimated in money terms

Prepared by Abatneh Shiferaw

Table 1.1 project time table

Prepared by Abatneh Shiferaw

Record new civil cases

Prepared by Abatneh Shiferaw

Information (and Data)

Prepared by Abatneh Shiferaw

The system is inflexible to change

2.1.3 Forms and Reports Currently Used

/ Statement ofcrime claim from

Table 2.1 Forms of the existing system

Is part of the computerized system?

Table 2.2 Users of the existing system

Prepared by Abatneh Shiferaw

Name:-loan money Statement of claim

Name:-Claim for divorce request

Name:-Successor certificate claim request

Successor have evidence that checks the child of died person

Prepared by Abatneh Shiferaw

Name:-Maintenance claim request

Maintenance requester have evidence the relationship between maintenance requestor

Name:- Divorce by agreement and effects of divorce approved claim request

Name:-Appeal request from

Him/her case is should have been closed

2.1.6 Use Diagrams

Prepared by Abatneh Shiferaw