Face detection and finger print project documentation

Human Face and Fingerprint Recognition and Verification System

PART I: REQUIREMENT ANALYSIS DOCUMENT (RAD)

CHAPTER ONE

1. Introduction

As the necessity for higher levels of security rises, technology is bound to swell to fulfill these needs. Any new creation, enterprise, or development should be uncomplicated and acceptable for end users in order to spread worldwide. This strong demand for user-friendly systems which can secure our assets and protect our privacy without losing our identity in a sea of numbers, grabbed the attention and studies of scientists toward what’s called biometrics.

Biometrics is the emerging area of bioengineering; it is the automated method of recognizing person based on a physiology. There exist several biometric systems such as finger prints, voice, iris, retina, hand geometry, ear geometry, and face. Among these systems, face and fingerprint recognition appears to be the most universal, collectable, and accessible systems.

Biometric face and fingerprint recognition are particularly attractive biometric approaches, since both focuses on the same identifier that humans use primarily to distinguish one person from another: their “faces” and fingerprint is also around in criminal investigation since late 19 th

century. One of the main goals of this system is to understand the complex human visual system as well as to use the knowledge of distinguishing one persons fingerprint from other’s and how humans represent faces in order to discriminate different identities with high accuracy with the use of the two most universally accepted biometric mechanisms.

The face and fingerprint recognition problem can be divided into two main stages: face and fingerprint detection (verification), and authentication based on the face and fingerprint detected and verified.

1. The detection stage is the first stage; it includes locating a face and fingerprint as an image file and verifying by cross matching.

2. The authentication stage is the second stage; in which authentication will take place.

The system will be developed with JAVA which makes it portable and platform independent. There will be three systems namely Desktop application, web application, and mobile phones (Android application) we will discuss these applications briefly throughout this documentation.

Haramaya University Department of Computer Science, Final Project I Documentation


1.1. Background

Automated face recognition is a relatively new concept. Developed in the 1960s, the first semi-automated system for face recognition required the administrator to locate features ( such as eyes, ears, nose, and mouth) on the photographs before it calculated distances and ratios to a common reference point, which were then compared to reference data. In the 1970s, Goldstein, Harmon, and Lesk used 21 specific subjective markers such as hair color and lip thickness to automate the recognition.

In 1988, Kirby and Sirovich applied principle component analysis, a standard linear algebra technique, to the face recognition problem. This was considered somewhat of a milestone as it showed that less than one hundred values were required to accurately code a suitably aligned and normalized face image.

Today, face recognition technology is being used to combat passport fraud, support law enforcement, identify missing children, and minimize benefit/identity fraud. We have compared the features of Face Recognition System and Fingerprint Recognition system. In the digital age, both systems use the computer software application that can identify individual analyzing the features of facial shape and fingerprint ridges.

Fingerprint Identification System: It is the oldest scientific method of personal identity verification. Fingerprint Scanner authenticates the fingerprint applying digital technology. The basic principle of fingerprint identification is based on the following features:

The fingerprints of any two people cannot be identical. The fingerprint of a person remains the same throughout his life. The pattern of the fingerprints can be expressed by algorithms.

Face Recognition: Modern technique of face recognition provides detailed analysis of face image. There are certain prominent landmarks in each face. Peak and valleys of the face have created these landmarks, which are known as nodal points. There are about 80 nodal points in human face. The software analyzes mainly the following landmarks in face.

Width of the nose Depth of the eye sockets Distance between the eyes The length of jaw lines The shape of cheekbones

Face recognition device also works like fingerprint scanner. It also captures, stores, analyzes and authenticates a specific face from the database of stored images. The main advantage of the



system is that we can use any kind of camera to get the image; the image can be captured without any disturbance. The main disadvantage of the system is higher rate of error. Moreover, the system cannot identify the difference between the identical twins.

Among the above two systems, the fingerprint identification system has more advantages. On the other hand, big establishments like Police, Public Utility System and Corporate use the face recognition system because it is easy to get the face image of a person than to get his fingerprint.

1.2. Problem Definition

Fingerprint and face recognition system is the most widely deployed biometric technologies, with a number of different vendors offering a wide range of solutions. A number of weaknesses may influence the effectiveness of face and fingerprint recognition in certain cases:

Factors such as finger injuries or manual working can result in certain users being unable to use a fingerprint-based recognition system, either temporarily or permanently.

Small-area sensors embedded in portable devices may result in less information available from a fingerprint and/or little overlap between different acquisitions.

