Database For Criminal Record Management System

CRMS
Criminal Record Management System
Muhammad Danish Naseem
Muhammad Rizwan
Muhammad Jahanzeb Tariq
Faheemullah
Kamran Ali
Contact : mrizwan969@gmail.com
Introduction
Police provides safety to citizens. It always remains steady for arresting any
criminal who is a threat for the safety of society. After registering the FIR
from any citizen, police starts its work and on that basis it arrests the
criminals if proofs are found against them. Once the criminals are arrested,
police starts investigation from them. After getting all the proofs against the
criminal, it is the duty of the police to present all the proofs honestly to the
court so that the right man can get right punishment. The true and right
information provided by the people to police helps a lot in arresting the
criminals who try to spoil the peaceful environment of society.
Along with low salary scale, facilities of modern technology such as

computerized system of keeping records are not provided to police
department which causes low efficiency. As it is the age of computers and all
the organizations today use computers to maintain their records, so this
facility should also be given to police department in order to increase their
efficiency and to save their time.
In our Project we are going to implement a CRMS (Criminal Record

Management System). This is a database system in which police will keep
the record of Criminals who have been arrested, to be arrested or escaped.
This will help the Police department to manage their records easily. In police
system when an incident occurs, a Petitioner reports an FIR (First Information
Report). Police starts investigation according to law on this FIR. An
investigation Officer supervises the investigation process. The main
concerning people in the whole process are Petitioner (The person who files
an FIR), Victim, Accused/Criminal, investigation officer.
CRMS will keep the record of following entities:
ENTITIES
These are the entities of CRMS.
1. Petitioner
2. Victim
3. Accused
4. FIR
5. Case
6. Investigation Officer
Petitioner:
A person who is seeking legal help from police station or he has some
problem or complaints regarding the matters under the jurisdiction of police.
Petitioner may or may not be the victim of offense.
Victim:
"Victim" means an individual who suffers, in relation to an offence.
FIR:
First Information Report (FIR) is a written document prepared by the
police when they receive information from the Petitioner about the
commission of a cognizable offence.
Accused:
"Accused" means a person who is charged with an offence or crime.
Case:
Case is the issue to be investigated by the police and resolved by the
court.
Investigation officer:
“Investigation officer” is the police officer who investigates the
case. There may be more than one investigation officers in one police
station.
ATTRIBUTES OF ENTITIES
Petitioner:
Definition:
A person who is seeking legal help from police station or he has some
problem or complaints regarding the matters under the jurisdiction of police.
Anyone who knows about the commission of a cognizable offence can file an
FIR. It is not necessary that only the victim of the crime should file an FIR.
A police officer who comes to know about a cognizable offence can file an FIR
Himself/herself.
You can file an FIR if:
1. You are the person against whom the offence has been committed
2. You know yourself about an offence which has been committed
3. You have seen the offence being committed.
Attributes:
The Petitioner has the following attributes
Name:
The full name of Petitioner.
Father_name:
The father name of Petitioner.
Address:
Address of Petitioner.
Contact:
Contact number of Petitioner.
NIC:
National identity card number of Petitioner.
Identifier:
NIC+NAME:
Since NIC number is the only attribute of a Petitioner which is unique

