PRISON MANAGEMENT SYSTEM

MINI PROJECT REPORT

Submitted in partial fulfillment of the requirement for the award of the degree of Bachelor of Technology in Information Technology of the University of Calicut

Submitted By: ABHISHEK T.T MAHESH P MUHAMMED FASIL M

DEPARTMENT OF INFORMATION TECHNOLOGY KMCT COLLEGE OF ENGINEERING MANASSERY (P.O), CALICUT KERALA 2011

K.M.C.T COLLEGE OF ENGINEERING CALICUT

DEPARTMENT OF INFORMATION TECHNOLOGY CERTIFICATE

This is to certify that this Mini Project Report titled PRISON MANAGEMENT SYSTEM is the record of the work done by ABHISHEK T T (CTAIEIT001), MAHESH P (CTAIEIT019) and MUHAMMED

FASIL M (CTAIEIT022) of sixth semester, Information Technology, towards the partial fulfillment of the requirements for the award of the Degree of Bachelor of Technology by the University of Calicut .

PROJECT GUIDE
Mrs. Supriya Joseph Lecturer Kmctce Place: Date:

HEAD OF THE DEPARTMENT

ACKNOWLEDGEMENT

We would like to express our sincere thanks to the director Dr. V B Panicker of KMCT College of Engineering, Calicut. We express our deepest sense of gratitude to the Dean of the Department of Information Technology Mr. Pratap G Nair for his valuable advice and guidance. We express our deepest sense of gratitude to the Head of the Department of Information Technology Mrs . Sameera Muhammed Salam for her valuable advice and guidance. With immense pleasure and heartiest gratitude, we express our sincere thanks
Mrs. Supriya Joseph Lecturer in Information Technology for his valuable

suggestions and guidance. We also thank our staff members and dear friends for their kind hearted support and encouragement. Above all, we thank the almighty for enabling us to be what we are.

MUHAMMED FASIL M

ABSTRACT

This project is aimed at developing a prison management system that is a collection of registers and reports for the effective management of prisons. Basically prison is a correctional institution where persons are confined while on trial or for punishment. Each prison may have hundreds of criminals. With hardcopy of records it is hard to search report or record about a particular criminal in prison.

The purpose of this document is to present a detailed description of the Prison Management System. The document will describe what the system will do, the constraints under which it must operate and how the system will react to external stimuli. This system should contain the modules like nominal roll, case register, parole register, visitors details and automated release diary.

Nominal Roll: The personal details of each prisoner are stored including his\her digital photograph.

Case register: All the details of the cases against the prisoner should be captured. This must include the IPC section, case description etc.

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

Visitors details: This module includes the details of the visitors who visit the prisoners in the jail.

Automated release diary generator: This report should be display the list of prisoners to be released on next seven days.

Report generation: the details of each prisoner can be retrieved in the form of a report. We can take print of the report.

This software will be a client application built on the c#.net and sql platforms. This software system will be a prison management system for prison department. This system will be efficient collection of records and reports about the prisoners in prison. Besides police officers and higher government authorities can see reports about prisoners easily. The public can search their relatives or friends who are imprisoned for certain lawful detention, about the crime, place where they imprisoned or release date of imprisoned person. More specifically, this system will design to allow a data manager to add/update record about prisoners and administrator who may be prison administrator or government higher official to have full access rights. The police officer can search record about prisoner with confidential data. This software includes the following features.
y y y

The system has two users, administrator and jailor. The system should have a unique login for each users. System should support for Data Entry module for Nominal Roll, Case parole register and visitors details. register,

The system should be able to view the registered details at the time of need.

Our project consisted of various chapters that describe our whole project .There are mainly six chapters for our project .In the first chapter ,requirement analysis and specification provides the details for how the user interviews are conducted. DFD, ER, context analysis diagrams are designed and finally the detailed specific requirement specification document also. The chapter includes the narration of proposed system and its advantages over existing system .The chapter deals with the proposed system, problems

encountered in the existing system .The system requirement specification which deals with the product perspective product functions are also included in this chapter.

The second chapter of the project is design analysis and specification. The Software Design Document is a document to provide documentation which will be used to aid in software development by providing the details for how the software should be built. Within the Software Design Document are narrative and graphical documentation of the software design for the project prison management system.

This document is a high level design document (HLDD) of the system. The intended audiences for this document are the individuals, who want to store and retrieve information about each prisoner. As described software is implemented using C#. Knowledge in the specific fields of dot net will be much helpful for the reader to understand the contents easily.

In the design chapter, we have completed the design of our process and the database. In the database design we have designed the tables which describe the fields, constraints and the descriptions. In the process design, various screenshots related to our project have been made.

The third chapter of the project is coding. The document coding provides the details on different modules of source codes which are developed by the programmer and the details about the standard library functions used for the development of indented software. This chapter describes about the tools and technologies used for coding in great detail.

The fourth chapter of our project is testing. The chapter testing describes various testing methodologies which are adapted and detailed view of test datas within each database.

During testing of a program to be tested is executed with a set of test data and the output of the program for test data is evaluated.

The fifth chapter deals with implementation. Implementation is a process of converting a new system into an operational one. The designed system is converted into an operational one using a suitable programming language. Implementation includes all those activities that take place to convert an old system into a new one. Proper implementation is necessary to provide a reliable system to meet organizational requirement

The sixth chapter deals with the operations manual. The operations manual provides userfriendly input and output forms that have been designed with interactive dialogue. It enables the end users to insert details very easily through corresponding interface forms. In this section we deals with various screenshots of our project

TABLE OF CONTENTS

CHAPTER 1: REQUIREMENT STUDY AND ANALYSIS 1.1 Features, working and problem definition 1.2 Feasibility 1.3 Project plan 1.4 User interview 1.5 Existing system 1.6 Proposed system 1.7 Requirement analysis 1.8 Software and hardware requirements 1.9 General description 1.10 Specific requirements 1.11 Functional requirements 1.12 Identification of entities & attributes 1.13 Context analysis diagram (CAD) 1.14 Data flow diagram (DFD) 1.15 Entity-relationship diagram (ERD) 1.16 Conclusion 12 14 15 15 16 17 17 18 18 18 19 20 21 26 28 12

CHAPTER 2: DESIGN SPECIFICATION 2.1 Introduction 2.2 Database design 2.3 Process design 2.4 Conclusion 29 29 34 35

