Group Member Id

MADDA WALABU UNIVERSITY
COLLEGE OF COMPUTING
DEPARTMENT OF COMPUTER SCIENCE
Title:GobaCity Online Prisoners’ Information Management System
Group member ID
Robsen Aliyi Coe/0032/10

Tajudin Jemal Coe/0035/10
Muhammed Umer Coe/0070/10
Halfiya Sheko Coe/0059/10
Submttted to
College of Computing Department of Computer Science
Submitted by :Group 4
Robe,Ethopia
March 2022
I
EXAMINERS APPROVEL SHEET
Project title: prisoners online information managemaent system for goba city
Name of Student Signature date
1. _______________________________________
2. _______________________________________
3. _______________________________________
4. _____________________________________
Advisor Name Signature date

_______________________________________ _____________ ____________
Examiner signature date

___________________________________ _____________ ___________
Project coordinator signature date

___________________________________ _____________ ________
HOD signature date

_____________________________________ _____________ _____________
2
Abstract
The system analysis is prepared for web Based prisoner Management system and the
description of existing system description system, implementation of new system . include In
the first chapter we try to identify the Back ground of the study and the project and statement
of problem in existing system and limitation .
In the next chapter our study about the existing system ,identify problem encountered in the
system and in the rest chapter we are tying model the system ,design new system
The methodology we will be using is Object-oriented system analysis and design (OOSAD)
from object oriented the team will select Iterative method . After determining requirement
specification then the system tool design in accordance with specifications language and
implementation will be carried out using HTML5, CSS, PHP, JavaScript, XAMP server and
MYSQL, database. The current system will be design to be interactive and comfortable in
management of the system and will provide integrated service. This system will help for Goba
central prison institute to access their data easily and to reduce work load.
3
ACKNOWLEDGMENT
Firstly we would like to thank our almighty GOD to keep as full of health to prepare and come
up with this project. Then we would like to thank Computer science department for giving as this
chance to do this project. More over, we would like to express our gratitude to our Advisor Mr.
Muhammed At the last not the least, we would like to express our deepest appreciation to
those people who support us for successful in working of this proj Finally we would like to
thank alla who are help us
Special thanks to our Advisors: mr- mohammed
4
TABLE OF CONTENTS
ACKNOWLEDGMENT...............................................................................................................................4
CHAPTER TWO:- STUDY OF EXISTING SYSTEM.....................................................................................15
2.1 Introduction...............................................................................................................................15
2.2 LITERATURE REVIEW.....................................................................................................................15
2.3 description of Existing system....................................................................................................15
2. 4 Draw Back of existing system........................................................................................................16
2.6 Business rule.................................................................................................................................16
2.7 Alternative solution.......................................................................................................................17
CHAPTER THREE :- THE PROPOSED SYSTEM........................................................................................20
3.1 over view of proposed system......................................................................................................20
3.3 Functional requirements...........................................................................................................20
3.4 NON FUNCTIONAL REQUIREMENT............................................................................................21
Graphical user interface.......................................................................................................................22
Chapter four : System model..............................................................................................................25
4.1 Introduction....................................................................................................................................25
4.3 use case identification.....................................................................................................................25
4.4 system use case diagram...........................................................................................................27
4.4.1 Actor Description:–...............................................................................................................27
4.4.2 Use case Description:- describe in the following table................................................................27
4.5.1 Sequence diagram........................................................................................................................35
4.5.2 Collabaration Diagram..................................................................................................................43
4.5.3 Activity diagram......................................................................................................................46
4.6.1 CLASS DIAGRAM..........................................................................................................................54
4.6.2 Object Diagram.............................................................................................................................54
5
list ofTable
TABLE 3. 1 DISCRIPTION FOR LOGIN....................................................................................................32
TABLE 3. 2 DISCRIPTION FOR REGISTRATION...................................................................................32
TABLE 3. 3 DISCRIPTION FOR VIEW BY GENDER..............................................................................33
TABLE 3. 4 DISCRIPTION FOR VIEW BY CRIME TYPE......................................................................33
TABLE 3. 5 DISCRIPTION FOR SEARCH................................................................................................33
TABLE 3. 6 DISCRIPTION FOR VIEW RELEASEMENT BY REDUCTION.........................................34
TABLE 3. 7 DISCRIPTIONFOR VIEW BY RELEASEMENT BY APOLOGY........................................34
TABLE 3. 8 DISCRIPTION FOR VIEW RELEASING PRISONER..........................................................35
TABLE 3. 9 DISCRIPTION FOR SEND REQUEST MESSAGE FOR HOI..............................................35
TABLE 3. 10 DISCRIPTION SEND APPROVAL MESSAGE FOR PIOAO DIRECTOR........................35
TABLE 3. 11 DISCRIPTION FOR SSO AND MBO DIRECTORS SENDING REQUEST MESSAGE. .36
TABLE 3. 12 DISCRIPTION FOR SEND APPROVAL MESSAGE FOR SSO AND MBO DIRECTORS
..............................................................................................................................................................36
TABLE 3. 13 DISCRIPTION FOR VIEW MESSAG..................................................................................37
TABLE 3. 14 DISCRIPTION FOR SEARCH BY FINGER PRINT............................................................37
TABLE 3. 15 DISCRIPTION FOR UPDATE..............................................................................................38
6
List of of figures
FIGURE 3. 7 SEQUENCE DIAGRAM FOR VIEW BY CRIME TYPE, UPDATE AND DELETE FILE...............43
FIGURE 3. 8 SEQUENCE DIAGRAM FOR VIEW BY SEARCHING....................................................................45
FIGURE 3. 9 SEQUENCE DIAGRAM FOR SEARCH BY FINGERPRINT............................................................45
FIGURE 3. 10 SEQUENCE DIAGRAM FOR STATISTICAL REPORT..................................................................46
FIGURE 3. 11 SEQUENCE FOR SSO AND MBO SENDING REQUEST AND RECIEVING APPROVAL........46
FIGURE 3. 12ACTIVITY DIAGRAM FOR LOGIN....................................................................................................48
FIGURE 3. 15 ACTIVITY DIAGRAM FOR SEARCH BY FINGER PRINT.............................................................51
FIGURE 3. 16 ACTVITY DIAGRAM FOR VIEW STATISTICAL REPORT............................................................52
FIGURE 3. 17 ACTIVITY DIAGRAM FOR UPDATE FILE......................................................................................53
FIGURE 3. 18 ACTIVITY DIAGRAM FOR DELETING FILE...................................................................................54
FIGURE 3. 19 ACTIVITY DIAGRAM FOR SENDING APPROVAL MESSAGE....................................................55
FIGURE 3. 20 VIEW MESSAGE..................................................................................................................................56
FIGURE 3. 21ACTIVITTY DIAGRAM FOR SSO AND MB DIRECTORS SENDING REQUEST MESSAGE......56
FIGURE 3. 22 CLASS DIAGRAM................................................................................................................................58
List of acronym
7
GCOPIMS: ---------------------------Goba city online prisoners’ information management system
PIOAO:---------------------------------prisoners in and out office
HOI:-------------------------------------head of institute
SSO:----------------------------------security and safety office
MDO: --------------------------------maintaining discipline office
OOSAD:----------------------------object oriented system analysis and design
UML:-------------------------------unified modeling language
Chapter one
Introduction
8
The prison of goba town in bale zone is established in 1945 as well as at this time the prison it have
1470 prisoner .Goba central prison institute is one of the most renowned prison around Oromia region.
It have both military and civil employees. However this prison operates its work by manual system
which is not compatible with recent technology; i.e. Traditional way. As we know manual system is a
system which requires human labour for every processing of data it comprises searching, updating,
retrieving, deleting etc. Of data (file) by human labour.so, transforming this system to computer based
system seems to us crucial. Due to this it is very tiresome and time consuming activity to manage the
information of the institute; especially the prisoners’ information. That is why we are dared to improve
the working environment to computerized system by making it web based system for the sake of easy
manipulation of information.
1.1 Background of Project

