Face Detection 1
Face Detection 1
Submitted to
Study Center:
Subhash Academy
(College of IT and Management)
E-mail: [email protected]
Sc Code:9050
Date-:
Candidate-: GAURAV KUMAR
INDEX
1. Abstract
2. Introduction
3. System Analysis
a) Existing System
b) Proposed System
4. Feasibility Report
a) Technical Feasibility
b) Operational Feasibility
c) Economical Feasibility
a) Modules Description
b) Process Flow
c) SDLC Methodology
d) Software Requirement
e) Hardware Requirement
6. System Design
a) E-R Diagram
b) DFD
c) UML
7. Technology Description
8. Coding
11.Future Enhancements
12. Bibliography
Abstract:
Title:
Objective:
be done in many ways like finger print, eyes, DNA etc. One of the
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 identifie
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 sllces say
eyes, halrs, Ilps, nose, etc. These Images are again
s t o r e d in another database record so to Identify any
crlmlnals; eyewltnesses wlll see tile images or slices that
appear on the screen by uslng 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.
PROBLEM AREA DESCRIPTION
The project is aimed at identify¡ng 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
SYSTEM ANALYSIS
The first step in developing anything is to state the
requirements. This applies just as much to leading edge researcla
as to -imple programs and to personal programs, as well as to
large team efforts. Being vague about your objective only
postpones decisions to a later stage where changes are much
more costly.
The problem statement should state what is to be done
and not how it is to be done. It should be a statement of
needs, not a proposal for a solution. A user manual for the
desired system is a good problem statement. The requestor
should indicate which features are mandatory and which are
optional, to avoid overly constraining design decisions. The
requestor should avoid describing system internals, as this
restricts implementation flexibility. Performance specifications
and protocols for interaction with externa I systems are
legitimate requirements. Software engineering standards, such
as modular construction, design for testability, and provision for
future extensions, are also proper.