It is hard to get the fingerprint of one person without direct contact. It is time consuming to search the manual database of fingerprint and face (photo) of a

criminal. We cannot use the manual database of face and fingerprint remotely (from branch

offices) to get the information needed directly from the location of the manual database; in other word the manual database is not portable.

1.3. Objectives

1.3.1 General objectivesThe general objective of our project is to develop fully functional face and fingerprint recognition and verification system.

1.3.2 The specific objectives

Included in the general objective, our project is also expected to fulfill or achieve the following specific objectives:

Examine the major biometric technologies of today including, iris, voice, signature, fingerprint, face and hand.

Understand the key aspects of these major technologies, namely those relating to the technological, application domain, social, environmental and performance aspects.



Develop a fully operational face and fingerprint recognition application using an object oriented design approach with java.

Investigate the algorithmic structure of such a system and gain insight into how such an application is structured and deployed.

Apply application interface standards to the application design and appreciate the need for standardization in application development.

Understand and explain the need for biometric template file standards such as the Common Biometrics Exchange File Format, (CBEFF).

1.4. Scope

We propose a simple and effective approach for Biometric fingerprint image enhancement and minutiae extraction based on the frequency and orientation of the local ridges and thereby extracting correct minutiae points.

The Face and Fingerprint Recognition System is designed to determine automatically whether two sets of fingerprint ridge detail come from the same finger. The Fingerprint Recognition System is used to identify fingerprints of an individual and verify their identity. Fingerprints as one of many forms of special biometric characters are easy to identify individuals. The goal is to run the Fingerprint Recognition System automatically and correctly. The future plan is to improve the ability of this system to recognize low quality fingerprints images. This device can be used in many different fields as mentioned below:

i. Indentifying crime:

Private detectivesKeeping Federal records of criminals and suspected individual

ii. Security

Secure area scanningLaptop loginDigital information security.

Fingerprint based identification has been one of the most successful biometric techniques used for personal identification. Each individual has unique fingerprints. A fingerprint is the pattern of ridges and valleys on the finger tip. A fingerprint is thus defined by the uniqueness of the local ridge characteristics and their relationships. Small points are these local ridge characteristics that occur either at a ridge ending or a ridge bifurcation. A ridge ending is defined as the point where the ridge ends abruptly and the ridge bifurcation is the point where the ridge splits into two or more branches.



Automatic minutiae detection becomes a difficult task in low quality fingerprint images where noise and contrast deficiency result in pixel configurations similar to that of minutiae. This is an important aspect that has been taken into consideration in this project for extraction of the minutiae with a minimum error in a particular location. A complete minutiae extraction scheme for automatic fingerprint recognition systems is presented. The proposed method uses improving alternatives for the image enhancement process, leading consequently to an increase of the reliability in the minutiae extraction task.

CHAPTER TWO



2. PROPOSED SYSTEM

There are many problems in the existing system, to solve those problems we are going to develop a system that is well structured and computerized. And the goal of our project is to avoid the problems faced in the existing system of the face and fingerprint recognition system and develop fully functional one. To avoid these problems, we have to sort out the functional requirements and non functional requirements of the proposed system.

2.1. Functional Requirements

Functional requirement is a description of activities and services a system must provide. These requirements describe the interactions between the system and its environment independent of its implementation. The environment includes the user and any other external system with which the system interacts. Each is a statement of exactly what the system must do. Functional requirements that must be included in the system are listed below:

2.1.1. User requirements The user should be able to enter records. Each record represents information about a person and contains an image of his/her face

and fingerprint. Records will more or less consist of the following fields:

First name.Last name.Phone.Address (city, state, country etc…).Face templates.Fingerprint templates. ID-number.

The system must be able to take face or fingerprint image as an input and search for a match in the database, and then show the results.

The results should be viewed by showing the faces matches the input, and display the most possible image first, in numerical order.

The user should be able to chose (click on) the result that he/she wants and view the full record’s information of the person.

The system can do noisy filter on images.

2.1.2. Hardware and Software requirements



Various Software and Hardware that are required to do this project are discussed here.

1. Software: The product requires the use of a PC running on JAVA runtime environment or java enabled browser for the web application and an android system for mobile user.

1.1. For the client side (end user)

Running Window XP or later, UNIX, MAC operating system.

Java runtime environment.

Android 2.5 or later recommended Android 3.0

1.2. For the server Side

Running windows server 2003 or later, UNIX.

Java runtime environment

Oracle application server

Oracle mobile server.

2 . H a r d w a r e :The other part of the external interface is hardware interface, this interface describe the hardware part of the system.