and no Petitioner can file FIR without NIC due to which it can never be an
unknown value (null value) but it can be duplicate in fraudulent cases so we
take NIC and NAME as an identifier.
Definition:
Every criminal case has an investigation officer who finds and examines the nature of the
case, witnesses and evidences to find the criminal.
Attributes:
The investigation officer has the following attributes
Name:
The full name of the investigation officer.
Officer ID:
Every police officer has got some ID so the code or ID of investigation
officer is another attribute.
Rank:
The rank of an investigation officer.
Identifier:
Officer ID:
As every police officer has a unique ID so we can take officer ID as an
identifier.
Case:
Definition:
A file in which daily detail of a case are written down by the investigating
officer
The police may not investigate a complaint even if you file a FIR, when:
(i) The case is not serious in nature;
(ii) The police feel that there is not enough ground to investigate. However,
the police must record the reasons for not conducting an investigation and in
the latter case must also inform you.
Attributes:
Case ID:
Each case is assigned an ID.
Section_of_law :
Through section of law we can find a lot about nature of the case E.g.
the criminal act and its sentence accordingly.
Case Status:
It’s another attribute of entity case, through which we can find whether
the case is closed or open.
Case detail:
The detail of the case is written here.
Identifier:
Case ID:
Since each case has its own unique identifier which is it’s ID so we take
case ID as an identifier, which can never be an unknown value.
Accused:
Definition:
Accused is the person who commits a crime. It is the most important
entity in our DB because our whole project is based upon this entity. So
that’s why is also related to most of the entities. And also we are concerned
with most of its attributes to watch an accused as easily as possible.
Attributes:
Accused_ID:
It is assigned by the police department whenever a perosn either guilty
or not suffers from police investigation or in any sort of procedures remains
unique for the whole life
Name:
In this attribute the name against an accused id is entered.
Father_Name:
In this attribute the Father’s name against an accused id is entered.
Alias:
Alias is the nick name sort of thing which is popular among the people
and is very important these days because one accused usually is not known
as his real name and has several nick names that’s why Alias is a
multivalued attribute.
Address:
In this attribute the expected or permanent address of accused is
saved. It is also multivalued because one may have many addresses.
NIC:
If the NIC of accused is known then it is saved in this attribute.
Gender:
Gender of accused.
Age:
The age of accused is entered in this attribute.
Status:
The status of accused is entered like either he is
Arrested,Escaped,Bailed or Released.
Contact:
It is composite attribute. In this attribute we list the mobile number or
land line number and email address of the accused.
It is composed of following attributes
Phone:
The phone number of the accused. It is multivalued attribute because
an accused can have more than one contact numbers.
Email:
The email id of the accused.
Photo:
The picture identity of the accused.
Finger print:
The finger print of the accused stored for identification purpose.
Identifier:
Accused_ID:
Accused ID is the sole identifier for accused because all other
attributed becomes multivalued in case of dangerous criminals whose
identity is not confirmed. Once accused id is assigned to a criminal then we
start filing other available attributes.
FIR:
Definition:
First Information Report (FIR) is a written document prepared by
the police when they receive information about the commission of a
cognizable offence. It is a report of information that reaches the police first in
point of time and that is why it is called the First Information Report.
It is generally a complaint lodged with the police by the victim of a
cognizable offence or by someone on his/her behalf. Anyone can report the
commission of a cognizable offence either orally or in writing to the police.
Even a telephonic
message can be treated as an FIR.
Importance of FIR
An FIR is a very important document as it sets the process of criminal
justice in motion. It is only after the FIR is registered in the police station that
the police take up investigation of the case.
Attributes:
FIR_ID:
Once FIR is longed against any sort of complaint an ID is assigned to it.
Date_lodged:
The date on which FIR is lodged.
Time_lodged:
The time of FIR being lodged.
Detail:
The detail of an FIR consists of following attributes.
Incident Place:
The place on which complained incident took place.
Incident Date:
The date on which complained incident took place.
Incident Time:
The time on which complained incident took place.
Identifier:
FIR_ID:
FIR ID is identifier of an FIR because it is kept in record of police
department filing that specific FIR against a compliant. So a specific ID will
always toward the unique incident.
Victim:
Victim is a person is a person which is affected by any sort of activity
by the accused. He might be dead or alive due to the crime committed.
Attributes:
Name:
The name of the victim is entered in this attribute.
Father_Name:
Father name of accused person.
Address:
The address of the victim is entered in this attribute.
Contact:
The contact information of the accused is entered in this attribute like
phone# etc.
Identifier:
Name +Address:
One name can exist on more than one address, but it is not possible
that two persons with same name have same address.
RELATIONSHIPS BETWEEN
ENTITIES
Petitioner and FIR
➢ Petitioner files an FIR
➢ There is one-to-many relationship between Petitioner and FIR
because
➢ One Petitioner can file more than one FIRs.
➢ But one FIR is filed by one and only one Petitioner.
➢ It is not possible that an FIR is lodged by unknown Petitioner.
➢ Hence we conclude that cardinality of Petitioner is mandatory
one.
➢ According to the definition of Petitioner it is necessary for a person to
be a Petitioner that he/she must file at least one FIR.
➢ Hence the cardinality of FIR is mandatory-many.
Accused and FIR
➢ FIR is lodged or filed against accused