Prisons play a significant role in any country’s ability to establish a safe and secure environment
for its citizens. The most common use of prisons is as part of an organized Governmental Justice
System in which individuals officially charged with or convicted of crimes are confined to a jail
1.2 Statement of the proplem

Since Goba central prison institute is a large institute it should have been an institute that have an
organized and computerized system to manage the general information or data of the
organization, beside that the employees of the institution don’t have to struggle to search or
identify the prisoners’ necessary information.
 difficult to register a new prisoner
 Difficult to search prisoner information depending on their criminal type.
 Searching, updating, retrieving prisoner information is time consuming.
 Difficult to calculate reduced dates from the prisoner’s sentenced date.
 Indentifying the previous history of the prisoner is too difficult.
 Loss of data may occur
 Difficult to manage information about prisoner
1.3 Objective of the Poject

1.3.1 Genaral Objective
The general objective to develop Goba city online prisoners’ information management system.
9
1.3.2 Specific Objective
We can achieve the general objective by fulfilling the specific objective listed below:
 To design a system which register prisoners.
 To enable assigner to assign a Room for prisoners.
 To design a system enable officer take an attendance.
 To Design a system generate report
1.4 Scope and Limitation of the Project

1.4.1 Scope of the Project
 Register prisoner
 Assign Room for prisoner
 Take an Attendance
 Generate report
 Update prisoner information
 View prisoner data
 Search prisoner data
 Delete prisoner information
 Retrieve data
1.4.2 Limitation of the Project

 Cannot completely avoid human intervention
 Due to lack of finance we are unable to get fingerprint sensor.
 The our system operated only English language
 The system uses afan oromo rather than other or the system depended on afan oromo.
1.5 Significance of the Project

The System provide service to Goba central prison institute; specifically for the office of the
organization called prisoners in and out administrator office. So that the employees could do
their job easily starting from
 The system provide proper security and reduce manual work
 registration
