CRIMINAL FACE IDENTIFICATION SYSTEM

PROJECT-I REPORT

Submitted in partial fulfillment for the award of the degree of

BACHELOR OF COMPUTER SCIENCE AND ENGINEERING

Submitted by

REG NO NAME

1811103 AJITHKANNAN A

1811119 JEEVANANDHAM A

1811123 KOGUL DURGESH M

1811155 VEERAMANIKANDAN M

Under the guidance of

Mrs. ANNE CHRIS EVERT M.E.,

Assistant Professor,
Department of Computer Science and Engineering

GOVERNMENT COLLEGE OF ENGINEERING

(AUTONOMOUS)

BARGUR, KRISHNAGIRI - 635 104

DECEMBER - 2020
 GOVERNMENT COLLEGE OF ENGINEERING
(AUTONOMOUS)

BARGUR, KRISHNAGIRI -635 104

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

BONAFIDE CERTIFICATE

Certified that this project titled “CRIMINAL FACE IDENTIFICATION

SYSTEM” is the bonafide work of Ajithkannan A(1811103), Jeevanandham
A(1811119), Kogul Durgesh M(1811123), Veeramanikandan M(1811155) who carried
out the project work under my supervision.

Mrs. ANNE CHRIS EVERT M.E., Dr. J. NAFEESA BEGUM, M.E., Ph.D.,
SUPERVISOR HEAD OF THE DEPARTMENT
Assistant Professor Professor [CAS]
Department of CSE Department of CSE
Govt. College of Engineering Govt. College of Engineering
Bargur-635 104 Bargur-635 104

Submitted for the Thesis Viva voce Examination held on ______________

INTERNAL EXAMINER EXTERNAL EXAMINER

 CONTENTS

CHAPTER
TITLE PAGE NO.
NO.
Acknowledgement i

Abstract ii

List of tables iii

1. Introduction 1

2. Problem Description 3

3. System Analysis 4

4. System Requirements 5

5. System Design 6

6. System Implementation 14

7. Result and discussion 18

8. Conclusion and Future work 34

References 35
 i. ACKNOWLEDGEMENT

First and Foremost, praises and thanks to the God, the Almighty for showers of
blessings throughout our beautiful life journey. We are extremely grateful to our parents
for their love, prayers, caring and sacrifices for educating and preparing us for our future.

We express our sincere gratitude thanks to our respected Principal-in-Charge

Dr. NISHAT KANVEL, M.E., Ph.D., and our respected Head of the Department of
Computer Science and Engineering Dr. J.NAFEESA BEGUM, M.E., Ph.D., for giving
us the opportunity to display our professional skills through this project.

We are again greatly thankful to our project guide Mr. J. MANIMARAN, M.E.,
MBA., Department of Computer Science and Engineering for his valuable guidance and
motivation which helped us to complete this project on time.

We thank all our teaching and non-teaching staff members of the Computer
Science and Engineering for their passionate support for helping us to identify our
mistakes and also for the appreciation they gave us in achieving our goal.

Also, we would like to record our deepest gratitude to our parents for their
constant encouragement and support which motivated us to complete our project on
time.

AJITHKANNAN A (1811103)

JEEVANANDHAM A (1811119)

KOGUL DURGESH M (1811123)

VEERAMANIKANDAN M (1811155)
 ii. ABSTRACT

Criminal record generally contains personal information about particular

person along with photograph. To identify any Criminal we need some identification

regarding person, which are given by eyewitness. In most cases the quality and resolution

of the recorded image segments is poor and hard to identify a face. To overcome this sort

of problem we are developing software. Identification can be done in many ways like

finger print, eyes, DNA etc. One of the applications is face identification. The face is our

primary focus of attention in social inters course playing a major role in conveying

identify and emotion. Although the ability to infer intelligence or character from facial

appearance is suspect, the human ability to recognize face is remarkable.

 iii. LIST OF TABLES

DATABASE TABLES

FACE
Field Name Data Type Size

Criminal Id Number 5 (Primary Key)

First Name Varchar2 15

Last Name Varchar2 15

Alias Name Varchar2 15