➢ One FIR can be lodged against more than one accused
➢ One FIR can be lodged against unknown accused or criminal
➢ Similarly there may be more than one FIRs against one accused but
one accused will have at least one FIR against him.
➢ In this relationship cardinality of FIR is mandatory-one
➢ and cardinality of accused is optional-many
FIR and Victim
➢ FIR is filed by Petitioner for a victim who is suffered from offence.
➢ There can be one or many victims for one FIR.
➢ There is one and only one FIR for a victim.
➢ Cardinality of FIR is mandatory one.
➢ Cardinality of victim is one-many.
FIR and Case

➢ FIR initiates a Case
➢ Case is dependent on FIR.
➢ When a Petitioner files an FIR, the Police analyze the report whether it
is a valid report and needs a case to be initiated or the issue would be
solved without filing a case.
➢ The police may not investigate a complaint even if you file a FIR, when:
➢ The case is not serious in nature;
➢ The police feel that there is not enough ground to investigate.
➢ The police must record the reasons for not conducting an investigation
and in the latter case must also inform you.
➢ If the complaint is a crime according to Law, then a case is initiated.
➢ Either one or no case can be initiated (filed) on one FIR.
➢ Cardinality of FIR is mandatory one.
➢ Cardinality of case is optional one.
Investigation Officer and Case

➢ Investigation officer investigates the case
➢ Investigation officer must investigate at least one case
➢ Investigation officer may investigate more than one case at the same
time
➢ A case is investigated by one and only officer
➢ Hence the cardinality of investigation officer is mandatory-one
➢ And cardinality of case is mandatory many
ER-Model
(Entities and their relationships)
RELATIONAL MODEL
• Name and rank are attributes of entity investigation officer
• Officer_ id is primary key
Officer_ ID Name Rank
Case:
• Case status , section of law ,case detail are the attributes and Case_ ID
is primary key of entity case
• Since it has one-to many relationship with FIR and Investigation officer
that is why FIR_ID and Officer_ id are added as foreign key attributes
in this relation
Case_ Section_ of_ Case_Det

Case_ ID FIR_ID Officer_ ID
status law ail
Petitioner:
• Father_name, Address and Contact are attributes and the NIC and
Name is primary key of Petitioner.
NIC Name Father_ name Address Contact
FIR:
• Date_ logged, Time_ Lodged, Incident_ time, Incident_ place, Incident_
date is attributes and FIR_ID is primary key of FIR.
• P_NIC and P _Name is foreign key since FIR has one to many
relationship with petitioner.
• Victim _Name and Victim _address is foreign key since FIR has one to
many relationship with Victim.
Date Time Victi
Incide Incide Incide Victim
Petitioner Petitioner_N _ _ FIR_ m
nt_ nt_ nt_ _addre
_NIC ame lodg lodg ID _Nam
time Place date ss
ed ed e
Accused:
Name, Father_ Name, Status, Photo, Age, Email, Gender, and NIC is
attributes and Accused_ ID is primary key of accused, where as
accused Address, accused Phone and Accused Alias is multi valued
attributes of accused.
FIR_ID is the foreign key since accused has a one-to–many relationship

with FIR.
Accused_ Addres
ID s Accused_
Phone Accused_ Alia
ID
ID s
Accused_ Address:
Accused_ Phone: Accused_Alias:
Accused_
Alias:
Accused:
Nam Father_na Stat Phot Ag Gend Ema Finger_pr NI Accused FIR_I
e me us o e er il int C _ID D
Victim:
• Father_ Name , contact is attributes of Victim and Name , Address is
the primary key.
Name Address Father_ Contac

Name t
Officer_ Name Rank
ID
Case_ Case_ Section_ of_ Case_ FIR_I Officer_