A. Hardware requirement for the client computerRAM 1 GB, 2 GB or more recommended for fast access of the application Hard Disk: 5 GB free space to install the Client side application.Input device: Keyboard, webcam (digital camera), fingerprint reader.Outpu t dev ice : Compute r Moni to r .

B. Hardware requirement for the server.

RAM 2GB recommended 6GB or more for big systems this is recommended because image processing work need more memory. Hard Disk: minimum of 15 GB recommended 40GB or more to store the biometric data,we need bigger storage space for storing the image file properly. Input device: Keyboard, Webcam (digital camera), and fingerprint reader.Output device: computer monitor.External firewall if the system needs to be secure.

2.2. Non functional requirements



Non functional requirements include all characteristics that a mobile identification solution should possess which are not related to the identification functionality but rather to the management and administration of the device, to its security or to the usability/ergonomics or environmental requirements. Usability and ergonomics are particularly important for devices which most probably have to be worn on a belt in addition to other devices for a whole shift and must be handled easily and efficiently while interacting with the individual being identified.

Other non‐functional requirements could include elements which are related to the infrastructure environment or capabilities in the service which is going to use the equipment and to the architecture of the complete application (i.e. the distribution of the signal processing and matching functions over the network or to remote servers).Typical examples in this sense are the operating system platform, the choice of which might be influenced by the current or legacy environment or by the availability of suitable algorithms for quality and matching of biometric samples and the computing power/main memory which are greater when heavier local processing is foreseen in the application.

2.2.1. Security Requirements Human face and fingerprint recognition is used for authentication and verification which raise the need for big security. This is because it contains the identity of a person which if get in hand to wrong person or group may cause miss use of a person’s identity or in other word it may give that person’s identity to the hand of identity thieves.The system maintains high level of security by using hardware security and software security.

1. Hardware Security Using firewall hardware’s. Protecting the server room by putting it in secure place.

2. Software Security Using different kind of firewall systems Encrypting the database in high level of encryption. Encrypting the network in high level encryption.

2.2.2. Environmental Requirements The system must be stored in a good place which is cold, which allows the server to perform in its highest performance by allowing it not to get hot.

2.2.3. Maintainability



The system shall be distributed with independent modules or classes for database interface for the databases. This independency brings to easy testability, maintainability, flexibility and easy to use. In general, after the system has been produced, change or improvement may be needed. This could happen because design faults are identified after the system has been failed tested or

because functions need to be added.

2.2.4. Accuracy Human face and fingerprint recognition system need an accurate and correct data from the system that he/she uses for the preparation of reports as well as to make relevant decisions.

We can easily imagine the consequences of any decision that made inaccurate and incorrect data on their basis. We expect to address this major issue through implementing a number of validity checks on the number validity on the person entering the data that is going to be entered to the records of the system.

2.3. System Models

System model helps the analysts to understand the functionality of the system and models are used to communicate with the system. The system model is composed of three individual models:-The functional model: represented by use case and Scenario.

The system object model: represented by classes and objects diagrams and the dynamic model: represented by state chart and sequence diagram based on the proposed system.

In this section we try to analyze the overall activity of the proposed system by using use case, sequence diagrams, activity diagrams and class diagram scenarios.

2.3.1 Use cases and Actors 2.3.1.1 Use CasesUse case modeling identifies and describes the system functions by using a tool called use cases. Use cases describe the system functions from the perspective of external users and in a manner and terminology they understand. To accurately and thoroughly accomplish this demands a high level of user involvement and a subject matter expert who is knowledgeable about the business process or event.

Use cases are the results of decomposing the scope of system functionality into many smaller statements of system functionality. They are representing graphically by a horizontal ellipse with the name of the use case appearing above, bellow, or inside the ellipse. A use case represents a single goal of the system and describes a sequence of activities and user interactions in trying to accomplish the goal. The creation of use cases has proved to be an excellent technique in order to



better understand and document system requirement, but the scenario the use case tells consists of one or more requirements.

Use cases are initially defined during the requirements stages of the life cycle and will be additionally refined throughout the life cycle. During requirements discovery, use cases are used to capture the essence of the organizational problem and to model (at a high level) the functionality of the proposed system. Additionally, they are the starting point for identifying the data entities or objects of the system.

Generally use cases describe the behavior of the system as seen from an actor’s point of view. Behavior described by the use case model is external behavior. Which mean a use case describes a function provided by the system as a set of events that yields a visible result for the actors.

2.3.1.2 Actors

