Professional Documents
Culture Documents
-1-
PROJECT REPORT FACE IDENTIFICATION
ABSTRACT
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 eyewitnesses. 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 fingerprint, eyes, DNA etc. One of the applications is face identification. The
face is our primary focus of attention in social inter course playing a major role in
conveying identity and emotion. Although the ability to infer intelligence or character
from facial appearance is suspect, the human ability to recognize faces is remarkable.
-2-
PROJECT REPORT FACE IDENTIFICATION
CONTENTS
-3-
PROJECT REPORT FACE IDENTIFICATION
FACE IDENTIFICATION
CONTENTS
Page nos.
*Acknowledgement
*Abstract
1. INTRODUCTION
1.1 Organization Profile
1.2 Face Identification
2. SYSTEM ANALYSIS
2.1 Existing System
2.2 Proposed System
2.3 Feasibility Study
3. MODULE DESCRIPTION
3.1 Add Image
3.2 Clip Image
3.3 Construct Image
3.4 Identification
4. SYSTEM REQUIREMENTS
4.1 Software Requirements
4.2 Hardware Requirements
5. LITERATURE SURVEY
6. SYSTEM DESIGN
5.1 Detailed Design
-4-
PROJECT REPORT FACE IDENTIFICATION
7. TESTING
8. IMPLEMENTATION
9. CONCLUSION
10. BIBLIOGRAPHY
INTRODUCTION
-5-
PROJECT REPORT FACE IDENTIFICATION
1.2.1 INTRODUCTION
-6-
PROJECT REPORT FACE IDENTIFICATION
is an image of f (x, y) that has been digitized both in spatial co-ordinate and
brightness. The elements of such a digital array are called image elements, picture
elements and pixels or pels.
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.
-7-
PROJECT REPORT FACE IDENTIFICATION
SYSTEM ANANLYSIS
-8-
PROJECT REPORT FACE IDENTIFICATION
EXISTING SYSTEM
The development of face identification has been past from the year to years. In recent
years to identify any criminal face they used to make a sketch or draw a image based
on the eyewitnesses. It used to take more amount of time and it was very difficult task
-9-
PROJECT REPORT FACE IDENTIFICATION
for any investigation department to easily catch the criminals within a stipulated time.
In order to catch the criminals first they used to search their record whether to find out
is there any record about that particular person in the past. In olden days each and
every record was maintained in the books or registers or files which used to contain
information about previous criminals with their names, alias name, gender, age, crime
involved, etc. Here each and every task used to take the help of the person because
they used to write in them and it needed very much of manual effort.
There are three major research groups, which propose three different approaches to
the face recognition problem. The largest group has dealt with facial characteristics.
The second group performs human face identification based on feature vectors
extracted from profile silhouettes. The third group uses feature vectors extracted from
a frontal view of the face. The first method is based on the information theory
concepts in other words on the principal component analysis methods. In this
approach, the most relevant information that best describes a face is derived from the
entire face image. The second method is based on extracting feature vectors from the
basic parts of a face such as eyes, nose, mouth and chin.
- 10 -
PROJECT REPORT FACE IDENTIFICATION
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.
Addition, Clipping, Construction and updating of the criminal record and face.
Comparing the image with the faces that are there in our database.
If any new images are found then it should be entered into our database by add
image module and then it should be segmented into different slices.
- 11 -
PROJECT REPORT FACE IDENTIFICATION
FEASIBILITY STUDY
Technical Feasibility
Economical Feasibility
Operational Feasibility
TECHNICAL FEASIBILITY
ECONOMICAL FEASIBILITY
OPERATIONAL FEASIBILITY
- 12 -
PROJECT REPORT FACE IDENTIFICATION
Without stifling competition and innovation among users, to the benefit of the public
both in terms of cost and service quality. The proposed system is acceptable to users.
So the proposed system is operationally feasible.
- 13 -
PROJECT REPORT FACE IDENTIFICATION
MODULE DESCRIPTION
MODULES
Add Image
Clip Image
Construct Image
Identification
A module is a small part of our project. This plays a very important role in the project
and in coding concepts. In Software Engineering concept we treat it has a small part
of a system but whereas in our programming language it is a small part of the
program, which we also called as function in, some cases which constitute the main
program.
- 14 -
PROJECT REPORT FACE IDENTIFICATION
3.4 IDENTIFICATION
This module contains the interface to take the image from above
module and it compares or searches with the images already there in the database.
If any image is matched then we identify him/her as the criminal else we add that
new image again to the database.
- 15 -
PROJECT REPORT FACE IDENTIFICATION
SYSTEM REQUIREMENTS
- 16 -
PROJECT REPORT FACE IDENTIFICATION
LITERATURE SURVEY
OVERVIEW OF JAVA
Java was conceived by James Gosling, Patrick Naughton, Chris Warth, Ed Frank and
Mike Sheridan at Sun Microsystems Inc.in 1991. It took 18 months to develop the
first working version. This language was initially called “Oak” but was renamed as
“Java” in 1995. Between the initial implementation of Oak in the fall of 1992 and the
public announcement of Java in the spring of 1995, many more people contributed to
the design and evolution of the language.
The main properties of the Java, which made Java so popular, are as follows:
1. Simple
2. Secure
3. Portable
4. Object-Oriented
5. Robust
6. Multithreaded
7. Architecture-Neutral
8. Interpreted
9. High performance
10.Distributed
11.Dynamic
- 17 -
PROJECT REPORT FACE IDENTIFICATION
The key that allows Java to solve both the security and the portability
problems just described is that the output of a Java compiler is not executable code.
Rather, it is Byte code. Byte code is a highly optimized set of instructions designed to
be executed by the Java runtime systems, which is called the Java Virtual Machine
(JVM). That is, in its standard form, the JVM is an interpreter for Byte code. This
may come has a bit of surprise.
Translating a Java program into a byte code helps and makes it much
easier to run a program in a wide variety of environments. The reason is
straightforward only the JVM needs to be implemented for each platform. Once the
runtime package exists for a given system, any Java program can run on it.
Remember, although the details of the JVM will differ from platform to platform, all
interpret the same Java Byte code.
JAVA ENVIRONMENT:
The Java development kit comes with a collection of tools that are used
for developing and running Java programs. They include:
- 18 -
PROJECT REPORT FACE IDENTIFICATION
AWT package: The abstract window toolkit package contains classes that
implements platform independent graphical user interface.
Applet package: This includes a set of classes that allows us to create Java
applets.
- 19 -
PROJECT REPORT FACE IDENTIFICATION
OVERVIEW OF SWINGS
Swings are basically used to create a GUI look i.e. graphical user
interface. A GUI presents a pictorial interface to a program. It allows the user to
spend less time trying to remember which keystroke sequence do what and spends
more time using the program in a productive manner.
The classes that are used to create the GUI components of swing are part
of javax.swing package. These are the latest GUI components of java2 platform.
Swing Components are written, manipulated and displayed completely in java.
- 20 -
PROJECT REPORT FACE IDENTIFICATION
The important topics that play a very vital role in swings are as follows:
JCheckBox & JRadioButton: The swing GUI component has three types of
state buttons- JToggleButtons, JCheckBox and JRadioButton that have on/off
or true/false values. A JRadioButton is different from a JCheckBox in the
there are several JRadioButton are grouped and only one of the JRadioButton
in the group can be selected at any time.
- 21 -
PROJECT REPORT FACE IDENTIFICATION
JList: A List display a selection of items from which the user may select one
or more items. JList support single-line selection List and multiple-selection
list.
- 22 -
PROJECT REPORT FACE IDENTIFICATION
the JDBC specification to most easily use ODBC in short-term, but they have
provided the capability long-term for JDBC to be implemented in other ways.
NOTE: JDBC, like ODBC, is designed to be a Call Level SQL Interface. Because
many of its many of its low-level operations can be combined into a higher level,
object oriented interface, except to see Java class libraries released in the future that
provide a mapping to the underlying JDBC Calls. This happened with ODBC almost
immediately, and the majority of ODBC developers currently use other Interface
rather than using ODBC API directly.
ESTABLISING A CONNECTION
- 23 -
PROJECT REPORT FACE IDENTIFICATION
1.Loading the driver: If, we want to use the JDBC-ODBC bridge driver, the
following code will load it :
Class.forName(“sun.jdbc.odbc.JdbcOdbcDriver”);
Our driver documentation will give us the class name to use. For instance, if the class
name is jdbc.Driverxyz, you would load the driver with the following line of code:
Class.forName(“jdbc.Driverxyz”);
Connection con;
Con=DriverManager.getConnection (url,”scott”,”tiger”);
This step is also simple with the hardest thing being what to supply for
URL. If you are using the JDBC-ODBC Bridge driver, the JDBC URL will start with
jdbc:odbc:. The rest of the URL is generally your data source name or database
system.
CREATING A STATEMENT
Syntax:
Java.sql.Statement st=connection.createStatement();
- 24 -
PROJECT REPORT FACE IDENTIFICATION
OVERVIEW OF ORACLE
DATABASE
DATA DICTIONARY
The DBA is the person responsible for the operation, configuration and
performance of the database. The DBA is charged with keeping the database
operating smoothly, ensuring that backups are done on regular basis (and that backups
work), and installing new software. Other responsibilities might include planning for
future expansion and disk space needs, creating databases and table spaces, adding
users and maintaining security, and monitoring the database and retuning it as
necessary. Large installations might have teams of DBA’s to keep the system running
smoothly; alternatively, the task might be segmented among the DBA’s.
ORACLE
- 25 -
PROJECT REPORT FACE IDENTIFICATION
Create Table Command: This is used to create a table in database specifying the
columns in it.
Insertion of values: This is used to insert values to the specified columns in the table.
Viewing Data from tables: This is used to view the content’s of the table created.
Syntax: select * from table_name;
Creating a table from existing table: This is used to create a table from existing
table by taking the columns needed.
Inserting data into a table from another table: This is used to insert rows from one
table into another table.
- 26 -
PROJECT REPORT FACE IDENTIFICATION
Delete operation: The verb DELETE in SQL is used to remove all rows from table,
or a selected set of rows from a table.
Syntax: delete from table_name where condition; (deletes specified rows based on
condition)
Updating the contents of a table: the update command is used to change or modify
data values in a table. To update all the rows from table OR a select set of rows from a
table.
Syntax: update table_name set column_name = expression; (updates all the rows)
Syntax: Alter table table_name modify (column_name new datatype (new size));
Destroying tables: This is used to delete any table from the database.
Finding out the tables created by user: To display all the tables which are there in
our database.
- 27 -
PROJECT REPORT FACE IDENTIFICATION
Finding out the columns details of a table created: To check which columns are
present and what is there datatype& size we use this command i.e. desc.
SYSTEM DESIGN
DETAILED DESIGN
UML DIAGRAMS
- 28 -
PROJECT REPORT FACE IDENTIFICATION
UML is the international standard notation for object-oriented analysis and design.
The Object Management Group defines it. The heart of object-oriented problem
solving is the construction of a model. The model abstracts the essential details of the
underlying problem from its usually complicated real world. Several modeling tools
are wrapped under the heading of the UML™, which stands for Unified Modeling
Language™.
AN OVERVIEW OF UML:
These are the artifacts of a software-intensive system. The three major elements of
UML are
- 29 -
PROJECT REPORT FACE IDENTIFICATION
Things
Relationships
Diagrams
They are the abstractions that are first-class citizens in a model. There are four kinds
of things in the UML
1. Structural things
2. Behavioral things.
3. Grouping things.
4. Annotational things.
These things are the basic object oriented building blocks of the UML. They are used
to write well-formed models.
STRUCTURAL THINGS:
Structural things are the nouns of the UML models. These are mostly static parts of
the model, representing elements that are either conceptual or physical. In all, there
are seven kinds of Structural things.
Class:
A class is a description of a set of objects that share the same attributes, operations,
relationships, and semantics. A class implements one or more interfaces. Graphically
a class is rendered as a rectangle, usually including its name, attributes and operations,
as shown below.
- 30 -
PROJECT REPORT FACE IDENTIFICATION
Interface:
ISpelling
Collaboration:
Collaboration defines an interaction and is a society of roles and other elements that
work together to provide some cooperative behavior that’s bigger than the sum of all
the elements. Graphically, collaboration is rendered as an ellipse with dashed lines,
usually including only its name as shown below.
Chain of
Responsibility
- 31 -
PROJECT REPORT FACE IDENTIFICATION
Chain
Use Case:
Use case is a description of a set of sequence of actions that a system performs that
yields an observable result of value to a particular thing in a model. Graphically, Use
Case is rendered as an ellipse with dashed lines, usually including only its name as
shown below.
Place Order
Active Class:
An active class is a class whose objects own one or more processes or threads and
therefore can initiate control activity. Graphically, an active class is rendered just like
a class, but with heavy lines usually including its name, attributes and operations as
shown below.
Face
Identificatio
n
Image
Suspend ()
- 32 -
PROJECT REPORT FACE IDENTIFICATION
Component:
orderform.java
Node:
A Node is a physical element that exists at run time and represents a computational
resource, generally having at least some memory and often, processing capability.
Graphically, a node is rendered as a cube, usually including only its name, as shown
below.
server
BEHAVIORAL THINGS:
Behavioural Things are the dynamic parts of UML models. These are the verbs of a
model, representing behaviour over time and space.
Interaction:
- 33 -
PROJECT REPORT FACE IDENTIFICATION
Display
State Machine:
A state machine is a behavior that specifies the sequence of states an object are an
interaction goes through during its lifetime on response to events, together with its
responses to those events. Graphically, a state is rendered as a rounded rectangle
usually including its name and its sub-states, if any, as shown below.
Waiting
GROUPING THINGS:
Grouping things are the organizational parts of the UML models. These are the boxes
into which a model can be decomposed.
Package:
Business Rules
- 34 -
PROJECT REPORT FACE IDENTIFICATION
ANNOTATIONAL THINGS:
- 35 -
PROJECT REPORT FACE IDENTIFICATION
instance of one class must know about the other in order to perform its work. In a
diagram, an association is a link connecting two classes. Graphically it is
represented by line as shown.
4. Realization:
DIAGRAMS IN UML:
Diagrams play a very important role in the UML. There are nine kind of modeling
diagrams as follows:
- 36 -
PROJECT REPORT FACE IDENTIFICATION
Object Diagram
Sequence Diagram
Collaboration Diagram
State Chart Diagram
Activity Diagram
Component Diagram
Deployment Diagram
CLASS DIAGRAM:
Class diagrams are the most common diagrams found in modeling object-oriented
systems. A class diagram shows a set of classes, interfaces, and collaborations and
their relationships. Graphically, a class diagram is a collection of vertices and arcs.
Contents:
Class Diagrams commonly contain the following things:
Classes
Interfaces
Collaborations
Dependency, generalization and association relationships
Use Case diagrams are one of the five diagrams in the UML for modeling the
dynamic aspects of systems(activity diagrams, sequence diagrams, state chart
diagrams and collaboration diagrams are the four other kinds of diagrams in the UML
for modeling the dynamic aspects of systems). Use Case diagrams are central to
modeling the behavior of the system, a sub-system, or a class. Each one shows a set of
use cases and actors and relationships.
Common Properties:
A Use Case diagram is just a special kind of diagram and shares the same common
properties, as do all other diagrams- a name and graphical contents that are a
- 37 -
PROJECT REPORT FACE IDENTIFICATION
projection into the model. What distinguishes a use case diagram from all other kinds
of diagrams is its particular content.
Contents
Use Case diagrams commonly contain:
Use Cases
Actors
Dependency, generalization, and association relationships
Like all other diagrams, use case diagrams may contain notes and constraints. Use
Case diagrams may also contain packages, which are used to group elements of your
model into larger chunks. Occasionally, you will want to place instances of use cases
in your diagrams, as well, especially when you want to visualize a specific executing
system.
INTERACTION DIAGRAMS
Contents
Interaction diagrams commonly contains:
Objects
Links
Messages
- 38 -
PROJECT REPORT FACE IDENTIFICATION
Like all other diagrams, interaction diagrams may contain notes and constraints.
SEQUENCE DIAGRAMS:
1. There is the object lifeline. An object lifeline is the vertical dashed line that
represents the existence of an object over a period of time. Most objects that
appear in the interaction diagrams will be in existence for the duration of the
interaction, so these objects are all aligned at the top of the
diagram, with their lifelines drawn from the top of the diagram to the bottom.
2. There is a focus of the control. The focus of control is tall, thin rectangle that
shows the period of time during which an object is performing an action,
either directly or through the subordinate procedure. The top of the rectangle
is aligns with the action; the bottom is aligned with its completion.
Contents
Sequence diagrams commonly contains
Objects
Object Life Line
Focus Of Control
- 39 -
PROJECT REPORT FACE IDENTIFICATION
ACTIVITY DIAGRAM
An Activity Diagram is essentially a flow chart showing flow of control from activity
to activity. They are used to model the dynamic aspects of as system. They can also
be used to model the flow of an object as it moves from state to state at different
points in the flow of control.
Contents
Activity diagrams commonly contain:
Fork
Start & End Symbol
A state chart diagram shows a state machine. State chart diagrams are used to model
the dynamic aspects of the system. For the most part this involves modeling the
behavior of the reactive objects. A reactive object is one whose behavior is best
characterized by its response to events dispatched from outside its context. A reactive
object has a clear lifeline whose current behavior is affected by its past.
A state chart diagram show a state machine emphasizing the flow of control from
state to state. A state machine is a behavior that specifies the sequence of states an
object goes through during its lifetime in response to events together with its
response to those events. A state is a condition in the life of the object during which it
satisfies some conditions, performs some activity or wait for some events. An event is
a specification of a significant occurrence that has a location in time and space.
- 40 -
PROJECT REPORT FACE IDENTIFICATION
Contents:
State chart diagram commonly contain:
Simple states and Composite states.
Transitions, events and actions.
CLASS DIAGRAM
- 41 -
PROJECT REPORT FACE IDENTIFICATION
OBJECT DIAGRAM
- 42 -
PROJECT REPORT FACE IDENTIFICATION
- 43 -
PROJECT REPORT FACE IDENTIFICATION
SEQUENCE DIAGRAM
- 44 -
PROJECT REPORT FACE IDENTIFICATION
COLLABORATION DIAGRAM
- 45 -
PROJECT REPORT FACE IDENTIFICATION
ADD MODULE
UPDATE DETAILS:
- 46 -
PROJECT REPORT FACE IDENTIFICATION
CONSTRUCT MODULE
SHOW DETAILS:
- 47 -
PROJECT REPORT FACE IDENTIFICATION
ACTIVITY DIAGRAM
- 48 -
PROJECT REPORT FACE IDENTIFICATION
Login
Authentication
Valid User
Invalid User
Main Screen
Choose Option
Add Image Clip Image Update Details Construct Image Search Process
End
COMPONENT DIAGRAM
- 49 -
PROJECT REPORT FACE IDENTIFICATION
DATABASE DESIGN
- 50 -
PROJECT REPORT FACE IDENTIFICATION
DATA FLOW
DIAGRAMS
A graphical tool used to describe and analyze the moment of data through a system
manual or automated including the process, stores of data, and delays in the system.
Data Flow Diagrams are the central tool and the basis from which other components
are developed. The transformation of data from input to output, through processes,
may be described logically and independently of the physical components associated
with the system. The DFD is also know as a data flow graph or a bubble chart.
CONTEXT DIAGRAM:
- 51 -
PROJECT REPORT FACE IDENTIFICATION
single bubble with input and output data indicated by incoming and outgoing arrows
respectively.
1. PHYSICAL DFD:
Structured analysis states that the current system should be first understand
correctly. The physical DFD is the model of the current system and is used to
ensure that the current system has been clearly understood. Physical DFDs shows
actual devices, departments, and people etc., involved in the current system
2. LOGICAL DFD:
Logical DFDs are the model of the proposed system. They clearly should
show the requirements on which the new system should be built. Later during
design activity this is taken as the basis for drawing the system’s structure charts.
BASIC NOTATION:
- 52 -
PROJECT REPORT FACE IDENTIFICATION
DESIGN:
Design is the first step in moving from problem domain to the solution domain.
Design is essentially the bridge between requirements specification and the final
solution.
- 53 -
PROJECT REPORT FACE IDENTIFICATION
Start
Login
Authentication
Valid User
Invalid User
- 54 -
Main Screen
PROJECT REPORT FACE IDENTIFICATION
Add Image Clip Image Update Details Construct Image Search Process
Add to Database
Add Clips to DatabaseAdd to database Search Image
Result
End
EYE WITNESS
OPERATOR CRIMINAL
- 55 -
FACE
PROJECT REPORT FACE IDENTIFICATION
Description: Context Flow Diagram gives us the complete details about the inputs
and outputs for a given system. In the above system the main task is to identify a
criminal face. So, the operator and eyewitness are the inputs to our system and
criminal face is desired output.
LOGIN PROCESS
User Id PROCESS
LOGIN SCREEN
Password
ERROR IN
INPUT
Level-1
Description: The inputs to the process are User Id and Password given by the
developer to allow the software available for the user environment. After giving the
- 56 -
PROJECT REPORT FACE IDENTIFICATION
inputs the code checks whether the entered ones are valid are not. It displays screen if
match occurs otherwise error message if they are not matched.
MAIN SCREEN
OPERATOR ADD IMAGE
SEARCH
IMAGE
CLIP IMAGE
CONSTRUCT
IMAGE
Level -2
Description: This process mainly explains the different screens that are available for
the operator. Here the selection of the screen depends on the operator and he can
select whatever screen he wants. The different screens that are available are Add
Image, Show or Search Image, Clip Image and Construct Image.
- 57 -
PROJECT REPORT FACE IDENTIFICATION
DATABASE
ADD PROCESS
OPERATOR DATA IS
ADDED
ERROR
Level-3
Description: This process clearly illustrates adding the details of the criminal such as
name, alias name, age, gender, location, address, state and city along with his photo.
These details are being added to the database, if any error is generated then it will be
prompted to the operator otherwise we get message data is successfully added.
CLIPPING PROCESS
- 58 -
PROJECT REPORT FACE IDENTIFICATION
DATABASE
DATABASE
EYES
NOSE
FACE
FACE
HAIR
FOREHEAD
Level-4
Description: This is used for clipping the image into different slices say eyes,
forehead, lips, hair and nose. The input for this is face which is divided into some
slices which are stored in the database. Even though the image is divided into slices,
the original image remains as it is.
UPDATE PROCESS
- 59 -
PROJECT REPORT FACE IDENTIFICATION
DATABASE
UPDATE PROCESS
DATA
OPERATOR
UPDATED
Level-5
Description: Update process is mainly used for updating or modifying the details of
the criminal or person. This is used in situation where we have entered the details
incorrectly or we want to add some new details.
CONSTRUCT IMAGE
DATABASE
HAIR
- 60 -
FOREHEAD
EYES
NOSE
LIPS
INSTRUCTION FACE
Level-6
Description: Based on the instruction given by the eyewitnesses, the operator brings
the clips of the images from the database and then goes for the construction of the
image based on those clips.
COMPARISON PROCESS
DATABASE
COMPARISON
PROCESS RESULT
FACE
- 61 -
PROJECT REPORT FACE IDENTIFICATION
Level-7
Description: The face that is constructed in the above process is sent to the
comparison process where it searches the image in the database.
E-R DIAGRAMS
- 62 -
PROJECT REPORT FACE IDENTIFICATION
The E-R model forms the basis of E-R diagram that represent
the conceptual database as viewed by the end user. These diagrams depict the E-R
model three main Components:
Entities
Attributes
Relationships.
1. ENTITIES
An entity at the E-R modeling level actually refers to the
entity set not to a single entity occurance. In other words the word “entity” in the E-R
model corresponds to a table and not to a row in the relational environment. The E-R
model refers to a specific table row as an entity instance or entity occurrence. An
entity is represented by a rectangle containing the entity occurrence. An entity is
represented by a rectangle containing the entities name.
- 63 -
PROJECT REPORT FACE IDENTIFICATION
2. ATTRIBUTES
3. RELATIONSHIP
- 64 -
PROJECT REPORT FACE IDENTIFICATION
Forehead
Cid fnamee Hairs Nose
age Crime
Involved
Chin
Conn-ected
by
FACE Face_heights
- 65 -
PROJECT REPORT FACE IDENTIFICATION
changes in birth date would automatically reflect in all tables that link to that
birth date
DATABASE TABLES
DATABASE TABLES
FACE
- 66 -
PROJECT REPORT FACE IDENTIFICATION
CRIMINAL_SUSPECT TABLE
FACE_HEIGHTS TABLE
FACE_SUSPECTPHOTO
- 67 -
PROJECT REPORT FACE IDENTIFICATION
SCREENS
- 68 -
PROJECT REPORT FACE IDENTIFICATION
LOGIN SCREEN
MAIN SCREEN
- 69 -
PROJECT REPORT FACE IDENTIFICATION
- 70 -
PROJECT REPORT FACE IDENTIFICATION
- 71 -
PROJECT REPORT FACE IDENTIFICATION
- 72 -
PROJECT REPORT FACE IDENTIFICATION
- 73 -
PROJECT REPORT FACE IDENTIFICATION
- 74 -
PROJECT REPORT FACE IDENTIFICATION
SHOW DETAILS
- 75 -
PROJECT REPORT FACE IDENTIFICATION
- 76 -
PROJECT REPORT FACE IDENTIFICATION
- 77 -
PROJECT REPORT FACE IDENTIFICATION
CONSTRUCT SCREEN
- 78 -
PROJECT REPORT FACE IDENTIFICATION
- 79 -
PROJECT REPORT FACE IDENTIFICATION
FIND FACE
- 80 -
PROJECT REPORT FACE IDENTIFICATION
- 81 -
PROJECT REPORT FACE IDENTIFICATION
- 82 -
PROJECT REPORT FACE IDENTIFICATION
HELP SCREEN
- 83 -
PROJECT REPORT FACE IDENTIFICATION
- 84 -
PROJECT REPORT FACE IDENTIFICATION
TESTING
TESTING PHASE
- 85 -
PROJECT REPORT FACE IDENTIFICATION
The testing phase involves the testing of the developed system using
various kinds of data. An elaborated testing of data is prepared and a system is tested
using the test data. While testing, errors are noted and corrections remade, the
corrections are also noted for future use.
SYSTEM TESTING
UNIT TESTING
During the implementation of the system each module of the system was
tested separately to uncover errors with in its boundaries. User interface was used as a
guide in the process.
MODULE TESTING
- 86 -
PROJECT REPORT FACE IDENTIFICATION
INTEGRATION TESTING
ACCEPTANCE TESTING
The software has been tested with the realistic data given by the client and
produced fruitful results. The client
satisfying all the requirements specified by them has also developed the software
within the time limitation specified. A demonstration has been given to the client and
the end-user giving all the operational features.
- 87 -
PROJECT REPORT FACE IDENTIFICATION
Unit Testing
- 88 -
PROJECT REPORT FACE IDENTIFICATION
IMPLEMENTATION
- 89 -
PROJECT REPORT FACE IDENTIFICATION
IMPLEMENTATION PHASE
- 90 -
PROJECT REPORT FACE IDENTIFICATION
CONCLUSION
CONCLUSION
- 91 -
PROJECT REPORT FACE IDENTIFICATION
- 92 -
PROJECT REPORT FACE IDENTIFICATION
BIBLIOGRAPHY
BIBLIOGRAPHY
BOOKS REFERRED
The following books were used extensively for the project development and
implementation.
- 93 -
PROJECT REPORT FACE IDENTIFICATION
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/
- 94 -