D.O.B Date

Age Number 5

Gender Varchar2 15

Address Varchar2 15

City Varchar2 15

State Varchar2 15

Arrested Date Date

Crime Involved In Varchar2 15

Photo Varchar2 15
CRIMINAL_SUSPECT TABLE

Field Name Data Type Size

Criminal Id Number 5 (Primary Key)

Cid Number 5

FACE_HEIGHTS TABLE

Field Name Data Type Size

Criminal Id Number 5

Hair Number 5

Forehead Number 5

Eyes Number 5

Nose Number 5

Lips Number 5

Chin Number 5

FACE_SUSPECTPHOTO

Field Name Data Type Size

Cid Number 5

Suspect Photo Varchar2 15

Suspect Height Varchar2 15

 1. INTRODUCTION
PURPOSE OF THE PROJECT:

This project is aimed to identify the criminals in any investigation department. Here
the technique is we already store some images of the criminals in our database along with
his details and that images are segmented into many slices say eyes, hairs, lips, nose, etc.
These images are again stored in another database record so to identify any criminals;
eyewitnesses will see the images or slices that appear on the screen by using it we
develop the face, which may or may not be matched with our images. If any image is
matched up to 99% then we predict that he is only the criminal. Thus using this project it
provides a very friendly environment for both operator and eyewitness to easily design
any face can identify criminals very easy.

PROJECT OBJECTIVE:

This project is intended to identify a person using the images previously taken. The
identification will be done according the previous images of different persons.

PROJECT SCOPE:

The scope of the project is confined to store the image and store in the database.
When a person has to be identified the images stored in the database are compared with
the existing details.
OVERVIEW OF THE PROJECT:

This project is aimed to identify the criminals in any investigation department.

Here the technique is we already store some images of the criminals in our database
along with his details and those images are segmented into many slices say eyes, hairs,
lips, nose, etc. These images are again stored in another database record so to identify any
criminals; eyewitnesses will see the images or slices that appear on the screen by using it
we develop the face, which may or may not be matched with our images. If any image is
matched up to 99% then we predict that he is only the criminal. Thus using this project it
provides a very friendly environment for both operator and eyewitness to easily design
any face can identify criminals very easy.
 2. PROBLEM DESCRIPTION
The project is aimed at identifying the criminals with the help of eye witness.
There are mainly four modules in our project. They are Adding, Deleting, Updating and
identifying the criminals. There are mainly three roles in our project. They are:
➢ Administrator
➢ Operator
➢ Eyewitness
The administrator is responsible for providing User id’s new image from those
cropped parts which we consider as an imaginary face of the criminal and passwords. He
provides authentication to the users. He creates deletes and Updates the User ids and
Passwords.
The operator, who belongs to the investigating department, is responsible for
entering the criminal details and maintains them. He adds, deletes and updates the
criminal details. He also constructs the criminal face with the help of eye witness.
The eyewitness identifies the criminals with the help of cropped parts stored
in a different database by the operator. The eyewitness selects a cropped part from the
database and that cropped part will be freeze by the operator in this way, complete face
of the criminal is constructed and the details of that criminal is retrieved from the
database. We can also construct a new image from those cropped parts which we
consider as an imaginary face of the criminal.
 3. SYSTEM ANALYSIS

a. EXISTING SYSTEM:
This system is manual system only. Here, have a facility to store the
criminal images. If you want to compare the criminal images with the existing
images it is manual process. This process is very slow to give the result. It is very
critical to find the criminal images.

DRAWBACKS IN EXISTING SYSTEM:

❖ Need of extra manual effort.

❖ It used to take much time to find any criminals
❖ Not very much accurate.
❖ Danger of losing the files in some cases.
❖ Need Good Knowledge in drawing.

b. PROPOSED SYSTEM:
To overcome the drawbacks that were in the existing system we develop a
system that will be very useful for any investigation department. Here the program
keeps track of the record number of each slice during the construction of
identifiable human face and calculate maximum number of slices of the similar
record number. Based on this record number the program retrieves the personal
record of the suspect (whose slice constituted the major parts of the constructed
human face) on exercising the “locate” option.