CHAPTER 3: CODING 3.1 Introduction 3.2 Tools and technology 3.3 Code 36 36 37

CHAPTER 4: TESTING 4.1 Introduction 4.2 Unit testing 4.3 Integration testing 4.4Validation testing 4.5 System testing 4.6 Test data 4.7 Conclusion 51 51 51 51 52 53 55

CHAPTER 5: IMPLEMENTATION 5.1 Introduction 5.2 Implementation plan 5.3 Conclusion 56 56 56

CHAPTER 7: OPERATIONS MANUAL 7.1 Introduction 7.2 Screenshots 7.3 Conclusion 57 57 72

APPENDIX A: BIBILIOGRAPHY

LIST OF TABLES

Table 1.1 Project plan Table 1.2 Entities & Attributes Table 2.1 Login Table 2.2 Nominal roll register Table 2.3 Case register Table 2.4 Parole register Table 2.5 Visitor details Table 4.1 User login Table 4.2 Nominal roll Table 4.3 Case register Table 4.4 Parole register Table 4.5 Visitor table

LIST OF FIGURES

Fig 1.1 Fig 1.2 Fig 1.3 Fig 1.4

Line diagram for user registration Context Analysis Diagram Data Flow Diagram Entity Relationship Diagram

LIST OF SYMBOLS

Process

Data Flow

Database

LIST OF ABBREVIATIONS

PMS - Prison Management System CAD - Context Analysis Diagram ERD - Entity-Relationship Diagram SRS - Software Requirements Specifications DFD - Data Flow Diagram

CHAPTER 1

REQUIREMENTS STUDY AND ANALYSIS

Introduction Basically prison is a correctional institution where persons are confined while on trial or for punishment. Each prison may have hundreds of criminals. With hardcopy of records it is hard to search report or record about a particular criminal in prison.

In jail all the information about each prisoner should be stored and retrieved at the time of requirement, here we propose prison management system which makes possible an effective management of prisoners in jail.

With this project, we could be able to store and retrieve all the information about the prisoners in the jail. The information may include personnel details, case details, parole details and visitors details. This system will be efficient collection of records and reports about the prisoners in prison. Besides police officers and higher government authorities can see reports about prisoners easily. The public can search their relatives or friends who are imprisoned for certain lawful detention, about the crime, place where they imprisoned or release date of imprisoned person. More specifically, this system will design to allow a data manager to add/update record about prisoners and administrator who may be prison administrator or government higher official to have full access rights. The police officer can search record about prisoner with confidential data.

The document requirement specification provides the details for how the user interviews are conducted. DFD, ERD, context analysis diagrams are designed and finally the detailed specific requirement specification document also. The chapter includes the narration of proposed system and its advantages over existing system. 1.2 Feasibility Study Consider the three primary areas of feasibility analysis: economic, technical, operational. There was no need to economically justify this project and it is clear that the technology

exists to satisfy the needs identied. Brief legal research did not reveal any barriers. Existing software products were investigated to determine whether this problem had been solved previously. Products with the desired features exist, but no individual product was found with the desired combination of features. Hence, an o -the-shelf product was not a viable solution and it was worth developing custom software. 1.2.1 Technical Feasibility A study of function, performance and constraints may improve the ability to create an acceptable system. Technical Feasibility is frequently the most difficult area to achieve at the stage of product engineering process. Considering that are normally associated with the technical feasibility include,
y y y

Development risk Resource availability Technology

Technical Feasibility study deals with the hardware as well as software requirements. The scope was whether the work for the project is done with the current requirements and existing software technology has to be examined in the feasibility study. The outcome was found to be positive. In the proposed system, data can be easily stored and managed using database management system software. The reports and results for various queries can be generated easily. Therefore, the system is technically feasible. 1.2.2 Operational Feasibility Proposed projects are beneficial only if they can be turned into information system that will meet the organizations operating requirements. Simply stated, this test of feasibility asks if the system will work when it is developed and installed. Are these major barriers to implementation? The purpose of the operational feasibility study is to determine whether the new system will be used if it is developed and implemented from users that will undermine the possible application benefits.

There was no difficulty in, implementing the system and the proposed system is so effective, user friendly and functionally reliable so that the users in the company will find that the new system reduce their hard steps. If the user of the system is fully aware of the internal working of the system then the users will not be facing any problem in running the system. 1.2.3 Economic Feasibility Proposed system was developed with the available resources. Since cost input for the software is almost nil the output of the software is always a profit. Hence software is economically feasible. In the existing system, manpower is more required. In the proposed system, number of employees to be involved is reduced drastically. So, the proposed system is said to be economic. In the existing system, storage of the records should be properly done and security should be provided for the records. In the proposed system, the software provides security and maintenance and it hardly needs one or two persons to operate the system.

1.3 Project Plan Our group consists of three members and we worked together according to a detailed plan to ensure quality in all aspects for assigning tasks to each member clearly. Project name: PRISON MANAGEMENT SYSTEM (PMS) Project site: Jail Internal Guide: Mrs. Supriya Joseph Duration Team members: ABHISHEK T T MAHESH P MUHAMMED FASIL M

Table 1.1 Project plan Sl no 1 2 3 4 5 6 7 8. Activity description Topic identification Feasibility study User interview Requirement analysis SRS preparation Design Coding Testing, Implementation Role All members All members All members All members All members All members All members All members Start date 8/03/11 13/03/11 16/03/11 18/03/11 27/03/11 8/04/11 27/4/11 22/06/11 Target date 13/03/11 15/03/11 17/03/11 26/03/11 1/04/11 21/04/11 20/04/11 2/07/11

1.4 User Interviews In order to understand about the jail system, the requirement analysis had been conducted at district jail, Calicut. As per the project start up and planning procedure, our team went there and interacted with Mr. Subhramanian (Jailor, grade 1). He had provided us the details of existing manual system. From there, we came to know that how the existing system works. By describing the great process in details, we can divide the entire process into three major processes. 1. Entering the data: Various informations about the prisoners is entered by the responsible officers. 2. Updating the data: The information entered can be update at the time of need. 3. View the details: The information which are stored can be retrieve at the time of need.

1.5 Existing System Existing system for prison management is a manual system. In this system personal details, case details and parole details of the prisoner are kept in a register in the hand written format. The details of the prisoner are accessed from this register at the time of need. This system has got a lot of limitations.