Actors are external entities that interact with the system. Use cases are initiated or triggered by actors. An actor initiates system activities for the purpose of completing some task. An actor is a person, or external system that place a role in one or more interactions with yours system. A relationship between actors and another actor of the classes are indicated in use case diagram, a relationship exists where ever an actor is involved with an interaction described by a use case a relationship can also exist between use cases.

Associations are modeled as line connecting use cases and actors to one another, with an optional arrowhead on one end of the line indicating the direction of the initial invocation of the relationship.

Use cases

Login Capture photo Capture fingerprint Character identification Display information (transaction) Review (Update) analyses Alert notice

Actors Administrator End users

2.3.1.3. Essential use case modeling



Figure 1: Essential Use case Diagram

Use case and actor descriptions



Login Use case

Use case name LoginActor(s) Administrator, End User

Description The username and password to login for Administrator and User

Precondition Administrator and User must be authorized

Post condition Login is successfully

Basic course of Actions

1. Administrator and User want to Login2. Fill the user name and password on the space provide3. Administrator login as Admin and User login as standard user4. Click Login button5. Use case ends

Alternate of courses of Action

Alternative course A: 2. If the Administrator and user is not fill correctly, the login failsAlternate Course A : 5: use case ends

Capture Photo Use case

Use case name Capture photoActor(s) Administrator, End user (embedded digital camera)

Description The photo area provides access to photo capturing process

Precondition Digital camera (Mobile Android) application successfully launched

Post condition Photo displayed


1. Digital camera (Mobile Android) presents to the operator and indication of camera (mobile) readiness to capture photo

2. Administrator and User points camera (mobile) toward the presenter3. Android (camera) application displays to the administrator and user a preview

of the content of the picture4. Administrator and User takes the picture5. The picture is taken and presented to the operator6. Use case ends




Alternative course A: 4. If the administrator and user takes improper photo, he/she cancel the capture processAlternate Course A : 5. If the taken picture has an error, retake the picture (repeat step 2 to 5)Alternate Course A : 6. Use case ends

Capture Fingerprint Use case

Use case name Capture fingerprintActor(s) Administrator, End user ( fingerprint scanner)

Description The capture fingerprints process provides a predefined capture sequence

Precondition The administrator and user has chosen the “capture biometrics” feature of Android application

Post condition The fingerprint capturing process is completed


1. Fingerprint reader displays platen and active capture area of current presenter finger tips

2. Administrator and User places requested print on scanner platen3. Scanner captures the print image after it determines that the print image is

acceptable4. The Application displays the fingerprint captured to the administrator and user 5. Repeat steps 1 to 3 until all required print images are captured6. Use case ends


Alternative course A: 3. If the scanner fails, application indicates the failure of the scanner and the option to capture print is inactiveAlternate Course A : 6. Use case ends

Character Identification Use case



Use case name Character identificationActor(s) Administrator

Description The Administrator chooses character identification option, selects an image and then character to identify

Precondition The image must exist and be processed in order for the characters to be extracted

Post condition New information will be stored in the database


1. Administrator logs into the system2. Verification of log in information is correct3. Administrator clicks on character identification option4. A grid view is made available and returns an image that have already been

entered into the system5. Administrator selects an image from a grid view or adds a new image to the

selection6. A new page is displayed with all of the characters that have made appearances

in the selected image7. Administrator selects an image for a list of photos8. Administrator fills in known information pertaining to selected character9. Data is inserted into the database 10. Administrator can either view the character’s image gallery, view who the

current character interacted with, go on to another page or logout11. Logs the user out or redirects to another page


Alternative course A: 2. If the Administrator fails verification at the log in, error message will display, Administrator will not be able access the system and then he/she will be prompted to try againAlternative course A: 8. If the Administrator fills in unknown information, error message will displayed and he/she prompted to fill the correct again

Display Information Use case

Use case name Display information



Actor(s) End User

Description The Android application will display all available information by using the biometric image captured.

Precondition Android application successfully launched

Post condition Information displayed


1. The Android application resets the alert indication (i.e. all information displayed chronologically)

2. The Android application displays to the user the information that match entries in the Database

3. Use case ends Alternate of courses of Action

Alternative course A: 2. If captured image does not match any entries in the database, access the details of the informationAlternate Course A : 3. Use case ends

Review (Update) Analyses Use case

Use case name Review analysesActor(s) Administrator

Description The Administrator is able to look frame analyses or documents by other user or their own

Precondition Frames must already be analyzed and documents must be submitted in order for them to be reviewed later