ID status law Detail D ID
Case:
Petitioner:
Time
Victi Incide
Petitio Petition _ Incide Incide
m Victim_add Date_Lod nt_ FIR_
ner er_ nt nt
_Nam ress ged ID
_NIC Name lodg _time _Place
e date
ed
NIC Name Father_ name Address Contact
FIR:
Victim:
Name Address Father_ Contac
Name t
Accused
Phone
_ID
Accused:
Nam Father_na
Accused_ Stat Phot Ag Gend Ema Finger_pr NI Accused FIR_I
e me Alias o
us e er il int C _ID D
ID Accused_
Address
ID
NORMALIZATION
First Normal Form
All the tables in relational model are in 1NF because they fulfill the definition
of relation. i.e there are no multi-valued attributes
Second Normal Form
Investigation Officer:
• Name and Rank can be determined by officer_id (primary key)
• Officer_ID è Name , Rank
• This implies that there is no partial functional dependency in this

relation. Hence
• The relation “Investigation_officer” is in 2nd Normal Form
Officer_ID Name Rank
Case:
Case_ Case_statu Case_Descri Section_of_l FIR_I Officer
ID s ption aw D _ID
• Case_ID è Case_status , Case_Description, Section_of_law
• No partial functional dependency
• “Case” is in 2nd Normal Form
Petitioner:
NIC Name Father_nam Address Contact
e
• NIC +Nameè Name,Father_name,Address,Contact
• Only NIC cannot be determinant because fraud cases can cause

duplicate NIC values
• No Partial functional dependency
• Relation “Petitioner” is in 2nd Normal Form
Victim:
• Father_name and contact can be determined exactly if name and
address both are known because name is not unique similarly address
is also not unique but name+address collectively is unique
• Hence there is no partial functional dependency
Father_na
Name Address Contact
me
FIR:
• FIR_ID è Date_lodged , Time_lodged ,Incident_place, incident_date
• Relation “FIR” is in 2nd Normal Form
Complainant Date_lod Time_lod Incident_t Incident_P Incident_d FIR_I

_ID ged ged ime lace ate D
Accused:
• Accused_IDèName,father_name,status,gender,age,nic,email

• Relation “Accused” is in 2nd Normal Form
Nam Father_na Stat Ag Gend NI ema Phot Fingure_Pr Accused FIR_I

e me us e er C il o ints _ID D
Accused_Address:
Accused_ID Address
Accused_Contact:
Accused_ID Phone_No
Accused_Alias:
Accused
_ID Alias
Above three relations Accused_Address, Accused_Alias, Accused_Contact are

in 2nd normal form.
Third Normal Form
In the relation “Accused” NIC seems to be the possible determinant for

the Name , Address , Fathers_name , Gender and Age of the accused
but the problem is that it is an optional attribute that its value can be
null(unknown) because mostly accused NIC# is not known for several
reasons. So there is no transitive dependency here and our relation is
in 3NF.
All the other relations are in 3NF because there are no transitive
dependencies.
PHYSICAL MODEL
// paste physical model here
IMPLEMENTATION
SQL Implementation:
Note: All the following queries are written for Oracle XE so this SQL script
may need some variations while running on some other DBMS product
Petitioner_T:
CREATE TABLE Petitioner_T(
NIC VARCHAR2(15) NOT NULL,
Name VARCHAR2(50) NOT NULL,
Father_name VARCHAR2(50),
Address VARCHAR2(100),
Contact NUMBER(12,0),
CONSTRAINT Petitioner_PK PRIMARY KEY(NIC,Name)
);
• Primary key is composed of NIC and Name that is why NOT NULL
constraint is applied to these columns
FIR:
CREATE TABLE FIR_T(
FIR_id NUMBER(5,0) NOT NULL,
Incident_date DATE NOT NULL,
Incident_time TIMESTAMP,
Incident_place VARCHAR2(30),
Time_lodged TIMESTAMP DEFAULT SYSDATE,
Date_lodged DATE NOT NULL,
Petitioner_id VARCHAR2(15),
Victim_Name VARCHAR2(50),
Victim_Address VARCHAR2(100),
Case_id NUMBER(10,0),
Petitioner_Name VARCHAR2(50),
CONSTRAINT FIR_PK PRIMARY KEY(FIR_id),
CONSTRAINT FIR_FK1 FOREIGN KEY(victim_name,victim_address)

REFERENCES Victim_T(name,address),
CONSTRAINT FIR_FK2 FOREIGN KEY(Petitioner_id,Petitioner_Name)

REFERENCES Petitioner_T(NIC,Name),
CONSTRAINT FIR_FK3 FOREIGN KEY(Case_ID) REFERENCES

Case_T(Case_ID)
);
• The attribute Incident_time is not specified NOT NULL because