1.5.1 Limitations of Existing System:  Redundancy problem.  No data security and reliability, chance of malpractice is very high.  Information retrieval is a slow process.  Less efficient.  Expensive.  Requires more man power.  Probability of occurrence of error is high.  Maintaining personal and case details of the prisoner is a tedious process.  Probability of occurrence of data loss. 1.6 Proposed System The proposed system which is very fast and efficient can be used conveniently as an alternative to the existing manual system. In this proposed system we implements prison management. In this system the details of the prisoners are registered by officials. And each official will have to log in using this there id and password. This will help in exact identification of each entry into the proposed system to view the details update. The overall procedure done in the system is shown in the figure. The proposed system has got lot of advantages 1.6.1 Advantages of Proposed System:
1. 2. 3. 4. 5. 6. 7.

Reduces the consumption in the communication time. Reduces the time consumption in the preparation of various manual works. Enables quick references of necessary details. Effective implementation is possible. This is a user friendly system. High speed and accuracy. Efficient and Reliable.

8.

Provides data security. 9. Less man power. 10. Get updates to People as soon as the events are updated in the database.

1.6.2 Decomposition of proposed system:

There are six main modules in the proposed system. They are the following.

1. Nominal roll: The personal details of each prisoner are stored including his\her digital photograph. 2. Case register: All the details of the cases against the prisoner should be captured. This must include the IPC section, case description etc. 3. Parole register: This module should track all prisoners on parole and provide necessary reports on this data 4. Visitors details: This module includes the details of the visitors who visit the prisoners in the jail. 5. Automated release diary generator: This report should be display the list of prisoners to be released on next seven days. 6. Report generation: The details of each prisoner can be retrieved in the form of a report. We can take print of the report. 1.7 Requirement Analysis Requirement analysis is a process of understanding the customer needs and expectations from a proposed system or application and is a well-defined stage in software development life cycle model. This provides an effective prison management system which is a collection of registers and reports, which is more reliable, user friendly and thorough interaction with the database.

Requirements are the description of how a system should behave or a description of system properties and attributes. It can alternatively be a statement of what an application is expected to do.

A dedicated and specialized requirement analyst is best equipped to handle the jobs. The requirement analysis function may also fall under the scope of project manager, program manager, depending on the organizational hierarchy. 1.8 Software and Hardware Requirements

1.8.1 Hardware Interfaces

y y y

Processor RAM Hard disk free space

: Intel Pentium IV & above : Min 1GB : Min 2 GB

Hardware configuration is that the physical components used for the developing of the project. The best hardware environment provides the developer with the best utilization of the available resources. The importance of hardware configuration comes into scene when the project development is in its peak utilization of the systems physical resources. It can be observed that for developing a software project, one needs a better and higher configuration of the hardware than which is needed for its actual plan. In this case a good set of hardware resources must be present there for the smooth running of .NET environment. 1.8.2 Software Interfaces This project is a windows application that is developed in C#.NET having MS-SQL Server as back end. 1. Operating System 2. IDE 3. Database Design 4. Input Designs 5. Coding : Windows : Microsoft Visual Studio 2008 : MS-SQL Server : Windows Forms & Microsoft Chart Control : C#.NET

This is the software configuration in which the project was shaped. The programming language used, tools used, etc are described here.

1.9 General Description The existing prison management system is a manual process. It is very expensive and time consuming. This process needs more human resources, lots of paper works, data querying and updating inconvenience and huge amount of time. Our main goal is to improve the value of the existing system. By using this software we can store and retrieve the various details about the prisoners in the jail. 1.10 Specific Requirements There should be minimum and specific requirements for our system to be active. Mainly there are two categories they are hardware as well as software complexities. 1.11 Functional Requirements Our system mainly contain two user, an administrator and jailor. Various processes involved by these users are:  Login (Login in to the system by using a user name and a password)  Issue account (Administrator issue new account to the jailor)  Change password (Both administrator and jailor can change their password if needed)  Add details (A new entry of details of a prisoner, parole details and visitor details)  Update details (Updating the prisoners personal and parole details)  View register (Viewing details about the prisoner, parole and visitor details)  Generate report (Reporting the personal and case details of the prisoners)  View release diary (To view which prisoners going to be released in next seven days)

1.12 Identification of Entities & Attributes Entities Nominal roll register Attributes Prisoner id Case id Crime details Name Age Sex Entry-date Last-date Duration of sentence Height Room number Weight Pervious status Snap Address Status Case register Case id Description Ipc section

Parole register

Prisoner id Parole id Parole date Parole duration

Reason for parole Status of prisoner Visitor details Visitor name Address Prisoner id Prisoner name Visit date Start time End time Purpose of visit

Table 1.2 Entities & Attributes

1.13 Context Analysis Diagram (CAD) The Context Analysis Diagram (CAD) may be used to represent the top level overviews of the existing system. The CAD is drawn to represent the state of the system during the requirement analysis phase. The CAD shows the system as a single process represented by a circle at the center of the model. There shall always be only one system process in a CAD. The model shows entities external to the system process. The entities are representative of the existing significant objects in the current system scenario. The external entities are connected to the central process through connectors representing the information flowing into/ out of the system. CAD should be drawn with the help of latest version of the Turbo Analyst tool available with the company.

Administrator

Jailor

PRISON MANAGEMENT SYSTEM

Fig 1.1 CAD

1.14 Data Flow Diagram (DFD) A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system. Data flow diagram is also known as Bubble Chart and has the purposes of classifying the system requirement and identifying major transformation that will become programs on system design so it the starting point of the design phase that functionally decomposed the requirement. Data flow diagram consists of series of Bubbles and lines. Bubbles represent the data transformation and line represents the dataflow. The following table list important elements of DFDs.  Data Store  Data Process  Actor  Data Flow 1.14.1 Data Store

A data store responds to request to store and access data. It does not generate any operations. A data store allows values to be accessed in an order different form the order in which they were generated. Input flows indicate information or operations that modify the stored data such as adding or deleting elements or changing values. Output flows indicate information retrieved from the store, information value or a component of a value.

Data store

1.14.2 Data Process

A data process transforms data values.

Data Process The name of a process is usually a description of the transformation it performs. If a process is open, It can either create a new DFD or open an existing DFD in which the process is specified. The data flows of the opened process are connected in the new diagram to the process with the name of the opened process.

1.14.3 Actor

An actor produces and consumes data, driving the DFD.

Actor

Data flows between an actor and a diagram are inputs to and outputs of the diagram. The system interacts with people through the actor.