Post condition Users can only make changes to their own frame analyses or documents submitted


1. Administrator logs into the system2. Verification login information is correct3. Administrator clicks on review link4. A grid view is made available returns review that have already been entered into

the system5. Administrator selects review from a grid view6. A new page displays with a drop down list of reviews from a particular photo



and documents submitted7. Administrator selects a review from a drop down list or a document from a grid

view8. Administrator views this information9. Verification user is able make changes, redirects to the home page, logs the user

out.10. Administrator can make changes, return to main menu or exit by logging out


Alternative course A: 2. If the Administrator fails verification at the login, an error message will displayed, user will not be able to access the system and the user will be prompted to try againAlternate Course A : 9. If Administrator fails verification to make changes, an error message will display and the user will be unable to make any changes, go to step 10

Alert Notice Use case

Use case name Alert noticeActor(s) End User

Description The system will continuously monitor the return responses and indicate when there is a positive match response received

Precondition The system application must be launched with an active connection

Post condition Matched transaction is indicated


1. Checks if there is a new match response2. If there is a new match the system application presents to the user3. Use case ends

2.3.2. Class DiagramClass diagram depicts the system’s object structure. They show object classes that the system is composed of as well as the relationships between those object classes. The UML



class diagram below shows the classes of the system, their inter-relationships, and the operations and attributes of the classes.

Figure 2 Class Diagram

2.3.3. Sequence Diagram Sequence diagrams are used to depict graphically how objects interact with each other via

messages in the execution of a use case or operation. They illustrate how the operations are

performed between objects and in what sequence.



Sequence Diagram to Record is shown in the figure below.

Figure 3: Sequence Diagram to Record

Sequence Diagram to Store Face and Fingerprint is shown in the figure below.



Figure 4: Sequence Diagram to store Face and Fingerprint

Sequence Diagram to search Face and Fingerprint is shown in the figure below.



Figure 5: Sequence Diagram to search Face and Fingerprint

2.4. Interface



2.4.1. Forms The application more or less contains three or more forms for the desktop application and for the android application there will be 3 or more forms. Here we tried to describe more about the main three forms that will be available in all applications. The forms may change in some way from the original (final application) but there function is the same.

2.4.1.1. Login form The login form is the first which will be displayed both on the android application and desktop application. It will ask the user to insert his ID password and credential to login. There will be more or less 6 credentials level’s from level 1 to level 6 see the figure below.

Figure 6: Login Form

As indicated in above figure, the login page contains the user ID, password and user clearance level and the users should enter the User ID, password correctly and select his level of clearance to get the home page or the main menu.

2.4.1.2. Fingerprint read form



This form is a form which allows as capturing the fingerprint from the reader and show as the progress of the operation.

Figure 7: Fingerprint read form

As indicated in above figure, the fingerprint read form (page) contains the operations performed by the authorized person (administrator) to capture the new finger tips. This form is available only if we logged in successfully.

2.4.1.3. Main Page Window



The main page is the first page which will be displayed if the user Login information is correct and he logged in successfully. There will be different tabs which allow him/her to change and search for information in the database. This interface is also located in both the desktop and the android application.

Figure 8: Main Page Window

As figure 2.7 indicates, after the user login to the system the main menu is displayed, and then the user selects the information from the main menu to go to the forms. After logged in successfully, he/she clicks “add new” button to add a new user or information into the database, clicks “search” button to see the details of stored record, clicks “update” button to update the record and clicks “delete” button to delete the records from the database..



2.4.1.4. Face capture window This form is a form which allows as capturing the Face image from the hard disk and show as the progress of the operation. This form is available only if we logged in successfully.

Figure 9: Face capture window

As indicated in above figure, the face capture form (page) contains the operations performed by the authorized person (administrator) to capture the new face image. This form is available only if we logged in successfully.

2.4.1.5. Search window



This simple to use window allow the user of the system to search the database for some information by selecting the search parameters or can search and show all information stored in the database.

Figure 10: Search window

This page is used to search the information of record from the database. Select the criteria by

which you want to search by clicking one of the radio button and enter the selected on text box

provided. then click on ’search all’ button to search all records and click on ‘search ‘ button to

search specific record.

There may be other forms as we develop the application. The above forms are the most important and available in all three applications.

2.4.2. Activity diagrams (Navigation)



Activity Diagrams are used to Document the logic of a single operation /methods, a single use

case, or the flow of logic of a business operation. In many ways, Activity Diagrams are the

object_ oriented Equivalent of flow charts and Dataflow Diagrams (DFD) from structure

