PRISON MANAGEMENT SYSTEM

Table of Contents
Description

1.0 Introduction

1.1 Purpose

1.2 Scope

1.3 Definition, Acronyms, and Abbreviations

1.4 References

1.5 Technologies to be used

1.6 Overview

2.0 Overall Description

2.1 Product Perspective

2.2 Software Interface

2.3 Hardware Interface

2.4 Product Function

2.5 User Characteristics

 2.6 Constraints

2.7 Architecture Design

2.8 Use Case Model Description

2.9 Class Diagram
Sequence Diagram

2.10 Database Design

2.11.1 ER Diagram

2.11.2 Schema

2.12 Assumptions and Dependencies

3.0 Specific Requirements

3.1 Use Case Reports

3.2 Supplementary Requirements

CHAPTER – 1
 INTRODUCTION

1.1 PURPOSE:
This project is aimed at developing a
prison management system that is a collection of registers
and reports for the effective management of prisons. This
system should contain the modules like nominal roll, case
register, parole register, Interview requests, In-out register
and an automated release diary generator.

a .Nominal Roll:
The details of the prisoner and his/her
demographic details should be captured. A digital photo
comprising different views of the prisoner and the list of
articles surrendered by prisoner during nominal roll are to
be recorded.

b. Case register:
All the details of the cases against the
prisoner should be captured. This must include the
sentence details remand/conviction details, etc.

c. Automated release diary generator:

This report should
be display the list of prisoners to be released on a day, the
next day,the next week, the next month, or any given
duration of time. The system should consider the
reduction of sentence length due to various
considerations.

d. Parole register:
This module should track all prisoners
on parole and provide necessary reports on this data.

e. Interview requests and In-out register:

All interview
requests by the relatives of the prisoners need to be
recorded and tracked. An in-out register will track all
prisoners and others who move in and out for various
reasons. This should include provisions for recording the
prisoners sent to courts for hearing.

f. Various status reports and demographical analysis

reports are to be generated.

1.2 SCOPE:
1. The system should have a login.
2. System should support for Interview requests and
In-out register modules for visitors.
3. System should support for Data Entry module for
Nominal Roll, Case register for each prisoner entering in
the prison.
4. Automated release diary generator.
 5. Jailer should be able to generate various reports
Prisoner wise, case-wise.
6. Jailer should be able to generate Visitor reports
Prisoner wise and Visitor wise.

1.4 References
http://msdn.microsoft.com
http://java.sun.com
http://www.asp.net

1.5 Technologies to be used:

1. My SQL 5.1.5 along with Heidi SQL/PHP My
Admin
2. Eclipse/Net Beans IDE 6.9 with Java EE
3. Java EE 5 API
4. Apache Tom Cat 7.0.2
5. Adobe photo shop cs4
6. Magic Draw UML
7. Paint.NET
8. Open office 3.2
9. Windows XP professional
1.6 Overview:
SRS will include two sections: %__
Overall Description:
 Will describe major components of the
System, interconnection and external interfaces.
&__
Specific Requirements
Will describe the functions of actors, their role in
the system and constraints.

2.0 Overall Description:

Describe the general factors that affect
the product and its requirements.
2.1 Product Perspective:
The web pages
(XHTML/JSP) are present to provide the user interface on
customer client side. Communication between customer
and server is provided through HTTP/HTTPS protocols.
The Client Software is to provide the user interface on
system user client side and for this TCP/IP protocols are
used. On the server side web server is for EJB and
database server is for storing the information.

2. 2 Software Interface:
Client on Internet:
Web Browser, Operating System (any)
Client on Intranet:
Client Software, Web Browser, Operating System (any)
Web Server:
Apache Tomcat, Operating System (any)
Data Base Server:
My SQL, Operating System (any)

Development End: Net Beans

(J2EE, Java, Java Bean, Servlets, HTML), Database
server (My SQL), OS (Windows XP professional),
Apache Tomcat (Web Server).

2.3 Hardware Interface:

CLIENT SIDE

PROCEESOR RAM DISK SPACE

Internet explorer 6.0 CORE DUO AT 512 MB 80 GB

or above 1.6GHZ

SERVER SIDE

Apache Tomcat Pentium III at 1 512 MB 4 GB

7.0.2 GHz

My SQL 5.1.5 Pentium III at 1 512 MB 2 GB

GHz

2.4 Product Functions:

Class of use actors Use cases Description of use cases
involved
User account Jailer(admin) login Login into account
usage old visitor
Account New visitor register Registration for a new account
management Jailer(admin Issue Confirm new registration & issue new
account account ID
Viewing data Jailer(admin) View <Extends>
with admin registers 1. View nominal roll register
privilege 2. View case register
3. View parole register
4. View in-out register
Generating Jailer(admin) Report <Extends>
reports with generation 1. Prisoner wise report generation
admin 2. Case wise report generation
privilege 3. Visitor wise report generation
Interview Old visitor request Request for an interview with a prisoner
request
Jailer(admin) confirm Confirm interview request

Viewing Jailer(admin) View Viewing the date wise scheduled release of

release diary old visitor release prisoners
diary
Changing of Jailer(admin) Change Changing of password of user account
password old visitor password
The prison management system should
support this
Following use-case:
Class of use
Actors involved
Use cases
Description of Use cases
User Account
Jailer (ad min)
Login Login into Account
Usage
Old Visitor
Account
New Visitor Register Registration for a New account
Management
Jailer (ad min) Issue Account Confirm new registration & Issue
New Account ID
Viewing Data
Jailer (admin) View
<Extends>
with admin
Registers
1.view nominal roll register
privilege
2. View case register
3. View parole register
4. view in-o ut register
Generating
Jailer (admin) Report
<Extends>
Reports with
Generation
1.
admin privilege
generation
2. Case wise report generation
3. Visitor wise report generation
Interview
Old Visitor Request Request for an interview with a
prisoner
Request
Jailer(admin) Confirm Confirm Interview Request
Viewing Release
Jailer(admin)
View Release
Viewing the date wise scheduled
Diary
Old Visitor
Diary
release of prisoners
Changing of
Jailer(admin)
Change
Changing of password of user
password
Old Visitor
Password
Account

3.0 Specific Requirements:

1. FUNCTIONAL REQUIREMENTS:
We describe the functional requirements by giving
various use cases:

1. USE CASE RELATED TO LOGIN:

Primary actor
All registered users having valid accounts
1) Jailer (admin)
2) Old Visitor

Precondition
INTERNET connection is available and working at it's
optimal level

Main scenario
1) Users Access the login Page
2) Provide User ID and Password.
3) Login Validity is checked
4) The user is shown their respective homepage.

Alternate scenario
1) The entered is not valid
2) The user is shown the error page.
2. USE CASE RELATED TO REGISTRATION:

Primary actor
Unregistered New Visitor

Precondition
none