1.14.4 Data Flow A data flow moves data between processes or between processes and data stores. It represents a data value at some point within at some point within a computation and an intermediate value within a computation if the flow is internal to the diagram. Its value is not changed.

Data Flow

The names of input and output flows can indicate their roles in the computation or the type of the value they move. Data names are preferably nouns. The name of a typical piece of data, the data aspect is written alongside the arrow.

Data Flow Diagrams: LEVEL 0:

USER

Re qu

est

Resp on

se

PMS

DATABASE

LEVEL 1:

in

to

r o

tr

is

in

IL

I I

IL

LEVEL 2:

"!

"!

o in it u s e rn e p ss o r

U SE R

R E I S TR A TI

 

 " ! ' " '& % $ # "!' " '& % $# 

E

pl

er



o in

ADMINISTRAT OR

LOGIN

LOGIN

CHANGE PASSWOR D

ISSUE ACCOUNT

VIEW PERSONAL DET AILS OF YHE PRISONER

VIEW CASE DETAILS

VIEW PAROLE DET AILS

VIEW VISITORS DET AILS

UPDATE

ADD CASE DETAILS

NOM INAL ROLL REGIS TER

CAS E REGISTER

P AROLE REGIS TE R

VIS ITOR TABLE

LEVEL 3:

JAILO R

LOGI N

LOGI N

VIEW AUTOMATI C RELEAS E DIARY

CHANGE PAS S WO RD

GENERAT E REPO RT

ADD PERS ONA L DETAILS

ADD AS E DETAILS

ADD PAROLE DETAILS

ADD VIS ITOR DETAILS

VIEW PERS ONAL DETAILS O F PRISONER

VIEW CAS E DETAILS

UPDAT E

UPDAT E

NOMINAL ROLL

CASE REGI STER PAROLE REGI STER

1.15 Entity-Relationship Diagram (ERD) The Entity Relationship Diagram (also known as an ERD or E-R diagram) is a network model that describes the stored data layout of a system at a high level of abstraction. The ERD should represent the relationships between all the entities. Any two entities must be connected to each other by some relationship set and type of relationship should also be specified. 1.15.1 Components of an ERD There are two major components of an ERD: Entity:

VIEW PAROLE DETAILS

VIEW VISITOR DETAILS

UPDAT E

VI SI TOR TABLE

Figure 1.2

It is defined as any object about which information is collected. It has different attributes which describe it. It should be represented by a regular box as shown below: Relationships: Entities are connected to one another by relationships. a relationship represents a set of connections between entities and represent by a diamond. A relationship is a two-directional significant association. There are three types of relationships
y y y

One-to-one relationships One-to-many relationships Many-to-many relationships

ERD:Jailor Admin

Visitor Details

Parole Register

Nominal Roll

Case Register

Fig 1.3 ERD Conclusion

The subsection of the chapter provides an overview of proposed system design and its other functional requirements clearly and precisely.

CHAPTER 2

DESIGN SPECIFICATION
Introduction The Software Design Document is a document to provide documentation which will be used to aid in software development by providing the details for how the software should be built. Within the Software Design Document are narrative and graphical documentation of the software design for the project identifying our project prison management system. As described software is implemented using C#. Knowledge in the specific fields of dot net will be much helpful for the reader to understand the contents easily. 2.1.1 Purpose The purpose of the Software Design Document is to provide a description of the design of a system fully enough to allow for software development to proceed with an understanding of what is to be built and how it is expected to build. The Software Design Document provides information necessary to provide description of the details for the software and system to be built. 2.1.2 Scope This Software Design Document is for a base level system which will work as a proof of concept for the use of building a quality system that provides a base level of functionality. This particular Software Design Document gives the detailed requirement specification of the design of the prison management system, which helps the developers and analysts for the further updates on the software. 2.2 Data base design A data base is a collection of related data. By data, we mean known facts that can be recorded and that have implicit meaning. Defining a database involves specifying the data types, structures, and constraints of the data to be stored in the database. The general objective is to make database access easy, quick, inexpensive and flexible for the users. Normalization is done to get internal consistency of data and to have minimum redundancy

and maximum stability. This ensures minimizing data storage required and optimizing for updates. The data in the system has to be stored and retrieved from database. Designing the database is a part detailed designing. Data elements and data structures to be stored have been identified in the analysis stage. They are structured and put together to design the data storage and retrieval system. Ms-Sql is the database of the system. It provide a secure, accurate and data management. While designing database, several objectives must be considered:
y y y y y

Controlled Redundancy Data Independence Accuracy and Integrity Privacy and Security Performance

The normalization process takes a relation schema through a series of tests to certify whether it satisfies a certain normal form. The process, which proceeds in a top-down fashion by evaluating each relation against the criteria for normal forms and decomposing relations as necessary, can thus be considered as relational design by analysis. There are mainly three normal forms: first, second, and third normal form. All these normal forms are based on a single analytical tool: the functional dependencies among the attributes of a relation. Normalization of data can be considered a process of analyzing the given relation schemas based on their FDs and primary keys to achieve the desirable properties of,
y y

Minimizing redundancy Minimizing the insertion, deletion, and update anomalies.

Unsatisfactory relation schemas that do not meet the normal form tests are decomposed into smaller relation schemas that meet the tests and hence the desirable properties. The normal form of a relation refers to the highest normal form condition that it meets, and hence indicates the degree to which it has been normalized.

First normal form

First normal form (1NF) states that the domain of an attribute must include only atomic values and that the value of any attribute in a tuple must be a single value from the domain of that attribute. Hence, 1NF disallows relations within relations or relations as attribute values within tuples. The only attribute values permitted by 1NF are single atomic values.
y

Second normal form

Second normal form (2NF) is based on the concept of full functional dependency. A functional dependency is a full functional dependency if removal of any attribute does not hold the dependency any more. A relation schema is in 2NF if every nonprime attribute in relation is fully functionally dependent on the primary key of that relation.
y

Third normal form

Third normal form is based on the concept of transitive dependency. A relation schema R is in 3NF if it satisfies 2NF and no nonprime attribute is transitively dependent on the primary key. Our project is fully normalized up to second normal form where each key is fully depending on the primary key. The database of our project is designed using ms sql and it comprise of 5 tables. 2.2.1 Tables
y y y y y