mostly exact incident_time may not be known
• Time_lodged Is given system date as default value
Victim:
CREATE TABLE Victim_T (
Name VARCHAR2(50) NOT NULL,
Address VARCHAR2(100) NOT NULL,
Contact NUMBER(12,0),
CONSTRAINT Victim_PK PRIMARY KEY(Name,Address),
);
Accused:
CREATE TABLE Accused_T(
Accused_ID NUMBER(5,0) NOT NULL,
Name VARCHAR2(50),
Status VARCHAR2(8) CHECK(Status

IN('Arrested','Escaped','Bailed','Released')),
Age NUMBER(3,0) CHECK(Age<150),
Gender CHAR(1) CHECK(Gender IN('m','f')),
NIC VARCHAR2(15),
Email VARCHAR2(50) UNIQUE,
Photo BLOB,
Finger_Prints BLOB,
FIR_ID NUMBER(5,0),
CONSTRAINT Accused_PK PRIMARY KEY(Accused_ID),
CONSTRAINT Accused_FK FOREIGN KEY(FIR_ID ) REFERENCES

FIR_T(FIR_ID)
);
• There are only four possible status values for an accused

'Arrested','Escaped','Bailed','Released'
Hence this constraint is implemented here
• A constraint of less than 150 is also applied on the age column

• Gender will be stored as a character only ‘M’ for male and ‘F’ for
female
Investigation Officer:
CREATE TABLE Investigation_officer_T(
Officer_id VARCHAR2(15) NOT NULL,
Name VARCHAR2(50),
Rank VARCHAR2(5),
CONSTRAINT Investigation_officer_PK PRIMARY KEY(Officer_id)
);
Case:
CREATE TABLE Case_T(
Case_id NUMBER(10,0) NOT NULL,
Case_status CHAR(1) CHECK(Case_status IN('c','o')),
Case_Detail LONG,
Section_of_law VARCHAR2(6),
FIR_ID NUMBER(5,0),
Officer_id VARCHAR2(15),
CONSTRAINT Case_PK PRIMARY KEY(Case_id),
CONSTRAINT Case_FK1 FOREIGN KEY(Fir_id)REFERENCES FIR_T(FIR_id),
CONSTRAINT Case_FK2 FOREIGN KEY(Officer_id)REFERENCES

Investigation_officer_T(Officer_id)
);
• There are two possible values for case_status i.e. either a case is
open or close so only a single character is stored for case status ‘c’ for
closed and ‘o’ for open
Following three tables are created for multi-valued attributes of accused
Accused Address:
CREATE TABLE Accused_address_T(
Address VARCHAR2(100) NOT NULL,
CONSTRAINT Accused_address_PK PRIMARY KEY(Accused_ID,Address),
CONSTRAINT Accused_address_FK FOREIGN KEY(Accused_ID)

REFERENCES Accused_T(Accused_id)
);
Accused Alias:
CREATE TABLE Accused_alias_T(
Alias VARCHAR2(50) NOT NULL,
CONSTRAINT Accused_alias_PK PRIMARY KEY(Accused_ID,Alias),
CONSTRAINT Accused_alias_FK FOREIGN KEY(Accused_ID) REFERENCES

Accused_T(Accused_ID)
);
Accused Contact:
CREATE TABLE Accused_Contact_T(
Phone_No NUMBER(12,0) NOT NULL,
CONSTRAINT Accused_Contact_PK PRIMARY

KEY(Accused_ID,Phone_No),
CONSTRAINT Accused_Contact_FK FOREIGN KEY(Accused_ID)

REFERENCES Accused_T(Accused_ID)
);