10
 to retrieving,
 searching,
 updating,
 It will able to identify repetitive prisoner
 It save time
 The system can automatically calculate the amount of date for prisoners who have to be
released by apology (excuse) and
 Calculating the amount of day that will be reduced from the prisoner’s sentenced date
(which is difficult with manual work)
 The service provided by employees will be fast as possible.
 The system will easily generate statistical report
 Reduce wastage of time
 Increase usability
1.6 Methodology and tools

1.6.1 Data collection methodology
The Methods and techniques we use to analyze the existing system and designing a web-based
system include interview, document analysis, To get the basic information about the existing
manual system, the team interviews the staffs and the head of the institute about their manual
system and the problems associated with the current manual environment.
 Documents Analysis: To get more information about how the work is done we use this
method for collecting more information and data by gathering some of their data
available to us.
 Interview: By asking the organization employees who are enrolled in different kind of job.
1.6.2 System Analysis and Desgn

The methodology we will be using is Object-oriented system analysis and design (OOSAD).
From Various types of SDLC Methodologies we specially choice the iterative
The main reason using OOA are
11
 Object are easier for people understand .
 Data process are kept together the main reason we decide to use the object approach.
 Code can be reused easily .
 To be able to change our existing code to fit.
 Its is more flexible .
1.6.3 System Development Tools

1.6.3.1Software requirement
For successful completion of our system we use the following software requirement these are:-
FRONT END
 Java script
 HTML
 PHP
 CSS
 Ms-word 2007/ 10/16
 Ms- Visio 2007/10/16
BACK END
 XAMPP Server
 Design tool:-visual studio
 Adobe photoshop Cs4:-Red and write video and photo fle
 Google chrome:-is the fast easy to use and secure web brow
1.6. 3.2 Hard ware requirement

For the development and testing of the system, we will use the following hardware.
Laptop computer:
 Processor: Intel(R) Core (TM) i5-4210U CPU @1.70GHZ 2.40 GHz
 Installed memory (RAM): 8.00 GB
 500 GB Hard disks
 LAN support
 System type: Windows 64-bit Operating System, x64-based processor
12
The team will use this laptop computer because it is compatible with the system that is going to
be developed in this project.
System requirements is a statement that identifies the functionality that is needed by a system in
order to satisfy the customer’s requirements.
1.7 Project Management

1.7.1 Project Schedule
 project schedule by using gantt chart. It representing project schedule with respect to
time periods .
 we have identified the activities the activities of the project in order to accomplish the
project objectives within their Schedule requirements,which is on the table belw
1.7.2 Project bufget (cost breakdown estimation)

Cost estimation is the summation of individual cost element, using established methods and valid
data, to estimate the future cost of program based on what is known today.
The following table describes the cost the team will use for this project
13
No Item Quantity Cost
Per unit Total
1 Paper Under half packet
2 Print 5 40 200
3 Transport - - 400
4 Laptop 1 25000 25000
5 Desktop 1
6 Networking cable 1 100 100
1.7.3
8 Internet usage
9 Removal disk 16 GB 360 360
Total 26060
Project Work break down structure

This work break down of team while doing the project by using data collecting and also
organize the data. Work decomposition of work to run by the team to accomplish the project
objects and create deliverable purpose of organize define the total scope of project.
Task Group Name

Proposal of project All Group Member
System Requirement and specification All Group Member

Analysis and design >>
Implementation and testing >>
1.7.4 Risk Analysis and Migration

Risk analysis Degree of impact Risk mitigation
Luck of time Medium By using night time

Luck of team communication Medium Communicate by social media
Luck of virus Attack soft ware Low Install anti virus
14
Luck of data lost Low Backup and restore data
1.8 Feasibility Analysis

The main objective of the feasibility for adding new modules and debugging old running
system .
All system are feasible if they are given unlimited resource and infinite time. They are aspects
in the feasibility study of the preliminary investigation.
 Operational Feasibility
 Technical Feasibility
 Political Feasibility
 Economic Feasibility
1.8.1 Technical Feasability

Our system is technically feasible; with the back End SQL Server database, Microsoft word for
writing document hopefully we will develop successfully by using our academic knowledge in
this case these project is feasible according to the above reasons
1.8.2 Economical Feasability

As part of this, the costs and benefits associated with the proposed system compared and the
project is economically feasible only if tangible or intangible benefits outweigh costs.
1.8.3 Polotical Feasability

 To an understanding of how key stakeholder within the jail view the proposed system.
 Our system is free from any political group.
 It’s works for citizen well, so our proposed system is political feasibility
1.8.4 Operational feasability

It is a standard that ensures interoperability without stifling competition and innovation among
users, to the benefit of the public both in terms of cost and service quality. The proposed system
is acceptable to users. So the proposed system is operationally feasible .
15
The following areas will have the operational feasibility in the proposed project
 The organization has approved this system as their working system.
 The user of the system has accepted the proposed system as their new working system
and realized the benefits of it.
CHAPTER TWO:- STUDY OF EXISTING SYSTEM