Login: This table contains the login details. Nominal roll register: This table contains the prisoners details. Case register: This table contains the IPC sections. Parole register: This table contains the parole details. Visitor details: This table contains the visitors details.

N0. 1

Field name Username

Type of field Varchar(50)

Remarks Primary key

2 3 4

Password User type Status

Varchar(50) Varchar(50) Bit

Table.2.1 Login

No. 1 2 3 4

Field Name Prisoner id Case id Crime details Name

Type of variable Int Int Varchar(50) Varchar(50)

Remarks Primary key Foreign key

Special characters like underscore are not allowed.

5 6 7 8 9 10 11 12 13 14 15

Age Sex Entry-date Last-date Duration of sentence Height Weight Room number Pervious status Snap Address

Int Varchar(50) Date Date Int Int Int Int Varchar(50) Varchar(50) Varchar(50) Permanent address of prisoner Y/N No of days Height in cms In Kgs M/F

16

Status

Int

1: in jail 2:on parole 3: released 4:dead 5:transfer to another jail 6:break

Table.2.2 Nominal Roll Register

No.

Field Name

Type of variable

Remarks

1 2

Case id Description

Int Varchar(50)

Primary key Special characters like underscore are not allowed.

Ipc section

Varchar(50)

Table.2.3 Case Register

No. 1 2 3 4 5 6

Field Name Prisoner id Parole id Parole date Parole duration Reason for parole Status of prisoner

Type of variable Int Int Date Time Date Int

Remarks Primary key Foreign key

1.in jail 2.on parole

Table.2.4 Parole Register

No. 1 2 3 4 5 6 7 8

Field Name Visitor name Address Prisoner id Prisoner name Visit date Start time End time Purpose of visit

Type of variable Varchar(50) Varchar(50) Int Varchar(50) Date Time Time Varchar(50)

Remarks Primary key

Foreign key

Table.2.5 Visitor Details

2.3 Process Design

2.3.1 Input Design In Input Design we mainly concerned about the Input Process. The data must be inputted to the system to produce the required output. The aim of making input design is to make the data entry as early as possible and free from errors. An input format should be logical and easy to understand. In the design, the user oriented inputs are converted into computer recognizable format. The collection of data is the most expensive part of the system in terms of the equipment used, time and no. of clients involved etc. In the input design data is accepted and it can be readily for data processing or can be stored in a database for further use. The used forms used for inputs are very user friendly. Different names are associated with each data entry form item makes data entry an easy job. Each data entry contains a separate buttons for submitting the form and proper validation checking is carried out and necessary message will be presented to the user incase of improper data entry. All the design work is done in Microsoft visual studio Environment so that it is very easy to design as all the options and programming is inherent there and their code is automatically written in source code file. Any change made during the design phase is automatically reflected in source code. 2.3.2 Output Design It has been an ongoing activity from the beginning of the project. It includes the process of finalizing of the medium format and exact contents of each output to be produced by the proposed system. The primary objective in creating an output is accuracy and neatness. To refine sketches into detailed description of output, we have planned output with specific medium .The major outputs are crystal reports generated by visual studio. Various processes included in our system are given below:
y y y y y

Case details Prisoner details Parole details of the prisoner Details of the visitors Reports

Automatic release diary

2.4 Conclusion The document contains the detailed design of database, user interfaces which include input and output design separately and finally the process decomposition also.

CHAPTER 3

CODING

3.1 Introduction The document coding provides the details on different modules of source codes which are developed by the programmer and the details about the standard library functions used for the development of indented software. This chapter describes about the tools and technologies used for coding in great detail. 3.2 Tools and Technologies The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. To provide consistent object-oriented programming environment whether object code is stored and executed locally but Internet distributed, or executed remotely code-execution environment that , minimizes software deployment and versioning conflicts, that guarantees safe execution of code, including code created by an unknown or semi-trusted third party, that eliminates the performance problems of scripted or interpreted environments. 3.2.1 C Sharp .NET The C# programming language (pronounced "C-Sharp") is one of the most powerful object-oriented programming languages developed by Microsoft. According to them, "C# is a modern, object-oriented language that enables programmers to quickly build a wide range of applications for the new Microsoft .NET platform, which provides tools and services that fully exploit both computing and communications." Actually, C# was originally codenamed "Cool" before being released as a beta in 2000. Microsoft then released different versions of the language including the latest release of C# 2.0. With each release, the product shipped with improved features for developing secured and scalable applications along with high quality documentation and code samples. Some of the notable features of the C# programming language are namespaces, type-safe variables, multi-dimensional arrays, jagged arrays, operator overloading, indexers, delegates, versioning, attributes and overriding. C# also comes with features like "pass by

reference" and "pass by value" for parameters, XML based documentation with special comment tags. Integration with COM components developed using Visual Studio 6.0. Further, C# has also been approved as an International Standard Organization (ISO) standard. C# is a simple, modern, object oriented, and type-safe programming language derived from C and C.C# aims to combine the high productivity of Visual Basic and the raw power of C++. C# is a strongly-typed object oriented language designed to give the optimum blend of simplicity, expressiveness and performance. Classes and data types are common to all of .NET languages. Using C# we may develop console applications, windows applications and web applications. In C# Microsoft has taken care of C++ problems such as memory management, pointers etc. It supports garbage collection and automatic memory management.
y

Features of C#  Pointers are missing in C#.  Unsafe operations such as direct memory manipulation are not allowed.  In C# there is no usage of "::" or "->" operators.  Since its on .NET, it inherits the features of automatic memory management and garbage collection.  C# has been based according to the current trend and is very powerful and simple for building interoperable, scalable, robust applications.  C# includes built in support to turn any component into a web service that can be invoked over the Internet from any application running on any platform.  C# supports Data Encapsulation, inheritance, polymorphism, interfaces.  In C# we cannot perform unsafe casts like convert double to a Boolean.

3.2.2 SQL Server 2008 Microsoft SQL Server 2008 is comprehensive, integrated data management and analysis software that enables organizations to reliably manage mission -critical information and confidently run todays increasingly complex business applications. SQL Server 2008 allows companies to gain greater insight from their business information and achieve faster results for a competitive advantage.

SQL is high-level language that provides more abstraction than third generation languages. The most important feature of SQL is its use of English-like syntax. This syntax is much easier to understand and because of this it is easier to understand and because of this it is easier to understand and is smaller in size, they are also easier to learn, code and maintain.

