You are on page 1of 14

Lovelycoding.

org
 PLACE YOUR ORDER
 CONTACT
 REVIEWS

PRISON MANAGEMENT SYSTEM


INTRODUCTION OF PRISON MANAGEMENT SYSTEM
Are you looking for Prison management system for your final year
project? We are here to help you. You can contact us
This system is named as Prison management system. This system is
made to keep the records about the prisoners and about the guards.
Jailor can log in as a user and can add the details of prisoners like
name, age, address, crime and punishment.

Jailor can also add the details about the different guards that are on
duty. Jailor can change attributes like time shift duty hours of guards.

Jailor can also write the First Information Report and can save it.
FIR’s date, time, number and details can be seen anytime if required
by the registered user.
This system gives the unique id to ever FIR as required and the
prisoner number will also be unique. This system has one more user
which is an admin. Admin can add the user(jailor) and delete the user.

All other attributes can only be changed by Jailor. This system tells
about when any prisoner gets its punishment period over so that he
she can be released. Prison management system can be implemented
in every prison without any problem.

This system has the-the capability to maintain an infinite number of


records.

It is very useful as the written papers have a limited time period and
can get lost but in prison management system this is not possible as a
backup file will be created automatically and also updated
automatically when any change is made in any record.

There is no option to delete a prisoners record because it may be


required later by the government to know any details about the person
and can help in the tracking of the prisoner.

Moving on Further we will see the designing of the system and


attributes of it on the principles of which our system does work
properly.

MODULES OF PRISON MANAGEMENT SYSTEM


Our system has two main interfaces one for Admin panel and other is
for User which is jailor. Along with these, we have other interfaces
which can be discussed as below:

Registration:
Users data need to be registered in the prison management system so
as to use the system and add the prisoner’s details, change the guard’s
duty shift etc.
If the user(jailor) is not registered in the-the prison management
system, he/she cannot do any task with it like writing FIRs, adding
prisoner crime and punishment details etc.

Login:
After registration one can log in the system as the operator of the
system on the behalf of user. After this, he has the other user
interfaces available for further actions.

Writing FIR:
The first option that is provided in the prison management system is
writing FIR. We all know FIR is First Information Report. All FIRs
have unique complaint number, date, time and location.

A similar interface is provided for writing FIR in this system. FIR


written cannot be lost and fast actions can be taken on the basis of it as
it will be uploaded on server and others can see it.

In this system, FIR has all the options that are in the old handwritten
system but is more secure as no changes can be made once the FIR is
submitted and only the authorized users can see it.

Adding Prisoner:
The second option that is given in this is the one of the most important
that is adding prisoner.

As soon as the court declares that the victim is found guilty and tells
his or her punishment and in which prison the victim must be kept,
the prisoner will be sent to the same prison as told by court and all the
details of criminal like name, address, age, criminal number, crime
and the punishment all can be updated in the prison management
system,

Then later these details can be used further and there is no option to
delete the prisoners data so once the prisoner is added to the database,
no one can delete the data of the criminal and it will be helpful as
papers can get lost or can be theft but in this case information cannot
be lost and there is no use of theft this data as no changes can be made
in the database.

Prisoners data cannot be lost because the backup of the database is


there and the backup gets updated as soon as the changes are made
into the database.

Adding and Deleting Guards:


The third important feature that is provided by this system is adding
and deleting the details about the guards of prison.

As we know that the government keeps transferring the people for


security reasons so it is important to know about the details of the
guards in the particular prison.

Therefore, an option is provided to the user to add the guards if any


new guard gets transferred and to delete the guard details if the guard
gets transferred somewhere else.

The options that are asked during adding a guard name, age, address,
shift and duty hours so that details of any guard can be checked.

If any guard gets transferred to somewhere else then there is an option


to delete the guard’s details.

SYSTEM DESIGN OF PRISON MANAGEMENT


SYSTEM:
Now this prison management system is designed in such a way that it
takes fewer resources to work properly. It has its own sort of minimum
requirements that we need to take care of :