2.1 INTRODUCTION
The existing system of Goba central prison has been operated by manual system. many
processes such as filing system, search for prisoner information, registration for prisoners,
report generation ,and many other activates has been done manually.
It is so to study and identifies the strength and weakness of existing system .it is also defines the
functional and non functional Requirement
2.2 LITERATURE REVIEW

The current literature review will cinsider the literature base in relation to life sentence prisones.
A synopsis of the prison effects debate will be provided following which reaserch topics
attracting more recent intrest will be explored .the term life sentence prisoners and life will be
used interchangeably to reflect their use both withn the litature and among prisoners
themselves .The aims of the review are illuminate the most dominant research trends in relation
to life sentence prisoners and to identify gaps in the empirical research base.
2.3 DESCRIPTION OF EXISTING SYSTEM
This existing system can handle prisoner information manually by using paper as well as right
same information on desktop computer so it is difficult to manage prisoner data The existing
system has several disadvantages and many more difficulties to work
The director of each office can manage and manipulate all the information about the prisoners
by paper form in general the institution cn not easily access and provided prisoner information
for which office that required Report
16
Strength of existing system
 Team work utilization
 Proper communication
 Departementalization
weakness of existing system
 Since the Goba central prison performs registration, report manually, to find any prison
detail information it takes much time.
 Difficult to manage the overall system
 Duplication of data occurs when data input into the system.
 The data stored takes more rooms.
 A need for extra manual effort
 Since the system currently uses the manual system it is not economically sufficient i.e.
there is a redundancy of activities,
 Currently, almost there is no control and security mechanism within the office.
 The services provided by the office are not as fast as possible because the service
providers are busy with the paper and paper related activities.
 There will be calculation error during the release of prisoners
2. 4 DRAW BACK OF EXISTING SYSTEM

this Existing System is used manually handle and process prisoner information so this
traditional system is decreases institution service and make mistake .the instituoin have the
following problem
 Required large More man power.
 Time consuming to search information .
 Consumes large volume of paper work. And Needs manual calculations.
 Difficult to identifies prisoner and there criminal
To avoid all these limitations and make the working more accurately the system needs to be
computerized in a better way. Proposed System
Limitation of existing system
 Errors and Inconsistencies:
17
 can cause an irreparable damage.Slow, tedious, time consuming:-
 Searching a record is difficult
 Lack of security:-
 any changes load or maximum demand mayend up being
 Information redundancy:
 Suchredundancies are not required as the information is already stored previous
2.5 Practices to be preserved from current system

 Maintain and protect originality of existing system and update performance action
 Keep institution office hierarchy
 Keep preserved of data for only required office
 Make easy Accessing current system
2.6 BUSINESS RULE

Business rules are abstractions of the policies and practices of a business organization..
 There are same business rule process for this institution there rule have order,
definability and cross functionality
1. The institution have there own communication style
2. Institution have prisoner identification card
3. Limited time in and aut for Customer and prisoner
4. Each customer can view prisoner on specific window
5. The prisoner can take brake only during morning for one hours and afternoon for 30 min
Generally the business rule for existing system is as follow
Rule 1:
 Respect the counry, regions culture, values and regulation
 Full information about prisoner is open for customer
 Save from any illegal treaty
 Respected rule and regulation that formulated to protect institution and prisoner
Rule 2:
 Safeguard institution property and wealth
 Give fair service to guests
18
 Be honesty and responsible to institution
 Save from illegal act which harm to institution ,prisoner and society
 Not allowed smoking and taking illegal drugs
Rule3:Administator
 Announce the correct information about institution and give orientation for
prisoners
 Inform prisoner information for required body
 Maintain employee skill and initiate them
 Give command to worker to give quality service
 Respect workers right
 Control every activity
2.7 ALTERNATIVE SOLUTION
 Make data processing automate communication by using web based

 Change compliantly manual system to automated system by keeping the structure of
existing system
 Change all paper based mechanism to computer based system
19
2.8 FORM USED
20
21
CHAPTER THREE :- THE PROPOSED SYSTEM
3.1 OVER VIEW OF PROPOSED SYSTEM

In this section we are going to describe Analyzing current system and identifies the problem in
Goba city jail so our project team decide to develop for goba city on line prisoner management
system and our new project is solve problem of current system we seen and proposed system will
use the major Functionality of existing system and integrated with technology that to be efficient
the system going to develop provided information easily and make with good working
environment that to be flexible and will provided ease of work and will reduce time for process
and other paper work and the team identifies and evaluate functional and nonfunctional
requirements of the proposed system, designing the class diagram, the use case and its scenario,
designing the sequence diagram and activity diagram for the use cases, and finally, we are going
to design the interface of some use cases
3.2 SYSTEM CONSTRAINT

Constraint is the element factor block from achieving goal of the project .
During developing any wide or small system there may be Expecting same problem /obstacle
 Some problem are like
 Group being confused to select title for new system
 Time of the group meat is challenge
 Gathering data source (information ) challenge
 Reference on time may be extend project completion
 Project is not complete as much as possible because of shortage of time