development.

Figure 11: Activity Diagram for computer application

PART II: SYSTEM DESIGN DOCUMENT (SDD)



CHAPTER THREE

3. Introduction3.1 Purpose

System design focuses on decomposing the system into manageable parts. During system design,

we focus on the processes, data structures, and software and hardware components necessary to

implement it. The challenge of system design is that many conflicting criteria and constraints

need to be met when decomposing the system.

The purposes of object–oriented design document is to provide an overview as to how the

proposed system will be used to obtain the information needed to derive the actual

implementation of our system.

3.2 Design Goals

The objectives of Designing are to model a system with high quality and show what the system

will look like after the coding is done. Which allows the programmer to do his job as a

programmer and develop good and error-free system; these also give the developer, the ability to

develop easily maintainable system. These way maintenance programmers can make changes to

the system after it has been put into operation easily.

The field of structured design contains a number of guidelines that help designer determine

which modules, and which interconnections between the modules will best implement the

requirements specified in the system analysis /Requirement gathering phase.

The first step in designing process is to map the essential model of user requirements onto a

configuration of process. Then, within each process, the designer must decide how to allocate

processes and data to different tasks. Finally, we must organize the processes within each task

into a hierarchy of modules, using modeling tool.

The goal of system design is to manage complexity by dividing the system into smaller,

manageable pieces.

CHAPTER FOUR4. SYSTEM DESIGN MODEL



4.1 Subsystem Decomposition

Subsystem decompositions are the process of dividing the system parts in to smaller pieces which help the developer to do his job easily by giving him the ability of focusing on one task at a time.In this part of the documentation we tried to show some parts of our system by dividing them into some parts. The first part is the capturing or enrolling part of the system.

Enrollment: Capture and processing of user biometric data for use by system in subsequent authentication operations. And it is workflow is illustrated in figure 12 below.

Figure 12: Enrollment


Acquire and DigitizeBiometric Data

ExtractHigh Quality Biometric

Features/Representation

Formulate Biometric

Feature/Rep Template

DatabaseTemplate Repository

Authentication/Verification : Capture and processing of user biometric data in order to render an authentication decision based on the outcome of a matching process of the stored to current template.

ExtractHigh Quality Biometric

Features/Representation

Formulate Biometric

Feature/Rep Template

Template Matcher

Decision

Output


Authentication: Enrollment Mode/Stage Architecture is the next stage and it is workflow is illustrated in figure 13 below.

Figure 13: Authentication

Authentication Application: Verification/Authentication Mode/Stage Architecture this stage is the thread stage which is verification and authentication stage of the system workflow. Its workflow is illustrated in figure 14 below..

Figure 14: Authentication Application


BiometricData CollectionTransmission

Signal Processing, Feature Extraction,

Representation

Quality Sufficient?

Yes

No

DatabaseGenerate Template

Additional image preprocessing,

adaptive extraction or representation

Require new acquisition of

biometric

Approx 512 bytes of data per template

BiometricData Collection

TransmissionQuality Sufficient?

Yes

Template Match

DecisionConfidence?

Signal Processing, Feature Extraction, Representation

No

Database

Generate Template

Additional image preprocessing, adaptive extraction/representation

Require new acquisition of biometric

Approx 512 bytes of data per template


The following are the subsystems which the biometric system uses throughout every transaction/ process. We will describe each one as follows.

o Data Collection: Data Collection Module Biometric choice, presentation of biometric, biometric data collection by sensor and its digitization is shown in Figure 15 below.

Figure 15: Data Collection

o Transmission: Transmission Module Compress and encrypt sensor digital data, reverse process its workflow is shown in figure 16 below.

Figure 16: Transmission


TransmissionPresentationSensor

Recollect

Signal Processing Feature Extraction

Representation

Recollect

Biometric Data CollectionTransmission

BiometricPresentationSensor

Com

pre

ssio

n

Tra

nsm

issi

on

Deco

mpre

ss

Encr

ypti

on

Decr

ypti

on

Signal Processing,Feature Extraction,

Representation


o Signal Processing/Matching Module Be aware of potential transmission prior to match its workflow is shown in figure 17 below.

Figure 17: Signal Processing/Matching Module

o Database/Storage: store and hold the biometric template; A Biometric Template is A file holding a mathematical representation of the identifying features extracted from the raw biometric data and stored in the database. The database and the storage workflow is shown in figure 18 below.


T ra ns mis sio n

S ign a l P ro c es sin gF ea tu re E xt ra cti o n,R ep re s en ta ti on