The system needs a minimum of 2 GB of ram to run all the features


smooth and sudden.

It needs a minimum 1.3 GHz processor to rum smooth as less than


that may create problems.
The system needs to be operated by some authorized person as wrong
hands can make it irresponsible.

Rest is all up to the user’s usage will care for hardware

For security Antivirus is recommended.

The system is made properly and all the testing is done as per the
requirements. So the rest of the things depend upon the the-the user
and no one can harm the data or the software if the proper care is
done.

ER DIAGRAM OF PRISON MANAGEMENT SYSTEM:

Entity User:
can be performed only if the the-the user is authenticated. After the
user has registered and is verified by the admin then the user can
perform all the tasks on it. Some of the features of the user are as
follows:

Primary key User_id:


The user id is system generated and unique, which can be referenced
in any other entity. This mostly for recognizing it in the unique way
anywhere in the program.

Username:
Username is taken from the user and fed into this it is properly
validated so that no mistake happens.

Number:
The phone number is taken here to keep the member updated and for
the confirmation of the event is also managed through this method.

Email:
Email is taken to make member aware of new offers new events and
for future reference, it is also relevant. Password: Password is required
to login into the system and the password must contain a special
character, a numeric character and an uppercase letter.

Entity Admin:
Admin is only a single user which can verify the user who is trying to
register on this prison management system.

If the admin verifies the user then only the user can see the details and
can make changes according to the given privileges. No other user can
register as admin as there is only one account for admin.

Entity Prisoner:
The prisoner is the criminal who is found guilty and is in the prison for
his crime. A prisoner cannot do any change in this software as there
are no privileges given to them and their information can only be seen
only by the authentic user.
It has following attributes :

Primary key prisoner_id:


As we all know that all the prisoners in prison have a unique criminal
number so that is used here as a primary key.

Address:
As the prisoner is a criminal so for the record there must be prisoners
address so that if the criminal is required after completing his
punishment period in prison then he or she can be found on the
address.

Name:
Name of the prisoner is important as it is easy to found a person in
case it is required.

Crime:
The user must know that which prisoner is there and for which crime.
So the user can check it in the database whenever he wants and about
whoever he wants.

Punishment:
As the user must know about the crime he or she must also know
about the punishment period and the type of the punishment of the
prisoner. So an entity punishment is provided to know about the
punishment of the prisoners.

Entity Guard:
Guards are the one who keeps the surveillance over the prisoners.
Guards shifts are changed and their prison duty and duty hours are
also changed.

So it is also important to know about the guards of a particular prison


and the duty shift they have and their other details. Other attributes of
entity guard are as follows:
Name:
The user must know the names of the guards who are on duty in the
same prison.

Address:
If a guard gets hurt on the duty and in case his family needs to be
known about that then the guard’s address and the phone number is
required.

Shift:
The user must know about the shift of the guards so that all the guards
do their duty well.

Duty Hours:
Duty hours of the guards keep getting changed and it must be updated
into the prison management system.

USE CASE DIAGRAM OF PRISON MANAGEMENT


SYSTEM:
In this use case as you can see we have our system as box and the users
who use our system are of the kind of outside the box but related to
the system. There are two kinds of user one is admin and the other is
user type.

Users :
There is only a single type of user which is present here in this system.
This user has all the privileges but it cannot register itself on this
system as the admin needs to verify the registering user.

After the admin verifies the user only when he is eligible to use the
the-the system and after that, it has all the privileges.
Attributes given to the user are

Writing FIR:
The user can write FIR and can save it. The saved FIR can be seen only
by the valid users.
Prisoner:
In this attribute or column, the user can add the details about the
prisoners and there is no option to delete prisoner data once it is
added to the prison management system.

Guards:
his entity is about the details of the guards who are on duty and all
other details of them.

Admin panel :
There can be only one account of admin. Admin can add the users.
When a user tries to register on prison management system then the
request goes to admin and if the admin verifies only then the user can
register itself on it.