3.3 Code 3.3.1 Reusable codes Reusable codes can be used in anywhere by changing the parameters according to their purpose. 1. For Inserting Values Into The Table cinfo.Description = TextBoxdescrptn.Text; cinfo.IpcSection = TextBoxipcsectn.Text; 2. Link Code Response.Redirect("AdminHome.aspx"); Response.Redirect("JailorHome.aspx"); 3. To Take The Values Into Textbox TextBoxDuration.Text = Duration.Days.ToString(); 4.Session Code Session["Username"] = info.Username.ToString(); Session["Usertype"] = info.Usertype.ToString(); 5. Dropdown List Binding ninfo.CaseId= int.Parse(DropDownList1.SelectedValue); 6. Gridview Binding string PrsnrId = GridView1.SelectedDataKey.Value.ToString();

Code: 1. Login public partial class Login : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void Login1_Authenticate(object sender, AuthenticateEventArgs e) { LoginInfo info = new LoginInfo(); LoginService ser = new LoginService(); info = ser.LoginCheck(Login1.UserName, Login1.Password); if ((info.Usertype == "admin") && (info.Status == true)) { Session["Username"] = info.Username.ToString(); Session["Usertype"] = info.Usertype.ToString(); Response.Redirect("ChangePassword.aspx"); } else if ((info.Usertype == "jailor") && (info.Status == true)) {

Session["Username"] = info.Username.ToString(); Session["Usertype"] = info.Usertype.ToString(); } } }

Use: The procedure login is used for the login process.

2. Change Password public partial class changepassword : system.web.ui.page { protected void page_load(object sender, eventargs e) { labelincorrect.visible = false; } protected void button1_click(object sender, eventargs e) { string curpass = textboxcurrpass.text; string user = session["username"].tostring(); logininfo info = new logininfo();

loginservice ser = new loginservice(); string getpass = ser.getpassword(user); if (getpass == curpass) { string conpass = textboxcofrmpass.text; ser.changepassword(user, conpass); string user = session["usertype"].tostring(); if (user == "admin") response.redirect("adminhome.aspx"); else if (user == "jailor") { response.redirect("jailorhome.aspx"); } } else { labelincorrect.visible = true; } } protected void buttoncancel_click(object sender, eventargs e)

{ string user = session["usertype"].tostring(); if (user == "admin") response.redirect("adminhome.aspx"); else if (user == "jailor") { response.redirect("jailorhome.aspx"); } } }

Use: It changes the current password of Administrator into new password. Similarly there is a code for changing password of Jailor.

3. Issue Account public partial class IssueAccount : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void Button1_Click(object sender, EventArgs e) { LoginService ser = new LoginService(); ser.IssueAccount(TextBoxusername.Text, TextBoxPassword.Text);

Response.Redirect("AdminHome.aspx"); } protected void Button2_Click(object sender, EventArgs e) { TextBoxusername.Text = ""; TextBoxPassword.Text= ""; } }

Use: This procedure is used to issuing account to the jailor by administrator.

4. Registration public partial class Registration : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void TextBoxCrimeDetails_TextChanged(object sender, EventArgs e) { } protected void Button1_Click(object sender, EventArgs e) { NominalInfo ninfo = new NominalInfo(); NominalRollService ser = new NominalRollService(); ninfo.CaseId= int.Parse(DropDownList1.SelectedValue); if (RadioButtonMale.Checked == true) { ninfo.Sex = "Male"; } else ninfo.Sex = "Female";

if (DropDownList2.SelectedItem.Text == "Yes") ninfo.PreviousStatus = true; else ninfo.PreviousStatus = false; ninfo.CrimeDetails = TextBoxCrimeDetails.Text; ninfo.PrisonerName = TextBoxName.Text; ninfo.DateOfBirth =BasicDatePickerDOB.SelectedDate.Date.ToShortDateString(); ninfo.EntryDate = DateTime.Parse(BasicDatePickerEntry.SelectedDate.Date.ToShortDateString()); ninfo.LastDate = DateTime.Parse(BasicDatePickerLast.SelectedDate.Date.ToShortDateString()); ninfo.DurationOfSentence = int.Parse(TextBoxDuration.Text); ninfo.CurrentStatus = "In jail"; string filename = FileUpload1.FileName; string extension = System.IO.Path.GetExtension(filename); string save_path = Server.MapPath("Snaps" + "\\" + TxtSnapName.Text + extension); FileUpload1.PostedFile.SaveAs(save_path); ninfo.Snap ="~/Snaps/" + TxtSnapName.Text + extension; ninfo.Height = int.Parse(TextBoxHeight.Text); ninfo.Weight=int.Parse(TextBoxWeight.Text); ninfo.RoomNumber=int.Parse(TextBoxRoom.Text); ninfo.Address=TextBoxAddress.Text; ser.insert(ninfo); Response.Redirect("AdminHome.aspx"); } protected void TextBoxName_TextChanged(object sender, EventArgs e) { } protected void BasicDatePickerDOB_SelectionChanged(object sender, EventArgs e) { } protected void BasicDatePickerLast_SelectionChanged(object sender, EventArgs e) {

} protected void LinkButDuration_Click(object sender, EventArgs e) { TimeSpan Duration = BasicDatePickerLast.SelectedDate.Date.Subtract(BasicDatePickerEntry.SelectedDate.Date ); TextBoxDuration.Text = Duration.Days.ToString(); } protected void Button2_Click(object sender, EventArgs e) { Response.Redirect("AdminHome.aspx"); } protected void TextBoxHeight_TextChanged(object sender, EventArgs e) { } } Use: This procedure is used for prisoner registration.