Advantages:

❖ Very fast and accurate.

❖ No need of any extra manual effort.
❖ No fever of data loss.
❖ Just need a little knowledge to operate the system.
 4. SYSTEM REQUIREMENTS

SOFTWARE REQUIREMENTS:
Operating System : Windows 2000
Database Server : Oracle 9i

Programming Language : Java

Frame Work : Swing

HARDWARE REQUIREMENTS:
Processor : Pentium IV

Clock Speed : 2.86GHZ Processor

Hard disk : 2GB

RAM : 256MB
 5. SYSTEM DESIGN

b. E-R DIAGRAMS

E-RDIAGRAMS BETWEEN ADMINISTRATOR AND EMPLOYEE:

User Pwd

id User id Pwd

Authentication
Administrator Employee

E-R DIAGRAMS BETWEEN EMPLOYEE AND EYEWITNESS:

Criminal
User id Pwd
images Pwd
User

id

Viewing &
Employee Eyewitness
selecting,

images

Criminal Criminal

details images
E-R DIAGRAM BETWEEN EYEWITNESS AND CRIMINAL:

Criminal
Criminal Criminal id
details
images

Criminal
Eyewitness Identification

E-R DIAGRAM BETWEEN EMPLOYEE AND CRIMINAL:

Criminal Id Criminal
Pwd
User details

id

Getting
Employee Criminal
details

of

criminal
E-R DIAGRAM BETWEEN EYEWITNESS AND ADMINISTTRATOR

User Pwd
User Pw
id
id d

Authentication
Administrator Eyewitness

c. DATAFLOW DIAGRAMS
LEVEL 1
 LEVEL 2

DFD FOR Client:

 LEVEL-2

DFD FOR Split & Merge:

LEVEL 1:
LEVEL 2:
 d. UML DIAGRAMS

Use case Diagram:

Administrator:

Login

Inserting/Updating Criminal Details

Already Existed Criminal

criminal
Splitting/Updating Images
Administrator

New Criminal

Inserting/Updating Face Details

Deleting Images
Client (Operator):

operator Login

retriving the images

operator Criminal
identifying the images
 6. SYSTEM IMPLEMENTATION

The testing phase involves the testing of development system using various data.
Preparation of the test data plays a vital role in system testing. After preparing the test
data, the system under study was tested using those data. While testing the system, by
using the test data, errors were found and corrected by using the following testing steps
and corrections were also noted for future use. Thus, a series of testing is performed on
the proposed system before the system is ready for implementation.

The various types of testing done on the system are:

▪ Integration testing
▪ Validation testing
▪ Unit testing
▪ Output testing
▪ User Acceptance testing
Unit testing:

Unit testing focuses on verification effort on the smallest unit of software design
module. Using the unit test plans prepared in the design phase of the system development
as a guide, important control paths are tested to uncover errors with in the boundary of
the modules. The interfaces of the modules are tested to ensure proper flow of
information into and out of the modules under consideration boundary conditions were
checked. All independent paths were exercised to ensure that all statements in the module
have been executed at least once and all error-handling paths were tested.

Each unit is thoroughly tested to check if it might fail in any possible

situation. This testing is carried during the programming state itself. At the end of this
testing phase each module is found to be have an adverse effect working satisfactorily, as
regard to the expected output from the module.
Integration Testing:

Data can be lost across an interface, one module can on another; sub-
functions when combined may not produce the desired major function: global data
structures can present problems. Integration testing is a systematic technique for the
program structure while at the same time concluding tests to uncover errors associated
with interface. All modules are combined in this testing step. Then the entire program is
tested as a whole. Each of the module is integrated and tested separately and later all
modules are tested together for sometime to ensure the system as a whole works well
without any errors.

Validation Testing:

At the culmination of the integration testing, the software is completely assembled

as a package, interfacing errors have been uncovered and corrected, and a final series of
software validation testing began. Here we test if the system functions in a manner that
can be reasonably expected by the customer. The system is tested against the system
requirement specification.

Output Testing:

After performing validation testing, the next phase is output testing of the proposed
system, since no system can be useful if it does not produce the desired output in the
specified format. The output generated or displayed by the system under consideration is
tested by asking the user about the format required by them, here, the output format is
considered in two ways: One is on the screen and the other is on the printed form. Beta
testing is carried output by the client, and minor errors that have been discovered by the
client are rectified to improve the user friendliness of the system.

Object-Oriented Testing

The overall objectives of the object-oriented testing – to find the maximum number
of errors with a minimum amount effort – is identical to the to the objective of
conventional software testing. But the strategy and tactics for OO testing differ
significantly. The view of testing broadens to include the review of both the analysis and
design model. In addition, the focus of testing moves away from the procedural
component and toward the class.

Because the OO analysis and design models and the resulting source code are
semantically coupled, testing begins during these engineering activities. For this reason, a
review of CRC, object relationships, and object behavior models can be viewed as first
stage testing. As a result of this first stage testing, we encountered few problems in OOA
done at analysis time. We have gone back and remodeled with new errorless classes and
their relationships. The documented model is the revised model of earlier analysis model.

Once OOP has been accomplished, unit testing is applied for each class. Class
testing uses a variety of methods: fault-based, random, and partition test methods. Each
of those methods exercises the operations encapsulated by the class. Test sequences are
designed to ensure that relevant operations are exercised. The state of the class,
represented by the values of its attributes, is examined to determine if errors exist.

Integration test can be accomplished using a thread-based or use-based strategy.

Thread-based strategy integrates the set of classes that collaborate to respond to one input
or event. Use-based testing constructs the system in layers, beginning with those classes
that do not make use of server classes. Integration test case design methods can also make
use of random and partition tests. In addition, scenario based testing and the tests derived
from behavioral models can be used to test a class and its collaborators. A test sequence
tracks the flow of operations across class collaborations.

OO system validation testing is black box oriented and can be accomplished by

applying the same black box methods known for conventional software. However
scenario based testing dominates the validation of OO systems, making the use case a
primarily driver for validation testing.
 We mainly concentrated on scenario based testing strategy. Some of the test cases
for scenario based testing are given below.

Test case #1
Use Case: download a file

Background: User wants to download a file from Criminal Face

Identification System

Event Sequence:

1. Select file to down load in remote tree panel.

2. Right click and then click download.

Test case #2
Use Case : upload a file

Background : User wants to upload a file to the server from client.

Event Sequence:

1. Click file in local file view tree.

2. Right click and select upload.
 7. RESULT AND DISCUSSION

OUTPUT SCREENS

LOGIN SCREEN
MAIN SCREEN
NEW CRIMINAL FORM
SHOW DETAILS
CLIP IMAGE SCREEN
UPDATE DETAILS SCREEN
CONSTRUCT SCREEN
FIND FACE
HELP SCREEN
 8. CONCLUSION AND FUTURE WORK

The purpose of face identification system is to identify criminals. In past

years this process is carried out by humans. This process gives the exact image of the

criminal but it is very difficult to identify the criminal details and also it requires much

amount of human burden.

The main aim of our project is to overcome the drawbacks of human

based system by using the machine based face identification process. In this process

we store the details of criminal into the database along with his photo or

image. Then we make the image into different clips containing hair, forehead, eyes,

nose, lips and chin and store these clips into the database. When any crime occurs

we compare the details given by the eyewitness with the clips already stored in the

database and we will identify the criminal. This project can be extended to adjust the

gaps between the clips after construction of the image to be a perfect photograph using

Image processing Techniques.

 REFERENCES

BOOKS REFERRED

The following books were used extensively for the project development and

implementation.

1.”The Complete Reference Java2” Tata McGraw-Hill publishing Company Limited. By

Herbert Schildt.

2. “Software Engineering, A Practitioner’s Approach” Tata McGraw-Hill Publishing

Company Limited. By Roger S. Pressman.

3. “PL/SQL”. By Ivan Bayross.

WEBSITES REFERRED

The following links were searched and exploited extensively for the project development

and implementation.

1. http://www.java.sun.com/products\java

2. http://www.jakarta.apache.org

3. http://www.javaworld.com/

4. http://www.java2s.com/