3.3 FUNCTIONAL REQUIREMENTS

The Functional requirement specifies particular results of a system and it determine technical
detail ,data manipulation processing and other specific functionality that define what system
supposed to accomplish
Generally functional requirement are expressed in the form of “what system must do”.
The team have gathered the functional requirements listed as follows:
 Login: the system will have a login for the office of prisoner’s in and out administrative
director and head of the institute.
 Prisoner registration: the system will register guilty prisoner, suspected prisoner and
transferred prisoner
 Upload prisoner photo: photos of prisoner file will be uploaded to the system for
registration purpose.
 Finger print analysis: finger print of each prisoner will be taken for registration and
searching purposes.
22
 View prisoners: The system must have a fast and easy searching method using different
attributes of the prisoner’s record
 Export to excel: export (download) to excel prisoner and officer information from the
database.
 Viewing prisoner’s file:the user will be able to view each prisoners file by using whether
finger print orregister number.
 Search by finger print: using finger print ofany prisoner the user can fetch
 Update prisoner file: The system should have a way of updating or modifying the
prisoner’s information with sufficient reason and authorization
 Delete prisoner file:the authorized party can delete the prisoner unnecessary or repetitive
information if needed.
 View releasement: The system will transfer the prisoner from the current prisoner’s table
to released prisoners table
 Generate statistical report: the system will generate statistical report of the day
 Send request message for HOI: if the director of prisoners in and out administrative
office need to update any information regarding the prisoners file the director need to get
approval from the head of the institute.
 Send request message for Director of prisoner in and out administrator office: If
office of security and safety and maintaining discipline office needs prisoner file they must
send a request for the approval of the director to get access of certain prisoner file.
 View message: if any request message has been sent to the user the user can see the
message.
3.4 NON FUNCTIONAL REQUIREMENT
Non-functional requirement define how the system is supposed to be and it often culled qualities of the
system
It specifies criteria’s that can be used to judge the operation of a system rather than specific behavior
over all it specify characteristics such as cost and reliability
 Openness :system should define extend interface to allow easy addition of new data
 Transparency :the over all process of online goba city jail prisoner management system
must be transparent for the user being easy to see
Usability
 The user can use the system by looking at descriptive icons
 The system is user-friendly and easy to use and requires less training to understand.
Security
 The system only permits authorized user to enter the system. Authorized users are who
have username and passwords.
23
Error handling : there is the mechanism to handle error occur that is not stop system
functionality
Quality issues :information should be Accurate and update
Openness : the define extend interface ti allow new data

Response Time :respond request within short period of time
Scalability
 If the number of prisoners and user increases in the organization it does not effect on the
database.
Performance
 The system works at a high-performance rate when executing user’s input and should be
able to provide a response within a short time
 Availability
 The system should always be available at 24 hours, 7 days a week when the internet is
available. Backup and Recover
 y : the system are available at any time without interruption back
GRAPHICAL USER INTERFACE

It’s the form prepared for information and easy to understand and designed According to standard the
best thing in this input designed to Achieved all objective mentioned in simplest manner that possible to
create ,display and store information that will required
24
3.5.1 Specification
System requirement specification (SyRS) is a detailed outline of the requirements
necessary to create a complete system.
is a structured collection of information that embodies the requirements of a system.
 The system of GUI is consistent with all other program

 The caption and text of GUI should be clear to understand and self –
description
 GUI should be help to file that describe the usage of GUI
 GUI should be easily customizable
 complete functionality
 availability,
 performance, and security needs of a system.
3.5.2 user interface description

UI:1 home page :user interface part where main page of the system will be viewed and link for
related topic
UI 2:1 Login page: it is page which enable user of system log in to system by interring there user
name and password
UI 3: About us page: it is a page that contain detail information about website
UI 3: package page :it is the page tha contain detail information and service about the package
that exist
UI :.help us page: the page that provided help information or guides for user when they need help
regarding to this system
25
3.5.3 USER INTERFACE PROTO TYPE(SNAP SHOOT)
Prototyping is the process of building a model of a system. In terms of an information system,
prototypes are employed to help system designers build an information system that intuitive and
easy to manipulate for end users. Prototyping is an iterative process that is part of the analysis
phase of the systems development life cycle
26
CHAPTER FOUR : SYSTEM MODEL
4.1 INTRODUCTION
System model is the conceptual model that describe and represent the system The techniques
and associated notation used for object-oriented analysis and design incorporated into a standard
object-oriented language called Unify Modeling language (UML). An important goal of
requirement modeling comes to an understanding of the problem that the new system is to
address. Modeling is vocabulary of the system that used to make decision about which
abstraction is parts of the system and which fail outside boundary of system modeling to improve
and understanding of a situation ,identifying of problem or formulating opportunities and
supporting decision making to model the system we must draw diffident diagram like use
case model, sequence diagram and activity diagram, and interface prototyping are also included.
4.2 ACTOR SPECIFICATION (IDENTIFICATION)

 Actor: is a person, or external system or organization that play a role in one or more