Other privileges that admin has been explained below :

He can Login through his id and password. The password is made very
secure so that no person can guess and make it difficult for hackers to
crack.

He has access to the profile of his own and he can search detail of
other Users and can see the detail of him.

This admin is responsible for creating and uploading the Menu card to
every User in the Interface.

He can add a user to that account and give access to for handling the
prison on their own.

He can manipulate the data of any user.In this, we are showing here
the interaction of the users with our system through our use case
diagram.
FUNCTIONAL AND NON-FUNCTIONAL
REQUIREMENTS OF PRISON MANAGEMENT
SYSTEM
The functional requirement of this is that it does what it is meant for.
A functional requirement describes what a software system should do,
while non-functional requirements place constraints on how the
system will do so.

Functional requirements specify a function that a system or system


component must be able to perform. It can be documented in various
ways.

The most common ones are written descriptions in documents and use
cases.

Few of its functional requirements are as given below:-

User data should be fed into the system:


This system is doing that properly in user entity.

The user can add the prisoners:


Users are able to add prisoners, which is they are doing with this
system.

Writing FIR:
The user can write the FIR and other complaint reports that the user
came to know about.

Able to add and delete guards:


The user can add the guards and their details and if required he or she
can also delete the details of guards of prison.

Non-Functional requirements of prison management system:-


Non-functional necessities square measure the other demand than
practical necessities. This square measure the necessities that specify
criteria which will be wont to choose the operation of a system, instead
of specific behaviours.

Non-functional necessities square measure within the style of “system


shall be “, associate degree overall property of the system as a full or of
a specific facet and not a particular operation.

The system’s overall properties remarkably mark the distinction


between whether or not the event project has succeeded or
unsuccessful.

Non-functional necessities – are often divided into 2 main categories:

Execution qualities, like security and usefulness, that square measure


evident at the runtime.

Evolution qualities, like liabilities, maintainability, flexibility and


quantifiable, that square measure embodied within the static structure
of the code.

Non-functional requirements of prison management system


necessities place restrictions on the merchandise being developed, the
event method, and specify external constraints that the merchandise
should meet

Our project qualifies all the criteria of functional and non-functional


accordingly and the system is up to mark performance vice. Here we
need to take care of few more things before heading towards the
system.

The the most important feature of application world is that


application’s ease of usage .application will easy to use if made while
keeping in mind that user need not think twice about searching any
feature.

Everything should be made distinctive by using the colour


combination such that everything needed most frequently highlighted
with focus colours. We can use simple layouts like the card and grid
layout etc.
By varying colour and other UI combination, many good intuitive
interfaces can be made. Which ultimately makes interface easy to use
for a long time.

Unlike ancient style wherever the goal is to form the thing or


application physically enticing, the goal of interface style is to form the
user’s interaction expertise as straightforward and intuitive as
attainable – what’s typically known as user-centred style.

Where smart graphic/industrial style is daring and eye-catching,


smart interface style is commonly delicate and invisible.

Keep things simple and consistent:-


Simple and Harmonic way making UI is very intuitive and needs to
followed

Make good use of typography:-


The typography is taken care very strictly as the need of the system.

Use colour and contrast properly:-


Color combo of lite and dark is good way emphasis and done well in
this system

Consider feedback messages:-


The feedback form is a very good way taking feedback of forms and
improving the system.

Simplified forms:-
The form is made simple to fill with the clean user interface.

PRISON MANAGEMENT SYSTEM PROJECT


DOCUMENTATION
CONCLUSION OF PRISON MANAGEMENT SYSTEM
So the outcome of all the-the hard work did for prison management
system is here. It is a software which helps the user to work with the
prisons easily. This software reduces the amount of manual data entry
and gives greater efficiency.

The User Interface of it is very friendly and can be easily used by


anyone. It also decreases the amount of time taken to write FIR details
and other modules.

At the end, we can say that this software is performing all the tasks
accurately and is doing the work for which it is made.

Leave a Reply

You might also like