court information management system for somaliland...
TRANSCRIPT
COURT INFORMATION MANAGEMENT SYSTEM
FOR
Somaliland Attorney General Office
2017
COURT INFORMATION MANAGEMENT
SYSTEM
A REPORT SUBMITTED IN PARTIAL FULFILLMENT OF THE
REQUIREMENTS FOR THE BACHELOR OF SCIENCE IN SOFTWARE
ENGINEERING
By:
Rahma Ismail Ahmed
Ayan Hussein Abdi
Project Supervisor: [AWIL AHMED MOHAMED]
FACULTY OF SOFTWARE ENIGNEERING
ABAARSO TECH UNIVERSITY
2017
DECLARATION
We declare that this submission is our own work and that it contains no material previously
published or written by another person nor material which to a substantial extent has been
accepted for the award of any other degree or diploma of the university or other institute of
higher learning, except where due acknowledgment has been made in the text.
Rahma Ismail Ahmed
Ayan Hussein Abdi
Name and signature of candidate
Faculty of Software engineering
Abaarso Tech University
2017
Court information management system
2
Approval Sheet
We confirm that the work reported in this dissertation was carried out by the candidate under
our supervision.
Awil Ahmed Mohamed
Name of Supervisor Signature of Supervisor
Mukhtar Elmi Omar
Name of Supervisor Signature of Supervisor
Faculty of Software engineering
Abaarso Tech University
2017
Court information management system
3
ACKNOWLEDGEMENT
We are grateful to Allah for the good health and wellbeing to complete this project
documentation. We must pay immense honor to our professors and in a particular manner our
supervisors Lecturer Awil Ahmed Mohamed and Prof Mukhtar Elmi Omar who
encouraged us to finish and bent this precious thesis and our Prof Mohamed Daud the dean
of computer sciences department. We convey our infinite thanks to our beloved fathers and
mothers to their countless of support which reflects moral and financial assistant.
After that we would like to thank staffs of attorney general office Mr. Ali Mohamed Ali and
Mr. Mohamed Hussein Aided. For their kind of help and providing us, whatever materials
and requirements of our project or thesis and we are thanking to all staffs of attorney general
office who are the key of information of our project and they give more information about the
project.
Court information management system
4
ABSTRACT
This documentation is about the project carried out in order to fulfil the requirements of the
final year project of the B.SE in computer science. It is all about the development project, court
information and management system which was developed for Somaliland Attorney General
Office.
Court information management system was developed to make the functioning areas of
Attorney General Office more efficient and effective. One of the main concepts of this project
is to provide good and easier services to the staffs and reduce over works in the office.
In this documentation the method of analysis, design and testing are documented. This project
has used unified software development and object oriented techniques along with the unified
modeling language.
This information system is developed using database environment of SQL server. The front
end is developed using Csharp.net frame work. The system is window application.
Court information management system
5
INDEX
TITLE PAGE……………………………………………………………………………..
DECLARETION A ……………………………………………………………………….
DECLARETION B ……………………………………………………………………….
ACKNOWLEDGEMENT………………………………………………………………...
ABSTRACT……………………………………………………………………………….
TABLE OF CONTENTS………………………………………………………………….
LIST OF TABLES…………………………………………………………………………
LIST OF FIGURES………………………………………………………………………..
REFFERCE………………………………………………………………………………..
APPENDIX………………………………………………………………………………..
Court information management system
6
TABLE OF CONTENTS
CHAPTER ONE: INTRODUCTION
1.0 Introduction……………..........................................................................................13
1.1 Background……………..........................................................................................13
1.2 Problem Statement.........................................................................................13 1.3 Objectives of the project……………......................................................................14
1.3.1 General objective..................................................................................................14
1.3.2 Specific objectives................................................................................................14
1.4 Project Scope and Limitation...................................................................................14
1.4.1 Project Scope.........................................................................................................14
1.4.2 Data collection.......................................................................................................14
1.5 Significance of the project........................................................................................15
1.6 Risk assessment and management……………........................................................15
1.7 Operating and Development Environment……………...........................................15
CHAPTER TWO: LITERATURE REVIEW
2.0 Introduction...............................................................................................................16
2.1 The main activities....................................................................................................16
2.2 Functions of the existing system...............................................................................16
2.3 Players of the existing system...................................................................................16
2.4 Report generating in the existing system..................................................................16
2.5 Documents used in the existing system……………................................................16
2.6 Weakness of the existing system……………..........................................................16
2.7 Strength of the existing system….............................................................................17
2.8 Feasibility study........................................................................................................17
2.8.1 Economical feasibility............................................................................................17
2.8.1.1 Cost Benefit Analysis……………......................................................................17
2.8.2 Technical Feasibility……………...........................................................................18
2.8.3 Time Feasibility……………..................................................................................18
CHAPTER TTHREE: Requirement Specification, Analysis and
Methodology
3.0 Introduction……………..........................................................................................19
3.0.1 Purpose……………..............................................................................................19
3.0.2 Intended audience and reading suggestions……………......................................19
3.0.3 Document convention…………….......................................................................19
3.1 Objective……………..............................................................................................19
3.2 Functional requirement……………........................................................................19
3.3 Product prospective……………..............................................................................19
3.4 Product function……………...................................................................................20
3.5 Principal actors…………….....................................................................................20
Court information management system
7
3.6 User Characteristics……………..............................................................................20
3.7 General Constraints……………..............................................................................20
3.8 Assumptions and Dependencies……………...........................................................20
3.9 Non-functional Requirements……………...............................................................21
3.10 system mode……………........................................................................................21
3.10.1 Use case diagram……………..............................................................................22
3.10.2 Use case description…………….........................................................................23
3.10.3 Activity diagram……………...............................................................................23
3.10.4 Sequence diagram…………….............................................................................24
3.11 methodologies……………......................................................................................25
3.11.1 Advantages of OOAD with UML Methodology……………..............................25
3.11.2 Software Requirement……………......................................................................25
3.11.21Tools/ Design and Development Tools……………...........................................25
3.11.3 Hardware Requirement…………….....................................................................25
CHAPTER FOUR: System design/ Analysis and testing
4.0 Introduction……………..........................................................................................26
4.1 Design Goals……………........................................................................................26
4.1.1 Performance Criteria…………….........................................................................26
4.1.2 Dependability……………....................................................................................26
4.1.3 Maintenance Criteria…………….........................................................................26
4.1.4 End-user criteria……………................................................................................26
4.2 System Architecture…………….............................................................................27
4.3 Screen……………...................................................................................................27
CHAPTER FIVE: Implementation and testing
5.0 Introduction……………........................................................................................39
5.1 Implementation……………...................................................................................39
5.2 Database Implementation……………...................................................................39
5.3 Application Implementation……………...............................................................40
5.4 Testing……………................................................................................................58
5.4.1 Software testing……………...............................................................................58
5.4.2 Testing objectives include……………...............................................................58
5.4.3 Testing methodologies…………….....................................................................58
5.4.3.1 Testing strategies……………..........................................................................58
5.4.3.2 Unit testing……………....................................................................................58
5.4.3.3 Integration test……………..............................................................................58
5.4.3.4 Validation testing……………..........................................................................59
5.4.3.5 System testing……………...............................................................................59
5.4.3.6 Security testing……………..............................................................................59
5.4.3.7 Performance testing…………….......................................................................59
Court information management system
8
CHAPTER SIX: Conclusion and recommendations
6.0 Conclusion and Recommendation…………….......................................................60
Court information management system
9
LIST OF TABLES
Table 2.1 Office existing system cost per year……………………………………….17
Table 2.2 Office current system cost per year………………………………………..17
Table 3.1 Use case description……………………………………………………….23
Court information management system
10
LIST OF FIGURES
Figure 3.1 system use cases………………………………………………………….…..22
Figure 3.2 Activity diagram………………………………………………………….…..23
Figure 3.3 Sequence diagram……………………………………………………….........24
Figure 4.1 Splash Form………………………………………………………………......27
Figure 4.2 Login Form……………………………………………………………………27
Figure 4.3 Menu strip Form………………………………………………………………28
Figure 4.4 Nooca Danbiga Form……………………………………………………........28
Figure 4.5 Eedaysanayasha Noocan Danbiga Form………………………………...........29
Figure 4.6 Eedaysane Form…………………………………………………………........29
Figure 4.7 Ku dar Eedaysane Form…………………………………………………........30
Figure 4.8 Dibu eeg eedaysane Form……………………………………………….........30
Figure 4.9 Dhibane Form……………………………………………………………........31
Figure 4.10 Ku dar Dhibane Form………………………………………………………..31
Figure 4.11 Dibu eeg dhibane Form……………………………………………………...32
Figure 4.12 Saldhig Form………………………………………………………………...32
Figure 4.13 Ku dar saldhig Form…………………………………………………….......33
Figure 4.14 Dibu eeg Saldhig Form………………………………………………….......33
Figure 4.15 Shaqaale Form………………………………………………………….........34
Figure 4.16 Ku dar Shaqaale Form…………………………………………………….....34
Figure 4.17 Dibu eeg shaqaale Form……………………………………………………..35
Figure 4.18 Gal Form……………………………………………………………………..35
Figure 4.19 Ku dar gal form……………………………………………………………....36
Figure 4.20 Dibu eeg gal form…………………………………………………………….36
Figure 4.21 Warbixin eedaysane Form…………………………………………………....37
Figure 4.22 Warbixin guud Form………………………………………………………….37
Figure 4.23 Warbixin gal form………………………………………………………….…38
Figure 5.1 Database diagram………………………………………………………………40
Figure 5.2 Loading/splash form…………………………………………………………....41
Figure 5.3 Login form……………………………………………………………………...41
Figure 5.4 Main form……………………………………………………………………....42
Figure 5.5 Remove nooca anbiga…………………………………………………………..43
Figure 5.6 Insert nooca danbiga……………………………………………………………43
Figure 5.7 Edit nooca danbiga……………………………………………………………..44
Figure 5.8 Eedaysanaha noocan danbiga form…………………………………………….44
Figure 5.9 Search eedaysane……………………………………………………………….45
Figure 5.10 remove eedaysane……………………………………………………………..45
Figure 5.11 Edit eedaysane………………………………………………………………...46
Figure 5.12 Insert eedaysane………………………………………………………………46
Figure 5.13 Search Dhibane……………………………………………………………….47
Figure 5.14 Insert Dhibane………………………………………………………………...47
Figure 5.15 Edit Dhibane………………………………………………………………….48
Figure 5.16 Edit Dhibane………………………………………………………………….48
Figure 5.17 Search saldhig………………………………………………………………...49
Figure 5.18 Edit saldhig……………………………………………………………………49
Figure 5.19 Remove saldhig……………………………………………………………….50
Court information management system
11
Figure 5.20 Insert saldhig……………………………………………………………….50
Figure 5.21 Search shaqaale…………………………………………………………….51
Figure 5.22 Insert shaqaale……………………………………………………………...51
Figure 5.23 Edit shaqaale……………………………………………………………….52
Figure 5.24 Remove shaqaale…………………………………………………………..52
Figure 5.25 Search gal………………………………………………………………......53
Figure 5.26 Insert gal……………………………………………………………………53
Figure 5.27 Edit gal……………………………………………………………………...54
Figure 5.28 Remove gal…………………………………………………………………54
Figure 5.29 Search warbixinta eedaysane……………………………………………….55
Figure 5.30 Report generated by warbixinta eeadaysanayaasha………………………...55
Figure 5.31 Warbixinta Galka…………………………………………………………...56
Figure 5.32 Report generated by warbixinta galka………………………………………56
Figure 5.33 Warbixinta guud…………………………………………………………….57
Figure 5.34 Report generated by warbixinta guud……………………………………….57
Court information management system
12
REFFERCE REFFERCE…….……………………………………………………………………….61
APPENDIX
Appendix A………………………………………………………………………………...62
Appendix B………………………………………………………………………………...62
Court information management system
13
CHAPTER ONE
PROBLEM AND SCOPE
1.0 Introduction
This chapter covers the background, statement of the problem, objectives of the project, project
scope and limitations, significance of the project, risk assessment and management and
operating and development environment, this study will be occur for Somaliland Attorney
General Office Hargeisa, Somaliland.
1.1 Background Somaliland Attorney General Office is mandated for the prosecution of criminal cases as well
drafting criminal laws. Somaliland had its own judicial system headed by High Court in
Hargeisa until 1960. On independence, as the short lived State of Somaliland, the 1960
Somaliland Constitution re-confirmed the existing Somaliland judicial system but suspended
the appeals to the East African Appeal Court. In 2010 the active working offices in regions
was only confined to Hargeisa and Buroa but they don’t have offices to work and staff. The
Working Deputies and Prosecutors was less than 12 with no legal educational background and
the number of the female prosecutors was zero. Cases involving SGBVE and Juvenile cases
were used to be solved in a traditional way with no case management.
In this last five years Attorney General Office establishes and equipment of SGBV and Juvenile
dedicated unites to the four main regions of Hargeisa, Buroa, Berbera and Gabiley. Prohibit
the SGBV cases to be solved in traditional way by making regulation criminalizing the
traditional involvement. Also recruit 28 female Deputies which all has been distributed to
regions and now work on SGBV, Juviniel cases as well as other assaults and restructure the
office by tailoring it with the current needs because before it was structured as Attorney General
and Deputies.
As key result Attorney General Office improves the prosecution of sexual offences and juvenile
cases. Introducing and implementing of the case management reform in Hargeisa, Berbera,
Borama and Buroa regions. Establishes working juvenile departmental offices in Berbera,
Borama and Hargeisa regions and availability of female prosecutors in all Somaliland regions.
Also willing to construct working space for Berbera, Gabiley and Erigavo regional prosecution
offices. Also continue supporting implementation of the case management systems reform and
introduce automated construction of Working Space for Berbera, Gabiley and Erigavo regional
prosecution offices.
1.2 Statement of the problem
Attorney General Office uses only one form information system. That form used for
registration of the final draft which is called (GAL) and submitted to the court. But all other
information’s stored manually by using traditional files which leads to vital problems like file
misplacement and lose which means the current system do not guarantee the privacy and
confidential of the data that exposes the data and reduces data integrity.
Court information management system
14
The new system will impose manually stored data by providing well designed and secured
database and keep track of data flaw. Also it will guarantee the security of the data by using
passwords to access the data.
1.3 Objectives of the project
1.3.1 General Objectives
This information system will execute all data of the Attorney General Office for the orders of
the courts. The aim of this system is to minimize efforts and time lost.
A goal of court information management system should be delivered not only functionality
That allows the courts to process their cases, but make in many ways that deliver added value
of courts.
1.3.2 Specific Objectives
1. To improve data storing and retrieving for faster execution, efficient and reliable.
2. To reduce time for searching cases and make periodic reports.
3. To reduce date loose by increasing security of the system.
4. To reduce undo delay in disposing the court cases.
1.4 Project Scope and Limitation
1.4.1 Project scope
Content scope
The study was interested in trying to understand the techniques of management used in
Somaliland Attorney General Office and relation between the information storing and its
management.
Geographical scope
Somaliland Attorney General Office, Hargeisa, Somaliland. To understand the techniques of
management used in Somaliland Attorney General Office.
Time scope
The study considering information relating to the period of three months.
1.4.2 Data collection
Interview and questionnaire
Court information management system
15
1.4 Significance of the project
Court information and management system helps to reduce undo delay in disposing the court
cases. It helps to increase speed, accuracy in all the operations and processes within courts.
This system will facilitate the staff in keeping all the court information and also is proposed to
build up the system that provide and generate the reports from the database records. It should
enable employees to do their work more efficient.
1.5 Risk Assessment and Management
Several risks that may face the project during development are:
Virus attacks, Viruses can attack used computers.
Power issues may also occur.
Above risks can be managed by using the fallowing solutions:
To control virus problems antivirus are used and backup or duplication of data needed.
Power issues can manage by using personal power sources.
Several risks that may face the project during development are:
Virus attacks, Viruses can attack used computers.
Power issues may also occur.
Members misunderstanding
Above risks can be managed by using the fallowing solutions:
To control virus problems antivirus are used and backup or duplication of data needed.
Power issues can manage by using personal power sources.
Increasing the communication between group individuals and try to understand each other.
Operating and Development Environment
Software tools:
Windows 7 an above operating system,
Microsoft visual studio and
SQL database.
Hardware tools:
Computer and Printer to print documents
Court information management system
16
CHAPTER TWO
LITERATURE REVIEW / DESCRIPTION AMOUNG THE
EXISTING SYSYTEM
1.0 Introduction
This chapter contains the main activities, functions of the existing system, player of the existing
system, report generating in the existing system, documents used in the existing system,
weakness of the existing system, strength of the existing system and feasibility study. This will
help you to know the existing system and improve the limitations of the existing system.
2.1 The main activities
Information about the defendant cases is stored freshly
It stored all the cases into the books
Cases are generated by recording by each facility provided in separate sheets and all
the tasks are done manually
The computerized system only done by registration of the final draft which is called
(GAL)
2.2 Functions of the existing system
Review a decision to prosecute
Perform any other action necessary in the interests in criminal prosecution
Revise all actions taken in criminal justice matters
Carry out general control of other members in the office
Monitoring major criminal cases and the outcomes and
Preparation of reports on cases in the Attorney General Office
2.3 Players of the existing system
o Manager
o Staff
2.4 Reports Generating in the Existing System
Attorney General Office uses only one form information system. That form used for
registration of the final draft which is submitted to the court. But all other information stored
manually by using traditional files. So the office reports are mostly paper based.
2.5 Documents used in the existing system
It’s normally kept inside stores and it’s used for controlling cases
Entries are posted before judgment and announced and
Court information management system
17
Entries are made on the basis of criminal cases
2.6 Weakness of the Existing System
Time consuming,
Less accurate,
Less efficient,
Loss of paper work,
Not friendly,
Difficult to keep old records,
More delays in case of getting cases.
2.7 Strength of the Existing System
Great in case of recording,
Secure in term of virus.
2.8 Feasibility Study
2.8.1 Economic Feasibility
Economic feasibility is the measurement of the cost effectiveness of the project because of that
it sometimes said to be cost benefit analysis. The cost benefit analysis of this project is
following:
2.8.1.1 Cost Benefit Analysis
Tangible benefits
Office per year Price in dollar
Two books per month $5 each book per month(5*2*12
months)
Two staffs for registration $300 each staff per month(300*2
staffs*12 months)
Total cost $8,640
Table 2.1 Office existing system cost per year
Office per year Price in dollar
Court information and management $250
One stuff $300*12 months
Total cost $7,150
Table 2.2 Office current system cost per year
Court information management system
18
The difference between two costs
Cost Reduction of the System = $8,640 - $7,150 = $1,490
Intangible benefits
• Make periodic reports
• Reduce date loose
• Increase reliability and availability
2.8.2 Technical Feasibility
Technical feasibility analysis the resource availability that may affect achievement of
acceptable system Technical feasibility determines whether the technology needed for the
proposed system is available or not. Since technology needed is available this proposed system
is technically feasible.
2.8.3 Time Feasibility
Time feasibility analysis the schedule and time that is planned for the project initiating and
ending. Since the time needed is available and the schedule is outlined this proposed system is
time feasible.
Court information management system
19
CHAPTER THREE
REQUIRMENT SPECIFICATION, ANLAYSIS AND
METHODOLGY
3.0 Introduction
This chapter consist of purpose, intended audience and reading suggestions, document
convention, objective, functional requirement, product prospective and function, principal
actors, user characteristics, general constraints, assumptions and dependencies, non-functional
requirements, system model and methodologies.
3.0.1 Purpose
The two-fold purpose of this information system is:
I. To automate, freshly store and support daily operations of the office.
II. It is easy to use, understand and navigate through which provides effective use of
date input and retrieval.
3.0.2 Intended Audience and Reading Suggestions
This SRS is intended for use by:
I. Project coordinators to evaluate the project documentation.
II. Auxiliary developers as background reference material.
III. IT department staffs (Users).
3.0.3 Document Convention
Description Convention
System requirement specification SRS
3.1 Objective
Objective of this section is to describe the requirement specification and analyse it started using
the planned information. SRS is the description of the system developed and include some use
cases that describe user interaction of the system. These leads to the design and implementation
phases. Based on this design solving the existing problem becomes easy.
3.2 Functional requirement
Functional requirements of the system documents the operations and functions that the system
able to perform or its components.
I. The system must be authenticated; means use username and password
before accessing the system.
II. Data must be entered before a request can be approved.
III. Search button click must fetch the required data.
IV. Any delete button must remove the unwanted data.
Court information management system
20
V. System must display the appropriate errors.
VI. System must be able to provide the yearly report as wanted
3.3 Product prospective
The product is supposed to Somaliland Attorney General Office. It is window based application
that provides a simple mechanism for the office and users to keep track with the daily entries
and easy data searching.
3.4 Product function
The system will perform a set of important tasks including:
I. User can enter, edit and remove data.
II. Keeps all the information in one place.
III. Makes fetching easy.
IV. Saves time and energy.
3.5 Principal Actors
Principal actors of the system are:
Users
People who enter, edit, remove and fetch data in database.
3.6 User Characteristics
Understanding your users can help you design the system to meet their needs.
The following is a list of characteristics you might want to know each user.
Address
Tell Number
Education level
3.7 General Constraints
The following constraints have been made in completing project statement:
Approved project statement will be used as framework for documenting the scope baseline of
project and for scheduling and progress and performance measurement and reporting.
The project implementation will be completed by July 31, 2017
3.8 Assumptions and Dependencies
It is assumed that the Attorney general office will have enough trained staff to take care the
system.
Court information management system
21
3.9 Non-functional Requirements
Performance requirement
The performance of the system will highly depend on the performance of the hardware
and software components of installing computers.
Safety requirement
There are several user levels in court management system; access to the various
subsystems will be protected. Maintaining backups ensure the system database security.
System can be restoring in any case of emergency.
Software quality attributes
o Availability
All data in the system will be available in any time.
o Reliability
Specific factors required to establish the required reliability of the software
system at a time of delivery.
o Portability
The court management system shall run any Microsoft Windows environment.
Availability of visual studio for court management system could make the system
portable
3.10 System Model
3.10.1 Use Case Diagram Use case diagrams are methodology used in system analysis to identify, clarify and
organize system requirements. More than that it provides an external view of the
system. The system save, retrieve, edit, delete and produce reports when the users login
also takes value to search information from the database to return the requested data.
Actors Staffs
Manager
Use cases Login
Choose from Menu stripe
Nooc danbi
Court information management system
22
Delete, Edit, Insert
eedaysane
Delete, Edit, Insert
Dhibane
Delete, Edit, Insert
Saldhig
Delete, Edit, Insert
Shaqaale
Delete, Edit, Insert
Diwaangalin(gal)
Delete, Edit, Insert
Provide reports
Figure 3.1 System Use Cases
Court information management system
23
3.10.2 Use case description
Use case name System use case.
Summary The user sign in and navigate through the system.
Actor Staff, Manager
Precondition User login
Description -The user enters the system using password and username.
The system checks them and authenticates the user if the
information provided is right. Then the user navigates
through the system by choosing the menu strip items then
inserting, deleting, editing and searching data that produces
report as required.
-The manger enter the system using password and username.
The system checks them and authenticates the user if the
information provided is right. Then the manager also
navigates through the system by deleting, editing, searching
and registering new staffs. Also printing the provided reports.
Post condition System must provide and store data.
Table 3.1 Use case 3.1 description
3.10.2 Activity Diagram
Activity diagram describes dynamic aspects of the system. It basically represents the
flow from one activity to another activity.
Figure 3.2 Activity Diagram
Court information management system
24
3.10.4 Sequence Diagram
Sequence diagram shows interaction, which represents the sequence of the message between
instance of the classes, components, subsystems and actors.
Figure 3.3 Sequence Diagram
Court information management system
25
3.11 Methodologies
3.11.1 Advantages of OOAD with UML Methodology
It is easy to understand
It is easy to maintain. Due to its maintainability OOAD is become more popular
day to day
It provides reusability
It reduce the development time and cost
It improves the quality of the system due to program reuse
3.11.2 Software Requirement
3.11.2.1 Tools/ Design and Development Tools
Microsoft Visual Studio
It’s used to create graphical user interface of the system
Visual Paradigm
It’s used to create UML diagrams
Microsoft SQL Server
It's the database that keeps the data
3.11.3 Hardware Requirement
Computer
Printer to print documents
Court information management system
26
CHAPTER FOUR
SYSTEM DESIGN / ANALYSIS AND TESTING 4.0 Introduction
This chapter contains performance criteria, dependability, maintenance criteria, end-user
criteria, system architecture and screen. This study teaches how the system look like.
4.2 Design Goals
Design is about make progress. It is conceptualization and creation of new things.
Good design leads to system that is:
Correct: free from errors
Flexible: capable of bending easily without breaking
Reusable: able to be used once again
Efficient: performing in the best possible manner the least waste of time and effort.
The goal of the system design is to manage complexity by dividing the system into manageable
parts. Therefore the design goal criteria stated in this chapter consider the facts of determining
the performance, dependability, maintenance and end-user criteria.
4.2.1 Performance Criteria
Since the system is designed to be accessed by one user at a time it is capable for handling
requests quickly.
Response time: the response time for searching should be fast. To attain this goal, coding
should follow simple, efficient and fast algorithms. Especially looping statements should be
avoided or minimized.
4.1.2. Dependability
Reliability: The system should be tested after and during development process to verify that
whether the specified services are available or not.
Fault Tolerance: system should continue operating properly in the event of the failure of some
of its components.
4.1.3 Maintenance Criteria
Traceability of Requirement: The system shall be developed according to the system analysis
and the design specification and it should not incorporate anything beyond. Otherwise newly
incorporated functionality shall be documented.
4.1.4 End-User Criteria
Usability: The application should be developed easier for user understanding. Especially in the
development of the user interface it is good to keep track with the users.
Court information management system
27
4.2 System Architecture
System architecture is conceptual model that defines the structure, behavior and more views of
a system. An architecture description is formal description and representation of a system,
organized in a way that supports reasoning about the structures and behavior of the system.
4.3 Screens
Figure 4.1 Splash Form
Court information management system
28
Figure 4.2 Login Form
Figure 4.3 Menu strip Form
Court information management system
29
Figure 4.4 Nooca Danbiga Form
Figure 4.5 Eedaysanayasha Noocan Danbiga Form
Court information management system
30
Figure 4.6 Eedaysane Form
Figure 4.7 Ku dar Eedaysane Form
Court information management system
31
Figure 4.8 Dibu eeg eedaysane Form
Figure 4.9 Dhibane Form
Court information management system
32
Figure 4.10 Ku dar Dhibane Form
Figure 4.11 Dibu eeg dhibane Form
Court information management system
33
Figure 4.12 Saldhig Form
Figure 4.13 Ku dar saldhig Form
Court information management system
34
Figure 4.14 Dibu eeg Saldhig Form
Figure 4.15 Shaqaale Form
Court information management system
35
Figure 4.16 Ku dar Shaqaale Form
Figure 4.17 Dibu eeg shaqaale Form
Court information management system
36
Figure 4.18 Gal Form
Figure 4.19 Ku dar gal form
Court information management system
37
Figure 4.20 Dibu eeg gal form
Figure 4.21 Warbixin eedaysane Form
Court information management system
38
Figure 4.22 Warbixin guud Form
Figure 4.23 Warbixin gal form
Court information management system
39
CHAPTER FIVE
IMPLEMENTAION AND TESTING
5.0. Introduction
This chapter covers the implementation, database and application implementation and testing.
5.1 Implementation Implementation is the process of moving idea from concept into reality. Proper implementation
is vital to provide reliable system to meet the user requirements. Implementing software
requires a close and complex partnership between developers and users. Implementation phase
includes following tasks:
o Investigation of a system and constraints
o Training users
o Evaluation change over.
In advanced court information management system implementation process is successfully we
implement the system by apologize all the aspects of the users.
5.2 Database Implementation
Database system approaches to data management overcomes many of the shortcomings of the
old fashioned file system. One of the key features of a database system is data stored as a single
logical unit. Database can be shared or secured users. There is more control and accountability
over how the data is managed because the data all resides in one database. The database
development design phase brings up the concept of data models. Data models are diagram or
schema which are used to present the data requirements at different levels of abstraction.
Database implementation is one important phase of the system where you will implement your
database and put into practice how it will work. In this phase you will need more carefully
proposal the steps will be taken during implementation.
Court information management system
40
Database Diagram
Figure 5.1 Database diagram
5.3 Application Implementation
Application implementation is a system framework related elements. Application
implementation is one of the most important phases in the system development. This phase
must be carried out in consistency with the database implementation phase.
5.3.1 Loading/Splash Form First form of the application is the Splash form which allows for the user to get general view
of the system before entering the system. It Loads few seconds and looks like this.
Court information management system
41
Figure 5.2 Loading/splash form
5.3.2 Login Form
Second form is the login form that allows the access of the system. It checks whether the user
is authenticated or not by checking user name and password. If user name and password are
correct than user access the system otherwise the user rejected because only authorized users
can login.
Figure 5.3 Login form
Court information management system
42
5.3.3 Main form
After authentication main form loaded. Mani form contains collection of all system elements
such reporting menu items and user registration menu items.
Figure 5.4 Main form
5.3.3.1 Nooca Danbiga form
First manu strip item is the nooca danbiga that used to register, delete, edit and search date of
nooca danbiga. Also a click of it leads to another form which is the eedaysanayasha nooca
danbigana.
Court information management system
43
Figure 5.5 Remove nooca anbiga
Figure 5.6 Insert nooca danbiga
Court information management system
44
Figure 5.7 Edit nooca danbiga
Figure 5.8 Eedaysanaha noocan danbiga form
5.3.3.2 Eedaysanaha form
Second menu strip item is the eedaysanaha that used to register, delete, edit and search date of
eedaysanaha information.
Court information management system
45
Figure 5.9 Search eedaysane
Figure 5.10 Remove eedaysane
Court information management system
46
Figure 5.11 Edit eedaysane
Figure 5.12 Insert eedaysane
5.3.3.3 Dhibanaha form
Dhibanah menu strip item used to register, delete, edit and search date of dhibanaha
information.
Court information management system
47
Figure 5.13 Search Dhibane
Figure 5.14 Insert Dhibane
Court information management system
48
Figure 5.15 Edit Dhibane
Figure 5.16 Edit Dhibane
5.3.3.4 Saldhiga form
Saldhiga menu strip item used to register, delete, edit and search date of any saldhiga
information.
Court information management system
49
Figure 5.17 Search saldhig
Figure 5.18 Edit saldhig
Court information management system
50
Figure 5.19 Remove saldhig
Figure 5.20 Insert saldhig
5.3.3.4 Shaqaalaha form
Shaqaalaha menu strip item used to register, delete, edit and search date of any shaqaalaha
information.
Court information management system
51
Figure 5.21 Search shaqaale
Figure 5.22 Insert shaqaale
Court information management system
52
Figure 5.23 Edit shaqaale
Figure 5.24 Remove shaqaale
5.3.3.4 Diwaangalinta form
Diwaangalinta menu strip item used to register, delete, edit and search date of any
diwaangalinta information.
Court information management system
53
Figure 5.25 Search gal
Figure 5.26 Insert gal
Court information management system
54
Figure 5.27 Edit gal
Figure 5.28 Remove gal
5.3.3.4 Warbixinada
Warbixinta menu strip item used to generate three types of reports eedaysanayaasha report,
galka report and general report.
5.3.3.4.1 Warbixinta eedaysanayaasha
This menu item used to generate the report of any needed eedaysane using any value to search.
Court information management system
55
Figure 5.29 Search warbixinta eedaysane
Figure 5.30 Report generated by warbixinta eeadaysanayaasha
Court information management system
56
5.3.3.2 Warbixinta galka
This menu item used to generate the report of any needed galka using xigno to search.
Figure 5.31 Warbixinta Galka
Figure 5.32 Report generated by warbixinta galka
Court information management system
57
5.3.3.3 Warbixinta guud
This menu item used to generate the report of any needed general report using the date between
two dates and nooca danbiga to search.
Figure 5.33 Warbixinta guud
Figure 5.34 Report generated by warbixinta guud
Court information management system
58
5.4 Testing
Testing is the process to show the correctness of the program. Testing is needed to show
completeness to improve quality the system and provide the maintenance.
5.4.1 Software testing
Software testing is the process of analyzing a software item to detect the differences between
exiting and required conditions and to evaluate the features of the software items. Software
testing is an activity that should done throughout the whole development process.
5.4.2 Testing objectives include
Software testing has different goals and objectives. The major objectives of software testing
are as follows:
To prevent defects
Earning confidence in and providing information about the level quality
To make sure that the end results meets user requirements
To gain dependability of the users
5.4.3 Testing methodologies
5.4.3.1 Testing strategies
Software testing strategies is an outline that characterize the testing approach of the software
development cycle. There are many strategies of software testing are as follows:
Dynamic heuristic approaches
Consultative approaches
Model-bases approaches
Methodical approaches
5.4.3.2 Unit testing:
Unit test is a testing of individual hardware or software units or groups of related units. The
purpose to validate that each unit of the software performs as designed. Unit is the smallest
testable part of software. It is usually has one input and single output. Unit testing increases
confidence in maintaining code.
5.4.3.3 Integration test:
Integration test is a testing in which software components or hardware components or both are
combined and tested to evaluate the interaction between them. The purpose of this level of
testing is to expose faults in the interaction between integrated units.
Court information management system
59
5.4.3.4 Validation testing:
Validation testing is the process of evaluating software at the end of development process to
determine whether software meets user’s expectations and requirements. Validation activity
carried out after verification.
5.4.3.5 System testing:
System testing of software or hardware is testing conducted on a complete integrated system
to evaluate the system’s compliance with its specified requirements.
5.4.3.6 Security testing:
Security testing is a variant of software testing which ensure that system and application in
attorney general office are free from loophole that may cause a big loss. The goal security
testing is to identify the threats in the system and measures its potential vulnerability. It also
helps in detecting all possible security risks in the system and help developers in fixing these
problems through coding.
Types of security testing:
Vulnerability Scanning
Security Scanning
Penetration Testing
Risk Assessment
Security Auditing
Posture Assessment
Ethical Hacking
5.4.3.7 Performance testing:
Performance testing is a type of testing to ensure software applications will perform under their
expected workload. The goal of performance testing is not to find bugs but to eliminate
performance bottlenecks.
The focus of performance testing is checking software programs.
o Speed
o Scalability
o Stability
Court information management system
60
CHAPTER SIX
CONCLUSION AND RECOMMENDATION
6.0 Conclusion and Recommendation
In completion of this project court information and management system is computerized
software designed to provide users good services. Court information and management system
have very effective policy decision making tools for middle and top management system. In
the development of this software we used development lifecycle methodology, in different
process are done include analysing, designing, deployment, implementation and maintenance.
This software looks after all the requirements and is capable to provide easy and effective
storage of information related to court information and management system
The goal of court information and management system should be delivered not only
functionality that allows the courts process their cases, but makes in many ways to deliver
added value of courts
Court information management system
61
REFFERCES
References for the project development were token from
Websites:
[1] http://home.deib.polimi.it/bolchini/research/dsddm.html For Dependable
System Design and Design Methodologies
[2] https://stackoverflow.com
[3] http://canlu.blogspot.com
[4] http://www.techtarget.com
[5] Books: Fundamentals of database; Author: elmasri and navate.
Court information management system
62
APPENDIX A
APPENDIX B