interaction with your system in our system the following actor are involved
There main actors on our project. such as
 PIOAO
 HOI
 SSO
 MDO
 System Administrator
4.3 USE CASE IDENTIFICATION

.
Use case: describes a sequence of actions that provides something of measurable value to an
actor and in this step we identifies the following cases
 Manage account
 Login
 Registere information
 Release prisoner
 Accept approve request,
 view relesement
 generate report
 delete prisoner information
 search prisoner information
 update prisoner information
 take an attendance
27
 assign room for prisoner
 take finger printer
 Retrieves prisoners information
4.4 SYSTEM USE CASE DIAGRAM

system use case diagram
Use case diagram is used to capture the functional requirement of the intended behavior of
the system from the user point of view and its shows asset of use case ,actor their
relationship
4.4.1 ACTOR DESCRIPTION:–

PIOAO: is a person who manage the overall activities of the system
HOI:-it perform task like Login view notification and search the prisoner data
SSO:- Director :- perform action like login and search information
28
MDO :- Perform action like login and search prisoner information
System Administrator :-Perform task like register user, login and search prisoner
information.
4.4.2 USE CASE DESCRIPTION:- DESCRIBE IN THE FOLLOWING

TABLE
Use case number USC1
Use case name Login
Actor Prisoner in and out administrative office director, head of
institute, security and safety office director, and maintaining
discipline office director.
Description User are authenticated and taken to their own user interface
based on the given privilege.
Precondition User name and password must be verified.
Basic course of action User action System response
1.The user opens the system 2. The system will
3.The user fills the login form display login form.
4.The user click on login button 5. The system will check
if the user name and
password is correct.
6. the system will
redirect to the target
page
Table 3. 1 DISCRIPTION FOR LOGIN

Use case name Registration
Actor Director of prisoner in and out administrative office.
Description The director will fill all the necessary information of the prisoners.
Precondition User name and password must be verified
1. User click on registration. 2. System display registration
3. User fills the form and page that have registration form.
click next. 4. System display upload photo
5. User clicks upload photo page.
button and choose photo. 6. System uploads the photo.
7. User clicks next. 8. System display finger print
9. If finger print available user page.
clicks get finger print. 10. System uploads finger print.
11. User clicks submit. 12. System saves file to database.
29
Table 3. 2 DISCRIPTION FOR REGISTRATION

Use case name View by gender
Actor Director of prisoner in and out administrative office and HOI
Description User can search and find Prisoners that have been registered in this
system
The prisoners file that the user is going to search for must be
registered first
1.User clicks view prisoner 2. System display view prisoner
3. User choose and click view page.
by gender button. 4. System display view by
5.choose gender type. gender page.
6.user clicks specific file 6. System will display files.
7.user display file
Table 3. 3 DISCRIPTION FOR VIEW BY GENDER

Use case name View by crime type
Actor Director of PIOA and HOI
system
The prisoners file that the user is going to search for must be
registered first
1.User clicks view prisoner 2. System display view
3. User choose and click view by crime prisoner page.
type 4. System display view
5.choose crime type by crime type page.
6.user clicks specific file 6. System will display
files.
7.system display file
Table 3. 4 DISCRIPTION FOR VIEW BY CRIME TYPE

Use case name Search
Actor Director of PIOA ,HOI,SSO and MBO
system
Precondition 1.User name and password must be verified
2.The prisoners file that the user is going to search for must be
registered first
30
1.User clicks view prisoner 2. System display view prisoner
3. User choose and click page.
view by crime type 4. System display view by crime
5.choose crime type type page.
6.user clicks specific file 6. System will display files.
7.system display file
Frequency of use
Priority
Special requirement
Table 3. 5 DISCRIPTION FOR SEARCH

Use case name View releasement by reduction
Actor Director of PIOA
Description User will be able to view releasing prisoners who have gotten
reduction of days from their sentenced date.
Precondition user name and password must be verified
1.User clicks view 2.system displays view
releasement. releasement page.
3.user clicks view releasement 4.system displays view
by reduction. releasement by reduction page.
5.user chooses crime type. 6.system displays prisoners file
7. user clicks copy to one under a specific crime type.
folder. 8.system display files of prisoner
that get reduction.
Table 3. 6 DISCRIPTION FOR VIEW RELEASEMENT BY REDUCTION

Use case name View releasement by apology
Description User will be able to view prisoners’ file who have got the chance
for apology
1.User clicks view 2.system displays view releasement
releasement. page.
3.user clicks view 4.system displays view releasement
releasement by apology. by apology page.
5.user chooses crime type. 6.system displays prisoners file
7. user clicks copy to one under a specific crime type.
folder. 8.system display files of prisoner
31
that get reduction.
Table 3. 7 DISCRIPTIONFOR VIEW BY RELEASEMENT BY APOLOGY