Database For Criminal Record Management System

Uploaded by

Database For Criminal Record Management System

Uploaded by

CRMS

Criminal Record Management System

Muhammad Danish Naseem

Muhammad Jahanzeb Tariq

Along with low salary scale, facilities of modern technology such as

In our Project we are going to implement a CRMS (Criminal Record

CRMS will keep the record of following entities:

National identity card number of Petitioner.

Since NIC number is the only attribute of a Petitioner which is unique

The investigation officer has the following attributes

(i) The case is not serious in nature;

It is composed of following attributes

Accused and FIR

➢ FIR is lodged or filed against accused

FIR and Case

Investigation Officer and Case

(Entities and their relationships)

• Officer_ id is primary key

Officer_ ID Name Rank

Case_ Section_ of_ Case_Det

NIC Name Father_ name Address Contact

FIR_ID is the foreign key since accused has a one-to–many relationship

Name Address Father_ Contac

Case_ Case_ Section_ of_ Case_ FIR_I Officer_

NIC Name Father_ name Address Contact

Second Normal Form

• Officer_ID è Name , Rank

• This implies that there is no partial functional dependency in this

• The relation “Investigation_officer” is in 2nd Normal Form

Officer_ID Name Rank

• Case_ID è Case_status , Case_Description, Section_of_law

• No partial functional dependency

• “Case” is in 2nd Normal Form

• NIC +Nameè Name,Father_name,Address,Contact

• Only NIC cannot be determinant because fraud cases can cause

• No Partial functional dependency

• Relation “Petitioner” is in 2nd Normal Form

• No Partial functional dependency

• Relation “FIR” is in 2nd Normal Form

Complainant Date_lod Time_lod Incident_t Incident_P Incident_d FIR_I

• No Partial functional dependency

Nam Father_na Stat Ag Gend NI ema Phot Fingure_Pr Accused FIR_I

Above three relations Accused_Address, Accused_Alias, Accused_Contact are

Third Normal Form

In the relation “Accused” NIC seems to be the possible determinant for

NIC VARCHAR2(15) NOT NULL,

Name VARCHAR2(50) NOT NULL,

CONSTRAINT Petitioner_PK PRIMARY KEY(NIC,Name)

FIR_id NUMBER(5,0) NOT NULL,

Incident_date DATE NOT NULL,

Time_lodged TIMESTAMP DEFAULT SYSDATE,

Date_lodged DATE NOT NULL,

CONSTRAINT FIR_PK PRIMARY KEY(FIR_id),

CONSTRAINT FIR_FK1 FOREIGN KEY(victim_name,victim_address)

CONSTRAINT FIR_FK2 FOREIGN KEY(Petitioner_id,Petitioner_Name)

CONSTRAINT FIR_FK3 FOREIGN KEY(Case_ID) REFERENCES

• The attribute Incident_time is not specified NOT NULL because

Name VARCHAR2(50) NOT NULL,

Address VARCHAR2(100) NOT NULL,

CONSTRAINT Victim_PK PRIMARY KEY(Name,Address),

Accused_ID NUMBER(5,0) NOT NULL,

Status VARCHAR2(8) CHECK(Status

Age NUMBER(3,0) CHECK(Age<150),

Gender CHAR(1) CHECK(Gender IN('m','f')),

Email VARCHAR2(50) UNIQUE,

CONSTRAINT Accused_PK PRIMARY KEY(Accused_ID),

CONSTRAINT Accused_FK FOREIGN KEY(FIR_ID ) REFERENCES

• There are only four possible status values for an accused

Hence this constraint is implemented here

• A constraint of less than 150 is also applied on the age column

Officer_id VARCHAR2(15) NOT NULL,

CONSTRAINT Investigation_officer_PK PRIMARY KEY(Officer_id)

Case_id NUMBER(10,0) NOT NULL,

Case_status CHAR(1) CHECK(Case_status IN('c','o')),

CONSTRAINT Case_PK PRIMARY KEY(Case_id),

CONSTRAINT Case_FK1 FOREIGN KEY(Fir_id)REFERENCES FIR_T(FIR_id),