5. Parole Details public partial class Parole : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { GridView2.Visible = false; MultiView1.SetActiveView(LinkView); } public static int ParoleId; protected void Button1_Click(object sender, EventArgs e) { ParoleInfo pinfo = new ParoleInfo(); ParoleRegister ser = new ParoleRegister();

pinfo.PrisonerId = int.Parse(TextBoxPrisonerId.Text); pinfo.ParoleDate = DateTime.Parse(BasicDatePickerParoleDate.SelectedDate.Date.ToShortDateString()); pinfo.EndDate = DateTime.Parse(BasicDatePickerEndDate.SelectedDate.Date.ToShortDateString()); pinfo.ReasonForParole = TextBoxReason.Text; pinfo.StatusOfPrisoner = "In Jail"; ser.insert(pinfo); } protected void GridView1_SelectedIndexChanged(object sender, EventArgs e) { string PrsnrId = GridView1.SelectedDataKey.Value.ToString(); TextBoxPrisonerId.Text = PrsnrId; MultiView1.SetActiveView(AddView); } protected void LinkButAdd_Click(object sender, EventArgs e) { MultiView1.SetActiveView(AddView); } protected void LinkButton1_Click(object sender, EventArgs e) { MultiView1.SetActiveView(DetailsView); } protected void ButParole_Click(object sender, EventArgs e) { Session["ParolDt"] = BasicDatePicker1.SelectedDate.ToString(); GridView2.Visible = true; MultiView1.SetActiveView(DetailsView); } protected void GridView2_SelectedIndexChanged(object sender, EventArgs e) { ParoleId = int.Parse(GridView2.SelectedDataKey.Value.ToString()); BasicDatePicker1.SelectedValue = "";

MultiView1.SetActiveView(UpdateView); } protected void Button3_Click(object sender, EventArgs e) {

ParoleInfo pinfo = new ParoleInfo(); ParoleRegister pser = new ParoleRegister(); DateTime k = BasicDatePickerParoleDateUpdat.SelectedDate; string i = DropDownList1.SelectedItem.Text; int j = ParoleId; pser.UpdateParoleStatus(i,j,k); Response.Redirect("Parole.aspx"); } protected void Button2_Click(object sender, EventArgs e) { Response.Redirect("JailorHome.aspx"); } } Use: This procedure is used for add parole details.

6. Visitor Details public partial class Visitor : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { MultiView1.SetActiveView(LinkView); GridView2.Visible = false; } protected void Button1_Click(object sender, EventArgs e) { VisitorInfo vinfo = new VisitorInfo();

VisitorService ser = new VisitorService(); vinfo.VisitorName = TextBoxVisitorName.Text; vinfo.Address = TextBoxAdress.Text; vinfo.PrisonerId = int.Parse(TextBoxPrisonerId.Text); vinfo.PrisonerName = TextBoxPrisonName.Text; DateTime bd = BasicDatePickerVisitDate.SelectedDate.Date; vinfo.VisitDate = DateTime.Parse(BasicDatePickerVisitDate.SelectedDate.Date.ToShortDateString()); vinfo.StartTime = TimePickerStart.SelectedTime.ToString(); vinfo.EndTime = TimePickerEnd.SelectedTime.ToString(); vinfo.PurposeOfVisit = TextBoxPurpose.Text; ser.insert(vinfo); } protected void GridView1_SelectedIndexChanged(object sender, EventArgs e) { string PrsnrId = GridView1.SelectedDataKey.Value.ToString(); TextBoxPrisonerId.Text = PrsnrId; NominalRollService ser = new NominalRollService(); NominalInfo inf = new NominalInfo(); inf = ser.DetailsBasedOnPrisonerId(int.Parse(PrsnrId)); TextBoxPrisonName.Text = inf.PrisonerName.ToString(); MultiView1.SetActiveView(AddView); } protected void LinkButAdd_Click(object sender, EventArgs e) { MultiView1.SetActiveView(AddView); } protected void LinkButton1_Click(object sender, EventArgs e) { MultiView1.SetActiveView(DetailsView); } protected void Button3_Click(object sender, EventArgs e) {

DateTime VisitDate = BasicDatePicker1.SelectedDate; Session["VD"] = VisitDate.ToString(); GridView2.Visible = true; MultiView1.SetActiveView(DetailsView); } } Use: This procedure is used for add visitor details,

7. View Release Diary public partial class release : system.web.ui.page { protected void page_load(object sender, eventargs e) { session["currentdate"] =system.datetime.now; session["enddate"] = system.datetime.now.adddays(7); } }

Use: This procedure is gives the details of prisoner they are going to be released in next 7 days.

Conclusion Various subsections of this chapter give an overview of source codes and its usage in the software development.

CHAPTER 4

TESTING

4.1 Introduction The chapter testing describes various testing methodologies which are adapted and detailed view of test datas within each database. During testing of a program to be tested is executed with a set of test data and the output of the program for test data is evaluated. 4.2 Unit Testing Unit Testing is a procedure used to validate that individual units of source code are working properly. A unit is the smallest testable part of an application. In procedural programming a unit may be an individual program, function, procedure, etc., while in object-oriented programming, the smallest unit is a method; which may belong to a base/super class, abstract class or derived/child class. Ideally, each test case is independent from the others; mock objects and test harnesses can be used to assist testing a module in isolation. Unit testing is typically done by developers and not by Software testers or endusers 4.3 Integration Testing Integration testing is the phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing. Integration testing takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing. The purpose of integration testing is to verify functional, performance and reliability requirements placed on major design items. 4.4 Validation and testing Software validation is achieved through a series of tests that demonstrate conformity with requirements. Validation succeeds when software functions in a manner that can be reasonably expected by the end user. Testing is necessary for the success of the system.

During testing of a program to be tested is executed with a set of test data and the output of the program for test data is evaluated to determine if t e programs are performing as h expected. First the application goes through a phase often referred as alpha testing in which the errors and failures based on simulated user requirements are verified and studied. The modified software is then subjected to phase two called beta testing in the actual users site or live environment. After a scheduled time, failures and errors are documented for final correction and enhancements are made before the package is released In our project, validation and checks have been done in order to ensure that the developed system is performing up to its expectation. Validations have been done in the area of login sections and add details sections. In add details section, certain rules have been set like no field is left blank. In this way each field in the data entering sections are checked, checking for user name availability and reporting status. In the login pages appropriate messages are displayed when a user provides an invalid response. 4.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. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic. It is the process of executing the program with the intent of finding errors Testing cannot show the absence of defects; it can only show that software errors are present. Functionality Testing Tested forms in all pages: Forms are the integral part. Firstly checked all the validations on each field like user name and password, checking whether all mandatory fields are filled and so on. Checked by providing wrong inputs to the fields in the forms and found they are responding appropriately. Wrong input include like proving an invalid user name or password.

Checks have been made to ensure whether the database functions are working. Like when a new user registers with the site there is database query regarding this. So, these queries are tested by looking into the actual database whether all entries have been affected to the database. If this is not the case, query is checked and rectified. Database checking was positive.

4.6 Test data

4.6.1 Login

User name Jailor Administrator Ja Saaa

Password Jail Admin Mp Shmnn Table 4.1 User login

Remarks Valids Valids Invalid Invalid