Use case name View releasing prisoner.
Description User will be able to view prisoners’ file who will be discharged
from the prison in a week.
1.User clicks view 2.system displays view releasement
releasement. page.
3.user clicks view releasing 4.system displays view releasing
prisoners prisoners page.
7. user clicks send to HOI 6. System displays prisoners file
under a specific crime type.
8.system send message to HOI
Table 3. 8 DISCRIPTION FOR VIEW RELEASING PRISONER

Use case name Send request message for HOI
Description The user will send a request for approval for the releasement of
any prisoner.
There must be a prisoner who is going to be discharged
1.click view releasement 2. The system display view
icon releasement by reduction, view
3. The user as alternative releasement by apology and view
will choose one of the three releasing prisoner.
options. 4. The system will display the
5. Click copy to one folder desired prisoner files based on the
7user clicks send to HOI unique attribute given.
6. The system display the required
file
8.t
11. The system sends the request
for HOI for approval.
Table 3. 9 DISCRIPTION FOR SEND REQUEST MESSAGE FOR HOI

Use case name Send approval message to PIOAO Director
Actor HOI
32
Description The user is able to approve a request message about the approval
of discharging prisoners.
There must be a request file that have been sent by the director of
PIOAO
1.user clicks message. 2.system display message page.
3 user clicks the file. 4.System display file.
5.user click approve. 6.system sends approval
message to director of PIOAO.
Table 3. 10 DISCRIPTION SEND APPROVAL MESSAGE FOR PIOAO DIRECTOR

Use case name Send request message for PIOAO Director
Actor Director of SSO and director of MBO
Description The user is able to insert a specific prisoner
file register number on a search bar and send
request to director of PIOAO for a full access
of the file
The register number the user enters must be
available.
1.Clicks on a 4.system sends request
search bar to director of PIOAO.
2. insert register
number.
3.click send
request.
Table 3. 11 DISCRIPTION FOR SSO AND MBO DIRECTORS SENDING REQUEST MESSAGE

Use case name Send approval message to directors of SSO,
and MBO

Description The user is able to approve a request message
on getting the full file of the requested file.
There must be a request file that have been
sent by the director of PIOAO
1.user clicks 2.system display
message. message page.
3 user clicks the file. 4.System display file.
5.user click approve. 6.system sends
33
approval message to
director of PIOAO.
Frequency of use
Priority
Special requirement
Table 3. 12 DISCRIPTION FOR SEND APPROVAL MESSAGE FOR SSO AND MBO
DIRECTORS

Use case name View message
Actor Director of PIOA ,HOI, SSO and MBO
Description Viewing message either requesting for
approval or getting approval message
1.user clicks 2. System displays
message message.
3.user clicks 4.display specific
specific message message.
Table 3. 13 DISCRIPTION FOR VIEW MESSAG

Use case name Search by finger print
Description Searching specific prisoner file by using finger print searching
method
Precondition User name and password
User file must exist
1.The director will put the 3. System display page.
prisoner thumb on the finger 5. System display search by
print sensor finger print.
2.the logs in 7.system uploads finger print.
4. Click on search by finger 9.system relate the finger print
print. 10.system shows the file that
6. User click get finger print matches.
and chooses finger print.
8.user clicks find match
Table 3. 14 DISCRIPTION FOR SEARCH BY FINGER PRINT

Use case name Update
34
Description Update prisoner information whenever needed.
Prisoner’s information record must exist.
Post condition The prisoner information updated.
Basic course of action User action System respond
1.click view prisoner icon 2. The system will display view
3. The user as alternative will by gender, view by crime type
choose one of the three and search bar.
options. 4. The system will display the
5. Click one specific prisoner desired prisoner files based on the
file. unique attribute given.
7. Click the update button. 6. The system will display the full
9.the user will edit the file file of the required prisoner.
accordingly 8.the file will be editable
10.the user will click submit 11. The system will redirect to
button view prisoner page.
Table 3. 15 DISCRIPTION FOR UPDATE

Use case name Delete
Description Delete prisoner information whenever needed.
Precondition
1.click view prisoner icon 2. The system will display view by
3. The user as alternative gender, view by crime type and
will choose one of the three search bar.
options. 4. The system will display the desired
5. Click one specific prisoner files based on the unique
prisoner file. attribute given.
7. Click the delete button. 6. The system will display the full
file of the required prisoner.
8.the file will be deleted
9. The system will redirect to view
prisoner page.
Frequency of use
Priority
Special requirement
Table 3. 16 DISCRIPTION FOR DELETE

Use case name View statistical data
Actor Director of PIOA and HOI
Description Statistical report of the day is displayed in this
35
page
1.user click view 2.system displays
statistical report view statistical report
page
Frequency of use
Priority
Special requirement
36
4.5 Dynamic Modeling
4.5.1 SEQUENCE DIAGRAM

Sequence diagram describes the flow of messages being passed from object to object. It
represents a dynamic message between instances of classe
37
FIGURE 3. 1 SEQUENCE DIAGRAM FOR LOGINFIGURE
38
3. 2 SEQUENCE DIAGRAM FOR REGISTRATION
FIGURE 3. 3 SEQUENCE DIAGRAM FOR VIEW RELEASMENT FOR RELEASING