Compression

Transmission

Decompress

Encryption

Decryption

Y es

T emp la te M

a tc hD

a ta ba s e

Gen e ra te T em

p la te

R ep ro ce ss

Qu ali ty

C on tr o l

Dec isio n

C on fid en ce ?


Figure 18: Database/Storage

o Decision model: this stage will cheek if there is there enough similarity to the stored information to declare a match with a certain confidence? If so it show the result. The workflow is shown in figure 19 below.

Figure 19: Decision model


Transmission Signal ProcessingFeature Extraction,Representation

Com

pres

sion

Tran

smis

sion

Expa

nsio

n

Encr

yptio

n

Dec

rypti

on

Yes

Template Match

Generate Template

Reprocess

DecisionConfidence?

Quality Control

DatabaseTemplatesImages

Transmission Signal ProcessingFeature Extraction,Representation

Com

pres

sion

Tran

smiss

ion

Deco

mpr

ess

Encr

yptio

n

Decr

yptio

n

Reprocess

DecisionConfidence?DecisionConfidence?

Quality Control

DatabaseTemplatesImages

Template Match

Generate Template

No

Yes


4.2. Hardware/Software Mapping

This part of the documentation describes the Hardware/Software mapping of the proposed system the Hardware/Software Mapping Of our System is shown in Figure 20 Below.



Figure 20: Hardware/Software Mapping

4.3 Persistent Data Management

The human face and fingerprint recognition system is an image processing application which need more disk space and management than other applications. To do this properly we are using oracle 11g database as a database management system.



Persistent modeling is used to depict the design of the database. We are going to use a relational database since it is the most used database system recently. The persistent classes are used to store most important and permanent information of the system. In persistent modeling we will perform the following activates.

Identifying keys: Primary identifies unique instances of an entity. Identifying entities: entities which are the persistent classes will be stated with their

attributes. The methods of the classes will be used. Inheritances will be included and if there is any associations exist they will also be

included. The attributes will be given data type and initial sizes.

4.4 Access ControlThe human face and fingerprint recognition system needs authentication mechanism to control

the data access by different users, as it is information has to be protected from using by

unauthorized users. So that the software should have a particular mechanism, which allows the

system administrator to manage the data access by users and gives permission to each users

according to their priority given by system administrator, to modify (manipulate) the data. The

detail of the access control is described in the table below.

Table 1 Access Control

Add

use

r

Cap

ture

fac

e an

d fi

nger

prin

t im

age

Del

ete

reco

rd

Sea

rch

reco

rd

of

biom

etri

c

Upd

ate

Giv

e cl

eara

nce

leve

l

Log

in

to

sy

stem

regi

stra

tion

Add

Rec

ord

Biometric

Administrator

User

× ×

CHAPTER FIVE5. DETAILED DESIGN

5.1. Introduction



The Human Face And fingerprint recognition is a system to be developed to show the world

wide used Biometric system And to introduce this system to our countries forensic and other

manual systems. The system uploaded on a central server to be accessed by multiple users. It will

have user-friendly interfaces to interact with the users easily. User will type their user name and

password on the login form and the system will check the validity of the user in the database. If a

match is found the user will be allowed to access the system with the privilege level assigned to

him/her. If a match is not found in the database the system will display a message telling the user

to re-enter the User-ID and password or else service will be denied.

5.2. Object design model

Performance versus flexibility

Performance criteria

Response time. Refers to the time delay the user wait for accessing the application. It is

mainly depend on the connection type of the user internet and the speed of the computer

the user using.

Throughput. Refers to the number of tasks/operations that can be done at a time in our

case the system can handle multiple tasks at a time.

Memory: This is the required memory size, so as to run the application properly. The

proposed system will need minimum of 1GB of Memory for client machines and 4 GB

for server. And internet connection is the first step of processing. Offline users don’t have

the opportunity to use the application properly.

Durability versus platform dependence

This software product is designed to platform independent software in order to run meeting the

following hardware specifications.

3 GHz processor speed



1 GB RAM

20 GB hard disk

The product requires also the use of a PC equipped with a mouth and standard keyboard. A

monitor with not less than 800x600 resolutions and with 256 color capability.

This product requires the use of a PC with Java runtime environment. This software should be

installed on a windows XP or later, UNIX/LINUX, Mac operating system meeting the

following software specification.

The product should run on windows XP or later, UNIX/LINUX, Mac operating system.

For windows XP based systems, a Pentium class processor 3.0 GHZ or faster