4.6.2 Nominal Roll

Prisoner id

Case id

Crime details

Name

Age

Sex

12 8 5 22

4 14 9 8

robbery

raja

45 28 36 30

Male Male Male Male

Terror attack kasab Rape Public nuiscence Santhosh m Santhosh p

14

14

Terror attack Afsal Guru

32

Male

Entry date

Last date

Duration of sentence

Height

Weight

Room no.

1\1\2011 12\10\2010 28\11\2009 12\06\2010 14\11\2010

25\10\2013 28\12\2012 15\11\2012 8\11\2050

297 442 1083 14483

158 Asd 178 170 172

59 65 68 55 61

123 29 445 27 36

Previous status No No Yes No Yes

Snap

Address

Status

Remarks

Img Img Img Img Img

Chennai Islamabad Kochi Ernakulam Noida

In jail In jail In jail In jail In jail

Invalid Valids Valids Valids Invalid

Table 4.2 Nominal roll

4.6.3 Case Register

Case id 4 11 9 8 14

Description Robbery Murder Rape Public nuisance

IPC section

Remarks Invalid

322 167 265 32\1\A Table 4.3 Case register

Valids Valids Valids Invalid

4.6.4 Parole Register Prisoner id 7 9 18 10 33 16 13 22 9 28 Parole id Parole date 22\12\2010 8\04\2010 11\03\2011 31\05\2011 04\01\2011 26\04\2010 14\03\2011 11\06\2011 04\07\2011 Personal Death End date Reason Status of Remarks

for parole prisoner Hospital Death Injail Injail Injail Injail Injail Valids Valids Invalid Valids Invalid

Table 4.4 Parole register

4.6.5 Visitor table Visitors name Karnanidi Goerge Close Muthu lakshmi Raju address Chennai Londan Berlin Sathyamangalal Balarama Prisoner id 12 27 32 10 13 Prisoner name Raja Stephan Ballack Veerappan Radha Visit date 22\04\2011 30\11\2004 22\09\2008 18\05\2007 3\09\2009

Start time 8:00am 10:00am 1:30pm 10.00 am 9.00 am

End time 8:30am 10:30am 2:00pm 10.30 am 9.30 am

Purpose of visit Personal Court Death Personal

Remarks Valid Valid Valid Valid Invalid

Table 4.5 Visitor table 4.7 Conclusion Various subsections of the chapter provides an overview of validation and testing process.

CHAPTER 5

IMPLEMENTATION
5.1 Introduction Implementation is a process of converting a new system into an operational one. The designed system is converted into an operational one using a suitable programming language. Implementation includes all those activities that take place to convert an old system into a new one. Proper implementation is necessary to provide a reliable system to meet organizational requirement 5.2 Implementation plan Our project is a desktop application. User only needs a system with minimum requirements. Since we are not incorporating any complex hardware parts, it can be implemented anywhere very easily. Expertise knowledge is not needed to handle our project. A user with his/her basic knowledge can access it and use it safely. The user can use this without any training. Only thing user has to do is to just enter their data where it is required. The user can also retrieve the entered data at the time of need. then the user can generate reports and print the produced report.

In the implementation plan the requirements for implementing the project is determined and also tested to confirm the effectiveness while implementing the project design into the source code. The main goal of the implementation plan is the development of source code that is easy to read and understand. The implementation plan will help the project to proceed with the available resources. Once the implementation plan is over the source code can be developed easily because it will provide a clear idea about the project. The implementation of the proposed system is achieved via to the C#.net platform as front end and MSSQL as backend. Front end consist of language tools and mechanisms for manipulating the backend. 5.3 Conclusion Implementation describes about the whole activities necessary to provide a reliable system to meet the necessary requirement.

CHAPTER 6

OPERATIONS MANUAL
6.1 Introduction The user manual provides user-friendly input and output forms that have been designed with interactive dialogue. It enables the end users to insert details very easily through corresponding interface forms.

6.2 Screen Shots

Login page

This is the login page used by both administrator and jailor.

Fig 6.1 Login page

Admin Homepage

This is the home page of administrator.

Fig 6.2 Administrator page

Jailor Home Page

This is the home page of jailor.

Fig 6.3 Jailor home page

Issue Account

This form is used to for issuing account to the jailor by administrator.

Fig 6.4 Issue account page

Add Case Details

This form is used by the administrator to add case details.

Fig 6.5 Add case details page

Change Password

This form is used by the administrator to change the password.

\ Fig 6.6 Change password page

Add Prisoner Details

This form is used by the jailor to add prisoners personal and case details.

Fig 6.7 Add case details page

View Prisoner Details

This form is used by the jailor to view the details of prisoner.

Fig 6.8 View prisoner details

Update Prisoner Details

This form is used by the jailor to update the prisoners details.

Fig 6.9 Update prisoner details page

Add Parole Details

This form is used by the jailor to add the parole details of prisoner.

Fig 6.10 Add parole details

View Parole Details

This form is used by the jailor to view the parole details.

Fig 6.11 View parole details page

Update Parole Details

This form is used by the jailor to update the parole details.

Fig 6.12 Update parole details

Add Visitors Details

This form is used by the jailor to add the details of visitor.

Fig 6.13 Add visitors details page

View Visitors Details

This form is used by the jailor to view the details visitor.

Fig 6.14 View visitors details page

View Release Diary

This form gives the details of prisoners to be released in next 7 days.

Fig 6.15 View release diary page

Report Generation

This form gives the report of prisoners.

Fig 6.16 Report generation page 6.3 Conclusion Screen shots provides a simple user guide, to identify the user interface & various functions of the system.

APPENDIX 1

REFERENCE

www.scribd.com www.google.com www.freetemplate.com

BIBLIOGRAPHY
y

Fundamentals of Database Systems By Ramezelmsari,Shamkanthb.Navathe,Durvasulu V.L.N Somayajulu,Shyamk.Guptha. The McGraw hill companies, 3rd edition, 2007.

Professional asp.net 2.0 by Bill Evjen, Scollhanselman,Farhanmuhammed, Srinivas, Devin Rader. Wiley publishing inc 2006.

Professional C# 2005 by Christ Nagan, Bill Evjen, Jay Glynn,Karleywatson,Morganskinner,Allen Jones. Wiley publishing inc 2006.

Software Engineering a practitioners approach By Roger S.Iipressman. the McGraw hill companies, 6th edition, 2005.