PRISONER
39
FIGURE 3. 4 SEQUENCE DIAGRAM FOR VIEW PRISONER BY GENDER TYPE
40
FIGURE 3. 5 SEQUENCE DIAGRAM FOR VIEW BY CRIME TYPE, UPDATE AND
DELETE FILE
41
FIGURE 3. 6 SEQUENCE DIAGRAM FOR VIEW BY SEARCHING
FIGURE 3. 7 SEQUENCE DIAGRAM FOR SEARCH BY FINGERPRINT
42
FIGURE 3. 8 SEQUENCE DIAGRAM FOR STATISTICAL REPORT
FIGURE 3. 9 SEQUENCE FOR SSO AND MBO SENDING REQUEST AND RECIEVING
APPROVAL
43
4.5.2 COLLABARATION DIAGRAM
Component of collaboration diagram
Figure 10: Collaboration diagram for login
44
Figure 11: Collaboration diagram for search Information
45
Figure 12: Collaboration diagram of generate report
46
4.5.3 Activity diagram
Figure 3. 10ACTIVITY DIAGRAM FOR LOGIN
47
Figure 3. 11ACTIVITY DIAGRAM FOR REGISTRATION
48
Figure 3. 12 ACTIVITY DIAGRAM FOR VIEW RELEASEMENT PAGE
49
Figure 3. 13 ACTIVITY DIAGRAM FOR SEARCH BY FINGER PRINT
50
Figure 3. 14 ACTVITY DIAGRAM FOR VIEW STATISTICAL REPORT
51
Figure 3. 15 ACTIVITY DIAGRAM FOR UPDATE FILE
52
Figure 3. 16 ACTIVITY DIAGRAM FOR DELETING FILE
53
Figure 3. 17 ACTIVITY DIAGRAM FOR SENDING APPROVAL MESSAGE
54
Figure 3. 18 VIEW MESSAGE
Figure 3. 19ACTIVITTY DIAGRAM FOR SSO AND MB DIRECTORS SENDING

REQUEST MESSAGE
4.6.1 CLASS DIAGRAM
Figure 3. 20 CLASS DIAGRAM

4.6.2 Object Diagram
55
56
57

Group Member Id

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Group Member Id

Uploaded by

Copyright:

Available Formats

MADDA WALABU UNIVERSITY

Title:GobaCity Online Prisoners’ Information Management System

Robsen Aliyi Coe/0032/10

Advisor Name Signature date

Examiner signature date

Project coordinator signature date

HOD signature date

Special thanks to our Advisors: mr- mohammed

1.1 Background of Project

1.2 Statement of the proplem

1.3 Objective of the Poject

1.4 Scope and Limitation of the Project

1.4.2 Limitation of the Project

1.5 Significance of the Project

1.6 Methodology and tools

1.6.2 System Analysis and Desgn

1.6.3 System Development Tools

1.6. 3.2 Hard ware requirement

1.7 Project Management

1.7.2 Project bufget (cost breakdown estimation)

Project Work break down structure

Task Group Name

System Requirement and specification All Group Member

Implementation and testing >>

1.7.4 Risk Analysis and Migration

Luck of time Medium By using night time

1.8 Feasibility Analysis

1.8.1 Technical Feasability

1.8.2 Economical Feasability

1.8.3 Polotical Feasability

1.8.4 Operational feasability

CHAPTER TWO:- STUDY OF EXISTING SYSTEM

2.2 LITERATURE REVIEW

2. 4 DRAW BACK OF EXISTING SYSTEM

2.5 Practices to be preserved from current system

2.6 BUSINESS RULE

2.7 ALTERNATIVE SOLUTION

 Make data processing automate communication by using web based

3.1 OVER VIEW OF PROPOSED SYSTEM

3.2 SYSTEM CONSTRAINT

3.3 FUNCTIONAL REQUIREMENTS

3.4 NON FUNCTIONAL REQUIREMENT

Openness : the define extend interface ti allow new data

GRAPHICAL USER INTERFACE

 The system of GUI is consistent with all other program

3.5.2 user interface description

4.2 ACTOR SPECIFICATION (IDENTIFICATION)

4.3 USE CASE IDENTIFICATION

4.4 SYSTEM USE CASE DIAGRAM

4.4.1 ACTOR DESCRIPTION:–

4.4.2 USE CASE DESCRIPTION:- DESCRIBE IN THE FOLLOWING

Use case number USC2

Use case number USC3

Use case number USC4

Use case number USC5

Use case number USC6

Table 3. 6 DISCRIPTION FOR VIEW RELEASEMENT BY REDUCTION

Use case number USC7

Table 3. 7 DISCRIPTIONFOR VIEW BY RELEASEMENT BY APOLOGY

Use case number USC8

Use case number USC9

Use case number USC10

Use case number USC11