Criteria

Dependability criteria

Availability. It refers to the degree to which the system is found doing normal task. The

system works as long as connection is available.

Robustness. Ability to survive when users enter invalid input. It refers to the extent to which

the system works with invalid input. The system doesn’t fail/ crash when the users enter an

invalid input. For instance the users enter the username and password to login into the system

until three times unless the system exits and the user enter an input in each form the system

check the appropriate type and give the type of error the user commit as an alert message .

Usability. The usage of the system must be sensitive. The graphical user interface is

designed in way that simple usage with good look and feel.

Fault Tolerance- ability to operate under erroneous conditions. The system back up data to

avoid loss of data when system crash or damage.

Security. The system is used only by the authorized users.

Authentication-checks identity of the users



Authorization-restricts the user to work on parts of the system pertinent to their

allowed role.

Encryption-hides the real content of the text and the database contents to restrict

unauthorized accesses.

End user criteria

Usability: Easy adaptive for users after a short demonstration about the operation of the user

interface.

Utility: The system can support some additional information including pictures and movies

uploaded on the server and clients can read these posts.

Maintenance criteria

Readability: It is simple to recognize what the system will perform by reading the source

code written using the specified JAVA code. The use of appropriate comments, descriptive

variable naming and indentation will help in this purpose.

Modifiability: The system can be used in any kind of biometric approach we can easily change

the biometric devices and data used.

5.3. Database Design

Database design is the process of producing a detailed data model of a database. This logical data

model contains all the needed logical and physical design choices and physical storage



parameters needed to generate a design in a Data Definition Language, which can then be used to

create a database. A fully attributed data model contains detailed attributes for each entity.

The term database design can be used to describe many different parts of the design of an

overall database system. Principally, and most correctly, it can be thought of as the logical design

of the base data structures used to store the data. In the relational model these are

the tables and views. In an object database the entities and relationships map directly to object

classes and named relationships. However, the term database design could also be used to apply

to the overall process of designing, not just the base data structures, but also the forms and

queries used as part of the overall database application within the DBMS.

The process of doing database design generally consists of a number of steps which will be

carried out by the database designer. Usually, the designer must:

Determine the relationships between the different data elements.

Superimpose(place one thing over another, typically so that both are evident) a logical

structure upon the data on the basis of these relationships

Entity is a thing in real world with independent existence. Entity of the new system are listed below

List of entities along with their attributes are described in the table below.

Table 2: list of entities along with their attributes

No. Entity name Attributes of the entity Data types Primary key

1 Person PID Fingerprint Face image

Char(10)BLOBBLOBVarchar2(50)

PIDFingerprintFace image



2 Personal info PID Name Birth date Birth Place Last Known Address Sex

Char(10)Varchar2(50)Date and timeVarchar2(20)Long Text Char(1)

PID

3 User User ID Level Name Password sex Birth date Job Department DEP-ID Salary

Char(30)INTChar(30)Char(30)Varchar2(20)Varchar2(20)Varchar2(20)Number(10,2)

User ID

4 Level Level INT

Level

5 Department Department Name DEP-ID

Varchar2(20)Char(30)



Figure 21: Database Design



Abbreviation

RAD: REQUIREMENT ANALYSIS DOCUMENT

CBEFF: Common Biometrics Exchange File Format

ACE/V- Analysis, Comparison, Evaluation, and Verification

PC: Personal Computer

MAC: Mackintosh

RAM: Random Access Memory

GB: Giga byte

SDD: System Design Document

PID: Person Identification Number

Definitions

Biometrics: An open-ended set of technologies based on the measurement of some unique physical characteristics of an individual, for the purpose of identifying an individual (or verifying) identity.

Bio-API: An industry standard Application Program Interface (framework) defined by The Biometric Consortium.



References

1. Digital Image Processing An Algorithmic Introduction Using Java By Wilhelm Burger And Mark J.Burge

2. Learn Java for Android Development By Jeff “JavaJeff” Friesen.3. Oracle Database 11g Master SQL and PL/SQL in the Oracle Database By Jason Price4. Oracle Database 11g DBA Handbook Administer a Scalable, Secure Oracle Enterprise

Database By Bob Bryla, Kevin Loney5. http://www.google.com 6. http://www.ibm.com/developerworks/ 7. NeuroTechnology Developers Guide Version: 4.3.0.0.Release date: 9/30/2012.


http://www.ibm.com/developerworks/

http://www.google.com/

Face detection and finger print project documentation

Education

Transcript of Face detection and finger print project documentation