Automated Biometric Identification and Verification for GYEEDA Applicants

1
TABLE OF CONTENT
Declaration ----------------------------------------------------------------------------------- i
Abstract --------------------------------------------------------------------------------------- ii
Dedication ------------------------------------------------------------------------------------ iii
Acknowledgement ---------------------------------------------------------------------------iv
Table of Content------------------------------------------------------------------------------1
Abbreviations and Acronyms ---------------------------------------------------------------8
1.0 CHAPTER ONE: GENERAL INTRODUCTION & SUMMARY
1.1 Introduction…………………………………………………………………10
1.2 Field & Subject Area of Study……………………………………………...11
1.3 Study Objectives……………………………………………………………11
1.3.1 Global Objectives…………………………………………………...11
1.3.2 Specific Objectives………………………………………………… 11
1.4 Problem Statement………………………………………………………….12
1.5 Research Methodology…………………………………………………….. 13
1.6 Background ………………….……………………………………………. 14
1.7 Justification………………………………………………………………...15
1.8 Expected Outcome of the project……………………………………...........15

2
1.9 Safety, Environmental & Economic Aspect………………………………..16
1.10 Significance of Study……………………………………………………….17
1.11 Presentation of Thesis ………………………………………………………17
1.12 Project Implementation and Schedule ………………………………………18
2.0 CHAPTER TWO: LITERATURE REVIEW
2.1 Introduction………………………………………………………………... 20
2.2 Definition & Description of Terms………………………………………. 21
2.2.1 Verification …………………………………….…………………... 21
2.2.2 Biometric…………………………………………………………… 21
2.2.3 Identification………………………………………………………... 21
2.2.4 Systems……………………………………………………………… 21
2.2.5 Automated Biometric Identification System ………………………. 22
2.2.6 GYEEDA ……….………………………………………………….. 22
2.2.7 Information Systems………………………………………………… 23
2.2.7.1 Classifying Information Systems……………………………….…...........................23
2.3 History of Biometric System……………………………………………….. 24
2.4 History of Fingerprint…………………….………………………………… 28
2.5 Levels of Identification……………………………………………………….30
2.6 Types of Biometrics .………………..……………………………………... 31
2.6.1 Signature dynamics ……………………………………………………31

3
2.6.2 Typing patterns ………………………………………………………..31
2.6.3 Eye scans …………………………………………………………….. 31
2.6. 4 Fingerprint recognition ……………………………………………….31
2.6. 5 Hand or palm geometry ……………………………………………….32
2.6. 6 Voice recognition ……………………………………………………...32
2.6. 7 Facial recognition ……………………………………………………...32
2.7 Necessity for Biometric System…………….…………………………….....32
2.7.1 Accurate beneficiary identification ……………………………………..32
2.7.2 Eliminate identity theft ………………………………………………….33
2.7.3 To streamline the user enrollment process ……………………………...33
2.8. System Benefits to the Organization and Applicants…………………….........33
2.8.1 Reliable Accuracy ………………………………………………………33
2.8.2 Increased Productivity …………………………………………………..34
2.8.3 Decreased Burden on One Person or Department ……………………....34
2.9 Advantages of Biometric ……...……..……………………………………….34
2.9 .1 Accurate Identification …………………………………………………34
2.9 .2 Transparency ……………………………………………………...........35
2.9 .3 Accountability ………………………………………………………….35
2.9 .4 Easy and Safe for Use ………………………………………………….36

4
2.9 .5 Time Saving ……………………………………………………....36
2.9 .6 Security …………………………………………………………...36
2.9 .7 Convenience ……………………………………………………...36
2.9.8 Scalability ………………………………………………………....37
2.10 Traditional Way of Keeping Records……………………………………37
2.10.1 Labeling ………………………………………………………….37
2.10.2 Boxing …………………………………………………………...37
2.11 Review of some Existing Biometric system Software’s ……….……37
2.11.1 Bioscrpyt Time Attendance System……..……………………..37
2.11.2 BioLink Biometric Voter Registration System ………………...38
3.0 CHAPTER THREE: RESEARCH METHODOLOGY
3.1 Introduction…………………………………………………………….39
3.2 System Analysis & Design Materials Used……………………………39
3.2.1 System Analysis Material………………………………………39
3.2.1.1 Joint Application Design….……………………………………………………....39
3.2.1.2 Advantages of JAD to gather Requirement………………………………………40
3.2.1.3 Guidelines to a Successful JAD……………………………………………….……42
3.2.2 System Design Architectural Materials…………………………43
3.3 System Construction Method……………………………………………….45

5
3.3.1 Phases or Stages of RAD………………………………………….. 46
3.3.2 Key Players in RAD……………………………………………….. 48
3.3.3 Advantages of the Construction Method………………………….. 49
3.3.4 Weakness of the Construction Method……………………………. 51
3.3.5 When to use RAD…………………………………………………. 51
3.4 System Implementation Approach………………………………………… 52
3.4.1 Requirement Planning Phase………………………………………. 52
3.4.2 User Design Phase…………………………………………………. 52
3.4.3 Construction Phase………………………………………………… 53
3.4.4 Implementation Phase………………………………………………53
3.5 Adopted System Testing Procedure……………………………………….. 54
3.6 Software Testing Strategies………………………………………………... 55
3.6.1 Unit testing …………………………………………………………...55
3.6.2 Integration testing ……………………………………………………55
3.6.3 Performance testing ………………………………………………….55
3.6.4 Acceptance testing …………………………………………………...56
3.7 System Security…………………………………………………………… 56
3.8 Conclusion………………………………………………………………….57
4.0 CHAPTER FOUR: SYSTEM ANALYSIS AND DESIGN

6
4.1 System and Requirement Analysis ……………………………………….….58
4.1.2 Brief Overview of the Proposed System……………………………58
4.1.3 General Requirements …………………………………………...…59
4.1.3.1 Functional Requirements…………………………………...…59
4.1.3.2 Non-Functional Requirements ………………………………..60
4.1.4 Domain Assumption ………………………………………………..61
4.1.5 Software Requirement Specification ……………………………….61
4.1.6 Hardware Requirement Specification ………………………………61
4.1.7 System Requirement ………………………………………………..61
4.2 Feasibility Study ……………………………………………………………...62
4.2.1 Technical Feasibility ………………………………………………..62
4.2.2 Economic Feasibility ………………………………………………..63
4.2.3 Organizational / Operational Feasibility ……………………………64
4.3 System Design ………………………………………………………………………...64
4.3.1 Systems Components ………………………………………………..64
4.3.2 UML diagrams for the System Design ……………………………...65
4.3.2.1 Use case Diagram ………………………………………………….65
4.3.2.2 Usefulness of Use Case Diagraming ……………………………….65
4.3.2.3 Use case descriptions ………………………………………………66
4.3.2.4 Use case description for Process Applicant ……………………….66
4.3.2.5 Use case description for Send mail of approval …………………..67
4.3.2.6 Use case description for Generate Report …………………………68
4.3.2.7 Use case description for Enroll new Applicant ……………………68

7
4.3.2.8 Use case description for Capture Fingerprint ……………………...69
4.3.2.9 Use case description for Verify Fingerprint ………………………..70
4.3.3 Activity Diagram ……………………………………………………………………..70
4.3.3.1 Guidelines for Creating Activity Diagrams ………………………...71
4.3.4 Steps to Constructing a Context Level Diagram ……………………………………...72
4.3.3.1 Benefits of Context Level Diagram ………………………………...73
4.3.4 Advantages of Dataflow Diagrams ……………....…………………...74
4.3.4.1 Level 0 DFD ……………………………...………………………...74
4.3.5 Entity Relationship Diagram ……………………...………………………………….75
4.3.5.1 Entities & their description ………………………………….………76
4.3.6 Data Dictionary …………………………………………………………...………….77
4.3.6.1 Uses of Data Dictionary …………………………………………….78
4.4 System Testing and Demonstration ………………………………………………………...79
4.4.2 Screen Shots of automated biometric identification and verification system ………...81
5.0 CHAPTER FIVE: GENERAL CONCLUTION AND RECOMMENDATION
5.1 Introduction ……………………………………………………………………………….84
5.2 Conclusion of Study …………………………………………………………………..…84
5.3 Limitations ………………………………………………………………………………85
5.4 Future Works and Recommendation …………………………………………………….85
Appendix A ………………………………………………………………………………….86
References……………………………………………………………………………………95

8
Abbreviations and Acronyms
ABIS – Automated Biometric Identification System
ABIVS – Automated Biometric Identification and Verification System
AFIS - Automated Fingerprint Identification Systems
ASP – Active Server Pages
CASE– Computer Aided Software Engineering
CIS - Central Index System
CRUD–Create Retrieve Update Delete
DACS – Deportable Alien Control System
DFD– Data Flow Diagram
DHS – Department of Homeland Security
FIN – Fingerprint Identification Number
GYEEDA – Ghana Youth Employment and Entrepreneurship Development Agency
IAFIS – Integrated Automated Fingerprint Identification System
IDENT - Identifier
INS - Immigration and Naturalization Service
IT–Information Technology
JAD– Joint Application Design
NAILS – National Automated Immigration Lookout System
NCIC – National Crime Information Center
NYEP – National Youth Employment Program
OOAD– Object Oriented Analysis Design
PIN – Personal Identification Number

9
RAD – Rapid Application Development
SQL– Structured Query Language
SWAT- Skilled Workers with Advanced Tools
TECS - Treasury Enforcement Communication System
UML– Unified Modeling Language

10
CHAPTER ONE
GENERAL INTRODUCTION AND SUMMARY
1.1 Introduction
Originally, the word “biometrics” meant applying mathematical measurements to biology. Now
adays, the term refers to a range of techniques, devices and systems that enable machines to rec
ognize individuals, or confirm or authenticate their identities.
NYEP is a governmental organization which was established in 2006 by the John Kufour
administration which is now Ghana Youth Employment and Entrepreneurial Development
Agency GYEEDA. The agency was setup to empowering youths who are citizens of Ghana. The
functions of GYEEDA are to offer employment to Ghanaian youth, to offer requisite working
experience to post-national service personnel and to provide Ghanaian youth with employable
skills. The program started with nine (9) modules in 2006 and also new modules has so far been
added to it. The have youths in agri-business, youths in health extension etc.
The system aim at checkmating corrupt personals and also identify the applicant who enroll to
any module of their choice with the help of a fingerprint.
The system is a web based system which enables applicant to register in any region or district
which is closed to them, they will be given confirmation details sent through their emails and
printed out.

11
1.2 Field and Subject of Study
The field of study Information Technology but the subject area is Software Development and
Networking.
1.3 Study Objectives
The study objectives are grouped into two as stated below;
1.3.1 Global objectives
The general objective of the system is to identify and account for every registered individual in the
system so as to avoid false claimers.
The system will offer a great deal of knowledge or plan of action in the area of biometric system
development (of which in this case will be a system which will enhance integrity of the data and
save cost in an organization)
1.3.2 Specific Objectives
In achieving the general objectives mentioned earlier, this research work will specifically
concentrate on accomplishing the following:
The specific objectives of the study is to design and develop a system
 Offer a secure registration mechanism (of which in this case would be through a
biometric registration and verification process to prevent data redundancy.
 To create a centralized database system that will check or track down over
registration to prevent exceeding the quota for the year.
 To create a system that will automatically generate identification number to
uniquely identify the applicant.

12
 To develop a system that will automatically generate a registration information to
individual applicant by text and E-mail.
 To be able to prompt beneficiaries of any information.
1.4 Problem Statement
The current system is unable to identify unknown applicant who are not officially enrolled into the
program it also cannot keep records of all applicant GYEEDA operations was overhaul last year
by the government because of massive corruption and misuse of public fund under the program.
Those who have undergone their program for the duration of two years still continue to work under
the company which they are posted to due to the fact that there are no mechanism or form of alert
to inform the applicant that their time is due.
There are no formal way to prompt beneficiaries that a program or information is up for them
In order to avoid false claimers and those who will apply multiple times. The current system does
not have biometric fingerprint which will enable the organization to identify the original owners
of their information’s.
Once one is registered into the system there is no centralized database that collect all applicant
data from all region match them to check for redundancy.
All this are challenges that affect a company downfall so this system will help in transparency and
accountability in all the region.

13
1.5 Research Methodology
In order to come up with a successful development of the above system, the Rapid application
development (RAD) methodology will be used.
RAD is a type of incremental model. In RAD model the components or functions are developed
in parallel as if they were mini projects. The developments are time boxed, delivered and then
assembled into a working prototype. This can quickly give the customer something to see and
use and to provide feedback regarding the delivery and their requirements.
 RAD basically has four phases:
 Requirement and Planning: Combines element of system analysis and planning.
 User design phase: User interact with system analyst and develop model and prototype of
all process, input and output.
 Construction phase: Focuses on program and application development task.
 Cutover phase: Deals with system implementation.
Advantages of Rapid Application Development (RAD).
 Reduced development time.
 Increases reusability of components
 Quick initial reviews occur
 Encourages customer feedback
 Integration from very beginning solves a lot of integration issues.
Disadvantages of Rapid Application Development (RAD).
 Only system that can be modularized can be built using RAD
 Requires skilled developers/designers.
 High dependency on modeling skills.
The system will use M y SQL, HTML, PHP, CSS, JQuery, ASP. The Primary data can
be derived from field survey through discussions, close observation of processes and
procedures.

14
Joint Application Development (JAD) will be used as fact- findings techniques that will be used
to gather the requirements analysis on the development of the proposed system.
Phases in RAD:
Business modeling: The information flow is identified between various business
functions.
Data modeling: Information gathered from business modeling is used to define data
objects that are needed for the business.
Process modeling: Data objects defined in data modeling are converted to achieve the
business information flow to achieve some specific business objective
Application generation: Automated tools are used to convert process models into code
and the actual system.
Testing and turnover: Test new components and all the interfaces.
1.6 Background
Background study shows that, youth applies for GYEEDA from all the region in Ghana. Any youth
that is admitted to GYEEDA is required to stay for the maximum of two years in which they will
go through some trainings and raise some money to start up their own business when their time is
due
The age range of applicant are within 18-35 and this are citizens of Ghana, the program tends to
reduce the rate of unemployment in the society by so doing the beneficiaries may have an idea of

15
the module (area) which they will like to function if they don’t they will work as intern which ever
organization they are posted to irrespective of their disability.
So GYEEDA tend to create jobs for the unemployed Ghanaian youths in the country, which is
funded by the government and support from leading organization such as the world bank.
1.7 Justification
At the end of the study, the following will be put into place:
 All Registration to the GYEEDA program will be automated, thereby easily
retrieve information
 A proper report will be generated at the end of every GYEEDA program
registration.
 No User will be able to register twice for the GYEEDA program
 Leading organization who lend support will have access to how profitable the
help is to the society
 Beneficiaries will have access to information and also send message to the agency
1.8 Expected Outcome of the project
At the end of this project, the following becomes the results:
 The system would Offer a secure registration mechanism (of which in this case
would be through a biometric registration and verification process) to prevent

16
data redundancy.
 The system would have a centralized database system that will check and track
down over registration to prevent exceeding the quota for the year.
 The system would automatically generate identification number (PIN) to
uniquely identify the applicant to eliminate redundancy and to help eliminate
ambiguity over who is supposed to be a claimer. The PIN will serve as a login
password which can also be changed by the user.
 The system would automatically generate and registration information to
individual applicant by text and E-mail, in other to avoid loss of information’s by
the user and also make reference to their mail when they want to confirm the
registration and approval of where they are posted to there will be a portal for the
applicant to login to get any information and also send GYEEDA messages.
 The system would be able to prompt beneficiaries of any information which will
come up as a contingency via text message and E-mail.
1.9 Safety, Environmental and Economic Aspects
1. The proposed system is economically feasible because the cost involved in purchasing the
hardware and the software component is less expensive.
2. The operating-environment costs are marginal. The less time involved also helped in its
economic feasibility.

17
1.10 Significance of Study
This study is being proposed to create a management system via Fingerprint in other to give
account of all beneficiaries in the GYEEDA system
1.11 Presentation of Thesis
 Chapter 1:
General introduction is focused on the research which is the Project Proposal.
 Chapter 2:
Literature Review which focuses on history and the outlook of the existing system.
 Chapter 3:
Analysis of Proposed System. In this chapter, the proposed system is analyzed into details
and its importance discussed expansively where context level diagrams, dataflow diagrams,
flowcharts will be used to explain the proposed system further.
 Chapter 4:
Detailed Design of Proposed System; After the Analysis stage, the study carries on with the
design of the system. This chapter will encompass database modeling, class modeling,
use case modeling and the relationship diagram of the proposed system.
 Chapter 5:
Testing and Implementation;

18
Implementation of the computer software goes on after the design. The system will be tested
and reviewed to reveal errors. In this chapter also the documentation of the completed system.
It also lays emphasis on both the users of the system and the system itself. Under the user
documentation, the manual for both the user and the expert who will administer the system
will be known. Finally conclusion and recommendation will be made as well as observations
are identified and the necessary improvement which could be added to the system is made.
1.12 Project Implementation and Schedule
The Study Work Plan of the proposed research is in two parts, thus,
1. Part 1
This would comprise the preliminary investigation, analysis and the actual research into
the problem. The expected completion date is around April, 2015.
2. Part 2
This would comprise the development of the proposed model and its implementation as
well conclusion and recommendation for further research. The expected completion date
is around September 2015.

19
n
GANTT CHART FOR PROJECT ACTIVITIES

20
CHAPTER TWO
LITERATURE REVIEW
2.1 Introduction
This chapter will discuss and review relevant literature in connection with the research on Biometric
Identification Verification system. Critical analysis on various segments of a published body of
knowledge will be carried out through summary, classification, comparison of prior research studies and
articles and observation and findings about their advantages, limitations and recommendations.
The purpose of this literature review is to study the requirement specification, weakness and strengths of
selected systems. After these systems are reviewed, ideas can be gained and implemented on the proposed
system to overcome the weakness of this kind of technology.
Over new of automated and identification system has become popular in recent years because of its
applications like protected access to computer systems, buildings. Person identification is the process of
providing identity to an individual. Person identification techniques are broadly classified into three,
knowledge based, token based and biometric based. A knowledge based approach depends on something
that an individual knows to make a personal identification like password or personal identification
number (PIN). Token – based approaches are based on something an individual have like passport,
driving license, ID card, credit card or keys. But these approaches have lot of demerits: tokens may be
stolen, lost, elapsed or mislaid. But the biometric systems use physiological or behavioral characteristics
of an individual for identification and it cannot be stolen or lost.

21
2.2 Definition & Description of Terms
2.2.1 Verification
In a biometric security system, the process of comparing a biometric sample against a single reference
template of a specific user in order to confirm the identity of the person trying to gain access to a system.
2.2.2 Biometric
Generally, the study of measurable biological characteristics. In computer security, biometrics refers to
authentication techniques that rely on measurable physical characteristics that can be automatically
checked.
2.2.3 Identification
In a biometric security system, the process of comparing a biometric data sample against all of the
systems database reference templates in order to establish the identity of the person trying to gain access
to the system.
2.2.4 System
A group of interdependent items that interact regularly to perform a task. A system can be broadly
defined as an integrated set of elements that accomplish a defined objective. (INCOSE Sys Eng
Handbook, 2000)

22
2.2.5 Automated Biometric Identification System
ABIVS, the Automated Biometric Identification and Verification System (IDENT) is a Department of
Homeland Security (DHS) managed system that is used for the storing and processing of biometric and
biographic information for DHS national security, law enforcement, immigration, intelligence, and other
DHS functions.
In this article, John D. Woodward, Jr., Director of DoD Biometrics from 2003 to 2005, explains the
DoD’s Automated Biometric Identification System (ABIS) initiative, which allows biometric data
gathered by U.S. military forces abroad to be searched in the DoD ABIS database and in the FBI’s
Integrated Automated Fingerprint Identification System (IAFIS), a searchable database with the
fingerprints of approximately 48 million people who have been arrested in the United States. By using
the power of biometric technologies, the U.S. government will be able to positively identify terrorists or
other suspected national security threats. By John D. Woodward, Jr. in December 2004 edition.
2.2.6 GYEEDA
Is a new name given to what was formerly known and called National Youth Employment Programme
(NYEP). The NYEP, now GYEEDA, was introduced by the New Patriotic Party (NPP) Government of
President John Agyekum Kufuor. Which was setup by the sport ministry in 2006 to reduce youth
unemployment in the society by, creating a platform to engage youths within the age range of 18-35yrs
the area which they will fit. With the support the government, NGOs and privates companies for
employments and funding’s. GYEEDA has more than 20 modules which the youths can benefit from,

23
such as Youth in Road Maintenance, Youth in Driving, youth Waste & Sanitation, Youth in Agri-
Business, Youth in Trades and Vocations, Youth in ICT and so on.
2.2.7 Information System
An Information System can be defined technically as a set of interrelated components that
collect (or retrieve), process, store and distribute information to support decision making
and control in an organization. Information is a notoriously difficult concept to pin down.
It is often suggested that we live today in an information age or an information society. For
business organizations and governments, the use they make of information is critical to
their success, to controlling their operations and achieving their goals. In particular,
information is produced and used for decision making.
Information systems are purposive systems. They are established for reasons and have
objectives or goals, designed or established to achieve some stated end. In the case of
computer-based information systems, the stated end will generally be to satisfy the
information requirements of particular people or classes of people – for example, bank
managers or bank customers. At a higher level we could say that information systems are
established to serve the overall strategy of an organization – to help it do what it wants or
chooses to do. (Cornford, & Shaikh. 2013).
2.2.7.1 Classifying Information Systems
Many classifications for information systems exist in the literature

24
The first class of information systems is personal information systems. Such an
information system can manage and store information for a private person.
Examples are an address book or address database and an audio CD collection
Enterprise (or organizational) information systems are the second class of
information systems. An enterprise information system is tailored toward the
support of an organization. Examples are workflow management systems,
enterprise resource planning systems, data warehouse systems, and geographic
information systems.
The third class of information systems is public information systems. Unlike
personal information systems, public information systems can manage and store
information that can be accessed by a community. Public libraries, information
systems for museums, Web-based community information systems, and Web-
based stock-portfolio information systems are examples of public information
systems.
(Cornford, & Shaikh. 2013).
2. 3 History of Biometric System
The Automated Biometric Identification System (IDENT) is a database system using automated
fingerprint identification systems (AFIS) technology as part of programs supervised by the U.S.
Department of Homeland Security that intend to thwart illegal entry into the United States by criminal
aliens.

25
IDENT was implemented on a trial basis in 1994 and put into wide use by 1998. In August 1998, INS
IDENT mangers established standardized policies on the use of IDENT but for financial reasons decided
not to include historical data in the IDENT database. Accordingly, IDENT queries were limited to returns
of data acquired since IDENT implementation. By 1999, approximately 1.8 million biometrics were
keyed into the IDENT "recidivist" (repeat offender) database.
The IDENT system biometrics includes photos and the two index finger fingerprints (entered via a
portable Touch View fingerprint reader) of individuals previously apprehended by border and
immigration agents. That data is augmented by available data on the individual's criminal history. With
this data IDENT provides access to both a recidivist database and a "lookout" database for criminal
offenders.
IDENT fingerprint searches of the two databases normally takes only a few minutes. IDENT fingerprint
matching is based upon a numerical score derived from degrees of relationship in standard fingerprint
characteristics. An IDENT terminal then provides agents with photographs and fingerprint displays of
individuals under examination alongside photographs and fingerprints of potential matches. This final
visual matching is key because, especially under field conditions, fingerprint analysis is often hampered
by dirt on the alien's fingers or the scanner.
Records are ultimately linked to a unique fingerprint identification number (FIN) for each alien. The
IDENT fingerprinting technology does not require ink, but uses a machine that scans and digitizes prints
before transferring them to a standard ten-print card and storing them in the electronic database.

26
Use of the IDENT system is critical because studies have shown that apprehended illegal aliens often
attempt to falsify their identity by providing a fictitious name and/or a birthdate. As of March 2003, the
IDENT database contained records on more than 400,000 aliens who had a history of attempted illegal
entry and a criminal history that precluded their entry into the U.S. Prior to DHS reorganization, INS and
Border Patrol agents had detained more than 75,000 individuals based on IDENT data.
The IDENT system can also provide basic identification information that allows access to several other
security and law enforcement databases including, but not limited to, the Central Index System (CIS),
National Automated Immigration Lookout System II (NAILS), Deportable Alien Control System
(DACS), National Crime Information Center (NCIC) database, and the Treasury Enforcement
Communication System (TECS). Under pending security proposals the IDENT database and system may
be fused with the Integrated Automated Fingerprint Identification System (IAFIS) used by the FBI.
As of March 1, 2003, the newly created United States Department of Homeland Security (DHS) absorbed
the former Immigration and Naturalization Service (INS). All INS border patrol agents and
investigators—along with agents from the U.S. Customs Service and Transportation Security
Administration—were placed under the direction of the DHS Directorate of Border and Transportation
Security (BTS). Responsibility for U.S. border security and the enforcement of immigration laws was
transferred to BTS.

27
BTS is scheduled to incorporate the United States Customs Service (previously part of the Department
of Treasury), and the enforcement division of the Immigration and Naturalization Service (previously
part of the Department of Justice). Former INS immigration service functions are scheduled to be placed
under the direction of the DHS Bureau of Citizenship and Immigration Services. Under the
reorganization the INS formally ceases to exist on the date the last of its functions are transferred.
Although the technologies involved in the IDENT entry security program remained stable, in an effort to
facilitate border security, BTS plans to establish higher levels of coordination between formerly separate
agencies and databases. As of April 2003, the specific coordination and future of the IDENT program
was uncertain with regard to name changes, program administration, and policy changes.
There are a number of different types of biometrics: Some are ages old; others are more recent and
employ the latest technology. Technological advances will surely refine existing methods and lead to
the development of new ones. The most well known biometric technologies include fingerprinting, hand
geometry, signature verification, voice verification, retinal scanning, iris scanning and facial recognition:
but am emphasizing fingerprint.
Fingerprinting: This is the most well known non-invasive biometric technique. There are several sub-
methods within fingerprinting, with varying degrees of accuracy and precision. Some can even detect
when a live finger is present. This method has been refined over the years. Training is an issue with this
technique.

28
2.4 History of Fingerprint
Fingerprints were used on clay tablets for business transactions in ancient Babylon. In 1000-2000 B.C
and 3rd Century B.C. - Thumbprints begin to be used on clay seals in China to “sign”
14th Century A.D. Many official government documents in Persia have fingerprint impressions. One
government physician makes the observation that no two fingerprints were an exact match. And also in
1686 At the University of Bologna in Italy, a professor of anatomy named Marcello Malpighi notes the
common characteristics of spirals, loops and ridges in fingerprints, using the newly invented microscope
for his studies. In time, a 1.88mm thick layer of skin, the “Malpighi layer,” was named after him.
Although Malpighi was likely the first to document types of fingerprints, the value of fingerprints as
identification tools was never mentioned in his writings.
According to Dr. Henry Faulds in 1880, a British surgeon and Superintendent of Tsukiji Hospital in
Tokyo, published an article in the Scientific Journal, "Nautre" (nature). He discussed fingerprints as a
means of personal identification, and the use of printers ink as a method for obtaining such fingerprints.
Faulds had begun his study of what he called “skin-furrows” during the 1870s after looking at fingerprints
on pieces of old clay pottery. He is also credited with the first fingerprint identification: a greasy print
left by a laboratory worker on a bottle of alcohol. Soon, Faulds began to recognize that the distinctive
patterns on fingers held great promise as a means of individual identification, and developed a
classification system for recording these inked impressions. Also in 1880, Faulds sent a description of
his fingerprint classification system to Sir Charles Darwin. Darwin, aging and in poor health, declined
to assist Dr. Faulds in the further study of fingerprints, but forwarded the information on to his cousin,
British scientist Sir Francis Galton.

29
Gilbert Thompson 1882, employed by the U.S. Geological Survey in New Mexico, uses his own
fingerprints on a document to guard against forgery. This event is the first known use of fingerprints for
identification in America.
In the year 1888 specifically Sir Francis Galton’s began his study of fingerprints, primarily to develop
a tool for determining genetic history and hereditary traits. Through careful study of the work of Faulds,
which he learned of through his cousin Sir Charles Darwin, as well as his examination of fingerprints
collected by Sir William Herschel, Galton became the first to provide scientific evidence that no two
fingerprints are exactly the same, and that prints remain the same throughout a person’s lifetime. He
calculated that the odds of finding two identical fingerprints were 1 in 64 billion.
Galton’s book “Fingerprints” is published, the first of its kind. In the book, Galton detailed the first
classification system for fingerprints; he identified three types (loop, whorl, and arch) of characteristics
for fingerprints (also known as minutia). These characteristics are to an extent still in use today, often
referred to as Galton’s Details in 1892.
In 1905, The U.S. Army gets on the fingerprinting bandwagon, and within three years was joined by the
U.S. Navy and Marine Corps. In the ensuing 25 years, as more law enforcement agencies joined in using
fingerprints as personal identification methods, these agencies began sending copies of the fingerprint
cards to the recently established National Bureau of Criminal Investigation.
As Americans become more concerned with the growing missing and abducted children problem, and
law enforcement groups urge the fingerprinting of children for investigative purposes in the event of a
child becoming missing, Chris Migliaro 1996 founds Fingerprint America in Albany, NY. The company
provides a simple, at-home fingerprinting and identification kit for parents, maintaining the family’s

30
privacy while protecting and educating children about the dangers of abduction. By 2001, the company
distributes over 5 million Child ID Fingerprinting Kits around the world.
The FBI phases out the use of paper fingerprint cards with their new Integrated AFIS (IAFIS) site at
Clarksburg in 1999, West Virginia. IAFIS will starts with individual computerized fingerprint records
for approximately 33 million criminals, while the outdated paper cards for the civil files are kept at a
facility in Fairmont, West Virginia.
2015 - World's Largest Database
As of January 2015, the Unique Identification Authority of India operates the world's largest fingerprint
(multi-modal biometric) system, with over 734 million (73.4 crore) fingerprint, face and iris biometric
records. India's Unique Identification project is also known as Aadhaar, a word meaning "the foundation"
in several Indian languages. Aadhaar is a voluntary program, with the ambitious goal of eventually
providing reliable national ID documents to most of India's 1.2 billion
2.5 Levels of Identification
With biometric technology, a more robust level of security and protection can be achieved in the
identification component of access control, ID, and verification programs. Three basic means or levels
of identification are often referred to in identity management functions:
 The lowest level is defined as “something you have” In your possession, such as an ID badge
with a photograph on it.
 The second level is “something you know,” such as a password used with computer login or PIN
code to use at a bank ATM.

31
 The highest level is “who you are,” which encompasses biometrics - the measurement of physical
characteristics or traits.
2.6 Types of Biometrics
A number of biometric methods have been introduced over the years, but few have gained wide
acceptance.
2.6.1 Signature dynamics
Based on an individual's signature, but considered unforgeable because what is recorded isn't the final
image but how it is produced, differences in pressure and writing speed at various points in the signature.
2.6.2 Typing patterns
Similar to signature dynamics but extended to the keyboard, recognizing not just a password that is typed
in but the intervals between characters and the overall speeds and pattern.
2.6.3 Eye scans
This favorite of spy movies and novels presents its own problems. The hardware is expensive and
specialized, and using it is slow and inconvenient and may make users uneasy.
2.6.4 Fingerprint recognition
Fingerprints are unique way of identifying persons. They are also readily accessible and require little
physical space either for the reading hardware or the stored data.

32
2.6.5 Hand or palm geometry
This method but seldom think of an entire hand as an individual identifier. This method relies on devices
that measure the length and angles of individual fingers. Although more user-friendly than retinal scans,
it's still cumbersome.
2.6.6 Voice recognition
This is different from speech recognition. The idea is to verify the individual speaker against a stored
voice pattern, not to understand what is being said.
2.6.7 Facial recognition
Uses distinctive facial features, including upper outlines of eye sockets, areas around cheekbones, the
sides of the mouth and the location of the nose and eyes. Most technologies avoid areas of the face near
the hairline so that hairstyle changes won't affect recognition.
2.7 Necessity for Biometric System
The increase applicability of biometrics as a practical individual identification tool is a key reason it is
one of the fastest evolving technologies around the world. Seen as a technology that is a logical
replacement for antiquated and cumbersome personal identification numbers (PINs) and passwords,
biometrics is a more secure alternative to enhance individual identification accuracy and system security
2.7.1 Accurate beneficiary identification - Traditional beneficiary identification methods are no
longer adequate and accurate patient identification with biometric technology is starting to create
a big buzz among organization facilities all over the world. Correctly identifying user at the point
of entry to the program facility should be the first priority for organization. The use of biometrics

33
for beneficiary identification not only identifies user upon arrival and at each point along the
care continuum, but it also accurately links organizational procedures to the correct the system
records to avoid mistakes that can jeopardize people safety.
2.7.2 Eliminate identity theft – Beneficiaries identity theft occurs when a person steals another
individual’s personal information such as a social security number or medical insurance card in
order to receive payment for medical treatment or to buy drugs and services. According to a recent
study by the Ponemon Institute, nearly 1.5 million Americans have been victims of identity theft
with an estimated total cost of $28.6 billion. By deploying biometric user identification
technology, organization can eliminate user identity theft because biometric devices such as
fingerprints spanner or palm vein readers recognize people’s physical traits which are near nearly
impossible to steal, fake, or spoof.
2.7.3 To streamline the user enrollment process - Biometrics facilitates a fast, simple and user
friendly enrollment process. The process is time saving, easy to use and truly guards the users
against false identity theft and the creation of duplicate the system records.
Sr. Executive - SEO/SEM/PPC in M2SYS Technology.
2.8 System Benefits to the Organization and Applicants
2.8.1 Reliable Accuracy
The system helps to track down over registered applicant and also to prompt applicant on when their
contract with the company will end in other to recruit other youth. A manual timekeeping system requires
applicants to report their hours worked per pay period after the fact. Unfortunately, recording employees’

34
time in and out for each work day after it has been worked increases your organization’s exposure to the
likelihood of inaccurate time tracking.
2.8.2 Increased Productivity
When it’s time to recruit the youth, if you’re using a manual process, the collection of time cards, reentry
of data into a spreadsheet, and time necessary to process every single applicant from all district can be
tedious and laborious. Automating the collection of time through data collection devices ensures time
records are in an electronic format. This allows the transfer of that data to be automatically sent to system.
2.8.3 Decreased Burden on One Person or Department
With a manual process, human resource management means keeping massive amounts of paper-based
applicant and timesheet data files on each of your employees. Maintaining these types of records can be
both time consuming and inefficient and becomes especially cumbersome when key employment
information is requested by managers or payroll personnel.
2.9 Advantages of Biometric
Biometrics have offered a scalable solution to business owners who are now empowered to circumvent
issues like undocumented access, ID swapping, manual badge checks, credential replacements and more.
2.9 .1 Accurate Identification
While traditional security systems are reliant on passwords, personal identification numbers (PINs) or
smart cards, you can achieve a high level of accuracy with biometrics systems. If you have set up the
system correctly, you can use biological characteristics like fingerprints, which offer you unique and

35
accurate identification method. These feature cannot be easily duplicated, which means only the
authorized person gets access and you get high level of security.
2.9.2 Transparency
 The identity of the data controller in the organization.
 The purpose in processing the data.
 Any third party to whom the biometric data will be given.
It is essential that students are aware of the purpose for which the biometrics data will be processed. This
means that the organization must carefully think through any purpose or potential purpose. Is the system
solely for identification management purposes? Will it be used for access control? What are the
consequences for the beneficiaries concerned if there is an identified abuse of the system? Under what
circumstances will management access logs created by the system?
Transparency is even more important where the biometric system does not require the knowledge of the
beneficiaries. A fingerprint recognition system, for instance, may capture and compare images without
that person's knowledge.
2.9.3 Accountability
Biometric log-ins mean a person can be directly connected to a particular action or an event. In other
words, biometrics creates a clear, definable audit trail of transactions or activities. This is especially
handy in case of security breaches because you know exactly who is responsible for it. As a result you
get true and complete accountability, which cannot be duplicated.

36
2.9.4 Easy and Safe for Use
The good thing about using biometrics for identification is that modern systems are built and designed to
be easy and safe to use. Biometrics technology gives you accurate results with minimal invasiveness as
a simple scan or a photograph is usually all that’s required. Moreover the software and hardware can be
easily used and you can have them installed without the need for excessive training.
2.9.5 Time Saving
Biometric identification is extremely quick, which is another advantage it has over other traditional
security methods. A person can be identified or rejected in a matter of seconds. For those business owners
that understand the value of time management the use of this technology can only be beneficial to your
office revenue by increasing productivity and reducing costs by eliminating fraud and waste.
2.9.6 Security
Another advantage these systems have is that they can’t be guessed or stolen; hence they will be a long
term security solution for your company. The problem with efficient password systems is that there is
often a sequence of numbers, letters, and symbols, which makes them difficult to remember on a regular
basis.
2.9.7 Convenience
It’s considered to be a convenient security solution because you don’t have to remember passwords, or
carry extra badges, documents, or ID cards. You are definitely saved the hassle of having to remember
passwords frequently or changing cards and badges. People forget passwords and ID cards are lost, which
can be a huge nuisance with traditional security methods.

37
2.9.8 Scalability
Biometrics systems can be quite flexible and easily scalable. You can use higher versions of sensors and
security systems based on your requirements. At the lowest level you can use characteristics that are not
very discriminative; however if you are looking for a higher level of security for large scale databases
then you can use systems with more discriminable features, or multi-modal applications to increase
identification accuracy.
2.10 Traditional Way of Keeping Records
2.10.1 Labeling
Labeling is of two kinds: Of the containers, and of row ends in the stack areas after the shelving
has been completed.
2.10.2 Boxing by keeping applicants records in a box for reference purpose. All this can be gutted
by fire or get missing.
2.11 Review of some Existing Biometric system Software’s
2.11.1 Bioscrpyt Time Attendance System
from Cardzme in Dubai. Bioscrpyt is an innovative biometric fingerprint/PinPad/Ip Connectivity
reader for Time and Attendance & Access Control applications.
Key features include:
 Wide selection of Access control machine options.
 Realtime access from anywhere.

38
 Powerful reporting & workforce analytics
 Administrators & Employee portal
 Flexible scheduling interface
2.11.2 BioLink Biometric Voter Registration System
BioLink Biometric Voter Registration System (BVRS) is a highly advanced biometric information
system that allows to enroll and identify millions of voters quickly and unmistakably. Using
biometric identifiers, the possibility of election fraud is minimized, at the same time considerably
accelerating the voter identification process.
Key features include:
 A full range of biometric parameters to identify the voters by fingerprints, iris, voice
etc.
 Highly customizable software modules for both input and output settings
 Comprehensive data logs and reports for thorough voter activity monitoring
 Wide range of supported hardware (fingerprint scanners, IRIS/Face cameras etc.)
 Highest level security settings for data protection

39
CHAPTER THREE
RESEARCH METHODOLOGY
3.1 Introduction
This chapter takes into consideration the various findings made in the review of the existing
systems. In other words the methodology is a collection of procedures, techniques, tools and
documentation aids, which will help the system development in the efforts to implement a new
system. The types of methodologies in the system development are: Structured System Analysis
and Design Methodology, Structured System Analysis, Information Engineering, Object –
Oriented System Analysis and Design etc. (Whitten et al., 1998; Bennett et al. , 2002; Dennis et
al. , 2005)
.3.2 System Analysis and Design Materials used
3.2.1 System Analysis Material
In defining the requirement as a basis of understanding why an Automated Biometric Identification
and Verification System should be built and also identify clearly the size of the research scale
development and major requirements of the research, Joint Application Development (JAD) will
be used to few fact- findings techniques that will be used to gather the requirements if the
Automated Biometric Identification and Verification System will be much feasible to be
implemented in Ghana.
3.2.1.1 Joint Application Development (JAD)
JAD (Joint Application Development) is a met6odology that involves the client or
end user in the design and development of an application, through a succession of

40
collaborative workshops called JAD sessions. Chuck Morris and Tony Crawford,
both of IBM, developed JAD in the late 1970s and began teaching the approach
through workshops in 1980.
The JAD approach, in comparison with the more traditional practice, is thought to
lead to faster development times and greater client satisfaction, because the client
is involved throughout the development process. In comparison, in the traditional
approach to systems development, the developer investigates the system
Requirements and develops an application, with client input consisting of a series
of interviews.
3.2.1.2 Advantages of Using JAD to gather Requirements
• Reduced system development time.
In JAD, information can be obtained and validated in a shorter time frame by
involving all participants who have stake in the outcome of the session
• Accelerates design.
JAD is quoted the best method for collecting requirements from the users,
customers, or customer advocates. Important process like requirement
gathering requires the involvement and commitment of business area experts.
The cost of taking them away from their daily operation is very high. JAD
session creates the opportunity of bringing them together within a minimum
period of time.
• Enhances system quality and productivity.

41
JAD involves users in the development life cycle, lets users define their
requirements, and thus ensures that the system developed satisfies the actual
activities of the business.
Reduced development time reduces the labor cost for developers, as well as
users. JAD can reduce the involvement time of these business experts and hence
reduce the cost further
• Promotes teamwork with the customer.
The JAD sessions let designers and users work together in the very early of the
development cycle, defining the scope, requirements of projects, resolving
conflicts among different user groups.
• Creates a design from the customer's perspective.
Because users are fully involved in the JAD session their concept can easily be
grasped and implemented. Customers are not left out when it comes to JAD.
• Lowers development and maintenance costs.
Cost is also reduced by catching errors, misunderstandings and mistakes early
in the development phrase. Studies have found that a majority of system errors
result from early analysis errors, and the earlier these errors are corrected, the
much less they will cost.
• Enhanced education for participants and observers.

42
By participating in JAD and be the medium between other users and IT, the
business end-users will be kept fully informed about the progress of the system
development.
• JAD enhanced communication and relationship between business end-users
and IT personnel.
Preparation is an important factor in whether or not you have a successful JAD
session. The right participants need to be selected, and those participants must
actively participate in the JAD sessions. The wrong participants and/or lack of
participation can have a negative effect on the conversations and deliverables
that come from JAD sessions.
3.2.1.3 Guidelines for Successful JAD
During the process of gathering information, the researcher followed some
guidelines which assisted to the success of the gathering information. These
guidelines are summarized below:
• Use experienced and skilled facilitators
• Get Executive Sponsor’s commitment and support
• Get the right people to participate, predefine their roles and responsibilities
• Set clear defined, well understood and obtainable goals or objectives
• Plan detailed agenda and stick with it
• Define deliverables clearly in advance

43
• Keep Technical Jargon to a Minimum
• Produce Final Document Quickly
3.2.2 System Design Architecture Materials
Object Oriented Analysis &Design (OOAD) using UML is a system development methodology
and applies object – modeling techniques to analyze the requirement for a system, an organization
or a business unit and to design a solution (Whitten et al. (1998). The Unified Modeling language
(UML) has become the standard modeling language used in OOAD to graphically illustrate system
concepts. The UML defines a graphical notation for expressing object-oriented designed (Alan &
Barbara & David, 2005). The UML will be used because the strategic value of software increases
for many companies, the industry looks for techniques to automate the production of software and
to improve quality and reduce cost and time-to-market.
These techniques include component technology, visual programming, patterns and frameworks.
Businesses also seek techniques to manage the complexity of systems as they increase in scope
and scale. In particular, they recognize the need to solve recurring architectural problems, such as
physical distribution, concurrency, replication, security, load balancing and fault tolerance.
Additionally, the development for the World Wide Web, while making some things simpler, has
exacerbated these architectural problems. The Unified Modeling Language (UML) was designed
to respond to these needs.
The UML has three famous parts of a system’s model which are Functional, Object Model and
Dynamic Model. Firstly, the function model explains the point of user’s view which is system
functionality. It included Context Diagram to identify the external entities that exchange
information with the business system, Data-Flow Diagram (DFD) that shows representation of the

44
"flow" of data through an information system, Use Case Diagram object model used in showcasing
the static structure in terms of classes and relationships in the system, Class Diagram dynamic
model to display the internal system behavior, Sequence Diagrams diagram that details of how
operations are carried out, what are the messages and it is organized depending on time,
collaboration diagram shows object, link to another object and messages and Activities Diagrams.
This project will use UML to describe the Automated Biometric Identification and Verification
System from the user requirement to system implementation. Diagrams which involved Context
Diagram, Data-Flow Diagram, Use Case Diagram, Class diagram for data and function
specifications, Activity diagram, and Sequence diagram are chosen in the architectural design
phases.
Secondly, the Object Model showcases the structure and substructure of the system using objects,
attributes, operations, and associations. The structural view includes class diagrams and composite
structure diagrams
Thirdly, Dynamic (or behavioral): Showcases the internal behavior of the system. It emphasizes
on the dynamic behavior of the system by showing collaborations among objects and changes to
the internal states of objects. This view includes sequence diagrams, activity diagrams and state
machine diagrams.
Boochet al (1998) have agreed with the statement about the definition of UML, where UML is a
visual modeling language that is used to specify and to document models of software systems,
including their structure and design in the way that meets all of these requirements.

45
UML notations will be used to model the users’ requirements and were chosen because UML is a
standardized notation and it is easy to use and to understand.
3.3 System Construction Method
The adopted methodology is Rapid application development (RAD). Rapid application
development (RAD) is a methodology that promises organizations the ability to develop and
deploy strategically important systems more quickly while simultaneously maintaining quality and
reducing development costs (George M, 2006). Stanley Marcus of Neiman Marcus said, “There
are only two things of importance. One is the customer, and the other is the product. If you take
care of customers, they come back. If you take care of the product, it doesn’t come back. It’s just
that simple. And it’s just that difficult.” Rapid Application Development, in addition to providing
a more quality product in less time, also ensures greater customer satisfaction. By reducing the
elapsed time between User Design and Cutover, RAD increases the likelihood that the system will
be satisfactory to the users, whose demands are met much quicker than ever before.
The RAD process also directly integrates the end-users in the development of the application.
Iterative prototyping mandates that the development teams concentrate on delivering a series of
fully functional prototypes to designated user experts. Each prototype is tested by those users and
returned to the development team for reworking, at which point the cycle repeats. The series of
prototypes thus evolves into the final product, giving the users the opportunity to fine-tune the
requirements and review the resulting software implementation.
Today, many development organizations are adopting iterative development methodologies
emphasized by Rapid Application Development (RAD) cycles. Unlike waterfall development life

46
cycles, where testing is done at the end of the project, iterative life cycles specify testing at multiple
points during development. It is easy to understand the importance of including system
performance analysis and predictive tuning in the process. Identifying the addressing flows early,
especially performance limitations, has as advantage the cuts of the cost to fix them and at the
same time minimizes the impact on the project schedule. RAD has been proven to be a valuable
software strategy.
3.3.1 Phases or Stages of Rapid Application Development
Business modeling: The information flow is identified between various business functions.
The business model for the product under development is designed in terms of flow of
information and the distribution of information between various business channels. A
complete business analysis is performed to find the vital information for business, how it
can be obtained, how and when is the information processed and what are the factors
driving successful flow of information.
Data modeling: Information gathered from business modeling is used to define data objects
that are needed for the business.
The information gathered in the Business Modeling phase is reviewed and analyzed to form
sets of data objects vital for the business. The attributes of all data sets is identified and
defined. The relation between these data objects are established and defined in detail in
relevance to the business model.

47
Process modeling: Data objects defined in data modeling are converted to achieve the
business information flow to achieve some specific business objective. Description are
identified and created for CRUD of data objects. The process model for any changes or
enhancements to the data object sets is defined in this phase. Process descriptions for
adding, deleting, retrieving or modifying a data object are given.
Application generation: Automated tools are used to convert process models into code and
the actual system.
Testing and turnover: Test new components and all the interfaces. The overall testing time
is reduced in RAD model as the prototypes are independently tested during every iteration.
However the data flow and the interfaces between all the components need to be thoroughly
tested with complete test coverage. Since most of the programming components have
already been tested, it reduces the risk of any major issues.
RAD model enables rapid delivery as it reduces the overall development time due to
reusability of the components and parallel development.
RAD works well only if high skilled engineers are available and the customer is also
committed to achieve the targeted prototype in the given time frame. If there is commitment
lacking on either side the model may fail.

48
3.3.2 The key players in a Rapid Application Development project include:
• Sponsor
A high- level user executive who funds the system and is dedicated to both the value
of the new system and to achieving results quickly.
• User Coordinator
A user appointed by the Sponsor to oversee the project from the user perspective.
Requirements Planning Team a team of high-level users who participate in the Joint
Requirements Planning workshop.
• User Design Team
A team of users who participate in the design workshop. This team should be
comprised of both high-level users from the Planning Team and lower-level users with
a more detailed knowledge of the system.
• User Review Board
A team of users who review the system after construction and decide whether
modifications are necessary before cutover.
• Training Manager
The person responsible for training users to work with the new system.
• Project Manager
The person who oversees the development effort.
• Construction (SWAT) Team

49
The SWAT (Skilled Workers with Advanced Tools) Team is a small team of two to six
developers who are highly trained to work together at high speed. To achieve the fastest
possible development, the team members must be highly skilled in the RAD
methodology and in using the chosen CASE toolset.
• Workshop Leader
The specialist who organizes and conducts the workshops for Joint Requirements
Planning and Joint Application Design.
3.3.3 Advantages of the Construction Method
• Faster Delivery Time
The primary advantage of RAD is a faster development life cycle, and a better
turnaround time of the software product. This is achieved by rapid prototyping, and
by using automated tools like Computer Aided Software Engineering or CASE
tools, that enable the developers to re-use previously generated codes, thus saving
the time needed for manual coding. The CASE software tools are a major
contributing factor in reducing the delivery time in the RAD methodology.
• Greater Customer Satisfaction
The RAD methodology involves active participation of the customers and end users
in all stages of analysis and development of the application. It is especially helpful
in scenarios where the user requirements are uncertain, or not fixed. The
development team offers a series of functional prototypes to the end users, and

50
integrates customer feedback at every stage of development. This cycle is repeated
until a series of such prototypes result into a fully-integrated final product.
• Time Boxing
RAD uses a process called time boxing, which offers a method of controlling the
features to be released in the current, as well as the future versions of a software
product. This helps in releasing the product version in a shorter frame of time, by
including only the essential features in the current version. It aims at dividing the
project into sub-modules called time boxes, and allocating fixed deadlines and
budgets for each time module.
• Lower Cost
Customers are willing to pay more for a good quality product delivered in a short
time frame. RAD involves the use of existing reusable components, leading to a
lower cost of production. Automation results into a lesser number of resources
being required for the development of the software.
• Reduced Risk
Due to the iterative approach and prototyping, testing and integration of end user
feedback happens at each stage of product development. Hence, the end product
has lesser number of changes and defects, thereby minimizing the risks involved in
the project. There is little or no testing effort involved.

51
3.3.4 Weakness of the Construction Method
The following weaknesses where identified during the project by the developer or
researcher.
• Developers and customers must be committed to rapid-fire activities in an
abbreviated time frame and hard to use with legacy systems.
• This model doesn’t work well in a situations where alteration can occur once the
process has started according to plan. As compared to the prototype approach which
alterations can be done while developing the system.
It might be harder to gauge progress because there are no classic milestones, or could less
efficient because code isn’t hand crafted.
• High dependency on modeling skills.
• Suitable for systems that are component based and scalable.
Also there is the danger the requirements may not converge because the interests of
customers may diverge from one iteration to the next
3.3.5 When to use RAD model
In course of developing the Automated Biometric Identification and Verification System,
the developer discovered that RAD should be used when there is a need to create a system
that can be modularized in 2-3 months of time.
It should be used if there’s high availability of designers for modeling and the budget is
high enough to afford their cost along with the cost of automated code generating tools.

52
RAD SDLC model should be chosen only if resources with high business knowledge are
available and there is a need to produce the system in a short span of time (2-3 months).
3.4 System Implementation Approach
The structure of the RAD lifecycle is thus designed to ensure that developers build the systems
that the users really need. This lifecycle, through the following four stages, includes all of the
activities and tasks required to scope and define business requirements and design, develop, and
implement the application system that supports those requirements.
3.4.1 Requirements Planning Phase
The Requirements Planning stage (also known as the Concept Definition Stage) consists
of meetings in Joint Application Development (JAD) Workshops between requirements
planning team and key client users. The meetings will focus on both developing a high
level list of initial requirements as well as setting the project scope. The requirements
planning team identifies primary business functions and initially breaks them down into
business entities (such as Product, Sale, Company, Sales Person). The Requirements
Planning stage ought to result in a list of entities as well as action diagrams that define the
interactions between processes and data elements.
3.4.2 User Design Phase
At the User Design Phase (also known as the Functional Design Stage) the analysis team
will meet with end users in Joint Application Development (JAD) Workshops. During the
workshops the analysis team flushes out the requirements in more detail, develops the

53
entities developed in the Requirements Planning into a data model (Entity Relationship
Diagram), formalizes business rules, develops test plans, and creates screen flows and
layouts for essential parts of the system. During the latter half of the User Design stage the
development team (also known as the SWAT or Skilled Workers with Advanced Tools
team) aids the analysis team in activities such as creating a working data model that can be
converted to a functional database, and in identifying reusable components. Again, as
mentioned in the Requirements Planning stage, all requirements should be captured in a
tool.
3.4.3 Construction Phase
The initial iteration of the Construction Phase will focus on a feature light prototype. In
order to keep development iterations as short as possible, and to gain the maximum benefit
of RAD’s agile nature, core requirements will be identified and targeted for the initial
prototype, and secondary requirements will be identified and targeted for future
development iterations. Beyond a vertical limiting of scope, such as removing entities or
use cases from the initial scope, a horizontal type limiting of scope will be considered as
well, such as not developing field validation, not developing file upload/download
capabilities, or focusing on just the strengths of the particular CASE tool being used
without manually adding much developer customization.
3.4.4 Implementation Phase
Also known as the Deployment Stage, this stage includes final user testing and training, data
conversion, and the implementation of the application system. Because Rapid Application
Development is such a sweeping change from the conventional development methods, the best

54
way for a manager to introduce new rapid development techniques is to start small. Original
Construction Teams of two to four people will be established and their members will be thoroughly
trained in the use of the tools and techniques. As these teams gain experience, they will be able to
fine-tune the development lifecycle to improve its effectiveness in their environment. Underlying
all of this progress, however, managers will remember the importance of comprehensive and
quality training in the use of tools. Good training with tools that are exciting to use can have a
profound impact on the attitude of IT professionals, as well as ensure the uninterrupted success of
the rapid development project.
3.5 Adopted System Testing Procedures
System Testing is needed to show completeness, it improve the quality of the software and to
provide the maintenance aid.
Glen Myers [MYE79] in 1979 in his book “The Art of Software Testing”, states a number of
objectives:
1. Testing is a process of executing a program with the intent of discovering errors. This is also
called regression testing.
2. A good test case is one that has a high probability of finding undiscovered errors.
3. A successful test is one that reveals undiscovered errors.
The following testing techniques were used for the proposed system.
• White-box Testing: Testing of software is predicated on close examination of procedural
detail. Logical paths through the software are tested by providing test cases that exercise
specific sets of conditions and/or loops. The "status of the program" may be examined at

55
various points to determine if the expected or asserted status corresponds to the actual
status. (Pressman & Herron, 1991).
• Black-box Testing: Black-box testing, also called behavioral testing, focuses on the
functional requirements of software. This testing method enables the software engineer to
derive the input conditions that will fully apply all requirements for a program. Black-box
testing attempts to find the errors such as:
- Incorrect or missing functions
- Interface errors
- Errors in data structures or external database access
- Behavior or performance errors
- Initialization and termination errors
In Black-box testing software is exercised over a full range of inputs and outputs are
observed for correctness.
3.6 Software Testing Strategies
Testing strategies employed by the developer were:
3.6.1 Unit testing
The first level of test to be completed is unit testing. The purpose of unit testing is to ensure
that each program is fully tested.
3.6.2 Integration testing
The second step is integration testing. In this individual program units or programs will be
integrated and tested as a complete system to ensure that the software requirements are met.

56
3.6.3 Performance testing
Performance testing will be completed to determine how a system performs in terms of
responsiveness and stability under a particular workload. It can also serve to investigate
measure, validate or verify other quality attributes of the system, such as scalability,
reliability and resource usage.
3.6.4 Acceptance testing
Acceptance Testing involves planning and the execution of various types of tests in order
to demonstrate that the implemented software system satisfies the requirements.
3.7 System Security
The system security problem is divided into four related issues: security, integrity, privacy and
confidentiality. They determine the file structure, data structure and access procedures as stated
above in the data rationale.
• System security refers to the technical improvements and procedures applied to the
hardware and operating systems to protect against deliberate or accidental damage from a defined
threat. In contrast, data security is the protection of data from loss, disclosure, modifications and
destruction.
• System integrity refers to the proper functioning of programs, appropriate physical security
and safety against external threats such as eavesdropping and wiretapping. In comparison, data
integrity makes sure that do not differ from original from others and how the organization can be
protected against unwelcome, unfair or excessive dissemination of information about it.

57
• The term confidentiality is a special status given to sensitive information in a database to
minimize the possible invasion of privacy. It is an attribute of information that characterizes its
need for protection. System security is the technical means of providing such protection. In
contrast privacy is largely a procedural matter of how information is used.
3.8 Conclusion
In conclusion the Biometric Identification and verification system in general who would want to
move from the old system of filing and computing of yearly reports for their cherished customers
who waste a lot of time due to the manual ways of doing things. We believe that through the
practical example of the application of the concept in this project, we will be able to invariably
encourage developers to design solutions that limit, if not completely eliminate the use of Manual
identification and verification system of operation among the rural and urban areas in Ghana

58
CHAPTER FOUR
System Analysis and Design
4.1 System and Requirement Analysis
Requirements analysis comprises of the processes involved in ascertaining user needs. Users are
major stakeholders in system development therefore gathering their needs is paramount.
Requirement analysis also involves identifying the various functionalities of the system.
Furthermore, the researchers used various tools for this analysis which will include context level
diagram, flowcharts, data flow diagrams, and use case diagram of the proposed system. The
researchers also described the processes, flow of data and requirements needed to run the system
this features will represented through Data modeling.
4.1.2 Brief Overview of the Proposed System
The proposed system aims at checkmating corrupt personals and also identify the applicant
who enroll to any module of their choice with the help of a fingerprint. The system is a
desktop based system which enables applicant to register in any region or district which is
closed to them, they will be given confirmation details sent through their emails and printed
out.
The system will offer a great deal of knowledge or plan of action in the area of biometric
system development (of which in this case will be a system which will enhance integrity
of the data and save cost in an organization).

59
The system aims at ensuring all registration to the GYEEDA program to be automated,
thereby making retrieval of information easier. A proper report will be generated at the end
of every GYEEDA program registration. No user will be able to register twice for the
GYEEDA program. Beneficiaries will have access to its information and also send message
to the agency.
Summarily, the proposed system will perform the following functions:
 Registration of GYEEDA program applicant.
 Biometric enrolment of members
 Biometric verification of members
 Report Generations
 Search Engine
 Send E-mails
4.1.3 General Requirements
The main requirement of the proposed system is categorized into:
 Functional requirement
 Non-functional requirement
4.1.3.1 Functional Requirements
 The system shall allow applicant registration.
 The system shall allow registration and creation of admin.

60
 The system shall authorize and authenticate users before granting them access.
 The system shall be able to scan and record users’ thumbprint.
 The system shall be able to validate and verify users’ thumbprint.
 The system shall notify the user when the registration vacancy is full within a
particular region.
 The system shall notify applicants upon completion of their registration through
email as well as informing them of any upcoming events.
 The system shall automatically generate a unique PIN to applicants after
registering.
4.1.3.2 Non-Functional Requirements
 The system shall have a clear interface with only needed features, terminally and
whenever necessary .Warning or alerts shall be specified in a clear way.
 The system shall respond to different searches being conducted like, searching for
a GYEEDA applicant.
 The system shall generate reports with a response time of 5seconds.
 The response time for any search must be 5seconds.
 The system should not have a downtime more than 5 times in a month.
 The system shall be independent of the specific technological platform used to
implement it.
 A user access to any data or the system itself shall be controlled.
 System backup shall be maintained by system administrator and the system shall
provide automatic backup options.

61
 The system shall allow easy recovery from errors like allowing of duplicate of the
same registration PIN.
 The system shall be available for use 24 hours per day.
4.1.4 Domain Assumption
1. GYEEDA applicants has a little or intermediate knowledge of computer usage.
4.1.5 Software Requirement Specification
Operating System: WINDOWS XP, Vista, Windows 7, Windows 8, Windows 10, Linux.
Language (Front end): VB.Net
Database (Back end): My SQL
ARCHITECTURE: 3 Tier Architecture
4.1.6 Hardware Requirement Specification
PROCESSOR: Intel 2.0 GHz or above
HARDDISK: 80 GB
RAM: 800 MB
4.1.7 System Requirement
1. Pentium 4 with minimum 1.x GHz processor equivalent processor
2. Minimum 128 MB RAM (1 GB RAM recommended)
3. Hard disk with minimum 1 GB free space
4. NIC (network interface card) connected to network Pentium III
5. RAM : 64 MB.

62
6. Hard disk : 10.2 GB.
7. Monitor : SVGA color monitor
8. Keyboard : 105 standard mouse.
4.2 Feasibility Study
Feasibility analysis usually involves a thorough assessment of the operational needs, financial
and technical aspects of a proposal. Feasibility study is the test of the system proposal made to
identify whether the user needs may be satisfied using the current software and hardware
technologies, whether the system will be cost effective from a business point of view and
whether it can be developed with the given budgetary constraints. (Bentley, 2007).
In implementing the automated biometric identification and verification system, the following
feasibility analysis were performed;
a. Technical Feasibility
b. Economic Feasibility
c. Organizational Feasibility
4.2.1 Technical Feasibility
Technical Feasibility deals with the hardware as well as software requirements.
Technology is not a constraint to type system development. We have to find out whether
the necessary technology, the proposed equipment’s have the capacity to hold the data,
which is used in the project, should be checked to carry out this technical feasibility.

63
The following technical feasibility issues raised during the feasibility stage of investigation
includes the following;
 This system is running in windows XP, WINDOWS 7, and WINDOWS VISTA
Operating System, which can be easily used.
 The minimum hardware required is Pentium based server.
 The system can be expanded.
4.2.2 Economic Feasibility
This feasibility study here presents tangible and intangible benefits from the prefect by
comparing the development and operational cost. This system needs some more initial
investment than other existing system, but it can be justifiable that it will improve quality
of service.
Thus, the following Economic feasibility study carried center along the following
points:
 Improvement resulting over the existing method in terms of accuracy, timeliness.
 Cost comparison
 Estimate on the life expectancy of the hardware
This system is economically feasible. It does not require much cost to be involved in the
overall process. This is because acquiring the software to run this application is common
and can be easily got from the internet for free.

64
4.2.3 Organizational / Operational Feasibility
This analysis involves how it will work when it is used and the assessment of users’
environment in which it is implemented. People are inherently resistant to change and
computers have been known to facilitate change. The proposed system is very much
useful to the users and therefore it will accept broad users provided one is registered on
this system across the country and worldwide.
4.3 System Design
System design focuses on the architecture of the system and the underpinning structure and
philosophy used. Defining the structure of the design from a high level system viewpoint provides
the basis of the more detailed design of each component part of the system. The architecture of the
system defines how it will be layered and partitioned to encapsulate the system functionality into
manageable components or subsystems. System design also determines the physical platform for
the system and how the various services should be distributed.
4.3.1 Systems Components
Modules Description
There are 4 types of Modules. They are:
Administrator Module
 Creating administrator for various regions.
 Create special programs for youths to apply on.

65
Enrolment Module

 Enroll youths to GYEEDA program
 Update information of applicants.
 Capture biometric fingerprint of applicants.
4.3.2 UML diagrams for the System Design
4.3.2.1 Use case Diagram
A Use Case diagram is a graphical representation of the high-level system scope. It includes use
cases, which are pieces of functionality the system will provide, and actors, who are the users of
the system.
4.3.2.2 Usefulness of Use Case Diagraming
i. The use case diagram provides a comprehensive summary of the whole system software in
a single illustration.
ii. The use cases are mainly composed of narrative text. Hence, unlike many other modeling
techniques, the non-technical stakeholders (e.g. customer, end users) are also able to
understand the model for the software system.
iii. Another major advantage of use case modeling is that it requires the identification of
exceptional scenarios for the use cases.
The use case diagram for the automated biometric identification and verification system is
shown below.

66
Figure 4.1, use case diagram for the automated biometric identification and verification system
4.3.2.3 Use case descriptions
Use case descriptions contain all the information needed to produce use case diagrams. Although
it is possible to skip the use case description step and move directly to creating use case diagrams
and the other diagrams that follow, users often have difficulty describing their business processes
using only use case diagrams. Through the creation of use case descriptions, users can describe
the required details of each individual use case.
4.3.2.10 Use case description for Process Applicant
Use case name Process Applicant

67
Participating Actor Administrator
Entry Condition 1. Administrator is already logged into the system.
Flow of event 1. The administrator clicks on view new applications.
2. The system displays all new registered application.
3. The administrator verifies all details of the applicants
4. The administrator clicks on the process applicant button to finalize
their registration when all requirements are met.
Exit Condition Log out, End session
Exceptions If any execution error happens due to data-base connection which is not
to happen frequently, the system handles it in a common page
4.3.2.11 Use case description for Send mail of approval
Use case name Send mail of approval
Entry Condition 1. Administrator is already logged into the system
Flow of event 1. The administrator clicks on view processed applications.
2. The system displays all processed application.
3. The administrator clicks on “send approval letter” button.
4. The system sends approval letter to the all applicants that has been
approved.
Exit Condition Log out, End session
to happen frequently, the system handles it in a common page

68
4.3.2.12 Use case description for Generate Report
Use case name Generate Report
Entry Condition 1. Administrator is already logged into the system.
Flow of event 1. The Administrator clicks on “Generate Report” menu option.
2. The system prompts the administrator to choose the kind of report
to be generated (daily, weekly, monthly or quarterly).
3. The administrator selects the kind of report to be generated.
4. The system displays the report for the administrator to view or
print.
Exit Condition Log out, End session, Proceed with other operations
Exceptions If any execution error happens due to data-base connection which is
not to happen frequently, the system handles it in a common page
4.3.2.13 Use case description for Enroll new Applicant
Use case name Enroll new Applicant
Participating Actor Operator
Entry Condition 1. Operator logs in using a user_id and a password
2. The credentials will be validated and access will be granted.
Flow of event 1. The Operator clicks on “add new applicant” button
2. The system displays a form for the operator to fill
3. The operator enters the complete details of an applicant and clicks on
the “register” now button.
4. The system validates the inputs
5. The system displays a confirmation message and saves the entry

69
6. The system generates a PIN for an applicant
Exit Condition Log out, End session, Proceed with other operations
to happen frequently.
4.3.2.14 Use case description for Capture Fingerprint
Use case name Capture Fingerprint
Flow of event 1. Operator clicks on “capture print” button
2. The system displays a new capture print form.
3. The Operator enters the PIN of the applicant.
4. The Operator prompts the applicant to place his/her thumb on the
scanner.
5. The system captures the print of the applicant
6. The system disbands the selected associations and display a new list
of alumni association
Exit Condition Log out, End session.

70
4.3.2.15 Use case description for Verify Fingerprint
Use case name Capture Fingerprint
Flow of event 1. Operator clicks on “verify print” button
2. The Operator prompts the applicant to place his/her thumb on the
scanner.
3. The system captures the print of the applicant
4. The system compares the print captured with other existing prints to
find a match.
5. If a match exists, the system shows “print already exists” message.
Else the system displays “match not found” message.
Exit Condition Log out, End session.
4.3.3 Activity Diagram
Activity diagrams are used to model the behavior in a business process independent of objects.
Activity diagrams include notation that addresses the modeling of parallel, concurrent activities
and complex decision processes. As such, activity diagrams can be used to model everything from
a high-level business workflow that involve many different use cases, to the details of an individual
use case, all the way down to the specific details of an individual method. In a nutshell, activity
diagrams can be used to model any type of process.

71
4.3.3.1 Guidelines for Creating Activity Diagrams
Scott Ambler has suggested the following guidelines when creating activity diagrams:
1. Since an activity diagram can be used to model any kind of process, you should set the context
or scope of the activity being modeled. Once you have determined the scope, you should give the
diagram an appropriate title.
2. You must identify the activities, control flows, and object flows that occur between the activities.
3. You should identify any decisions that are part of the process being modeled.
4. You should attempt to identify any prospects for parallelism in the process.
5. You should draw the activity diagram.
Activity diagrams are comprised of activities or actions, objects, control flows, object flows, and
a set of seven different control nodes (initial, final-activity, final-flow, decision, merge, fork, and
join).
Furthermore, swimlanes can be used to enhance the readability of the diagrams. The activity
diagram is very useful in aiding the analyst in identifying the relevant use cases for the information
system being developed.

72
Figure 4.3, Activity diagram for Automated biometric identification and verification system
4.3.4 Steps to Constructing a Context Level Diagram
i. Identify the external entities that exchange information with the business system that is the
target of analysis.
ii. Identify the data flows to and from each external entity.
iii. Draw a process box at the center of the diagram to represent the highest level business
process that will exchange information with the external entities. The central process

73
becomes the root of a process decomposition diagram such as a Function Chart or Dataflow
Diagram which uses the flow of data as the criteria for decomposition.
4.3.3.1 Benefits of Context Level Diagram
i. It shows the scope and boundaries of a system at a glance including the other systems that
interface with it.
ii. No technical knowledge is assumed or required to understand the design.
iii. Easy to draw and amend due to its limited notation.
iv. Easy to expand by adding different levels of DFDs.
v. Context diagram can benefit a wide audience including stakeholders, business analyst, data
analysts, and developers.
The context level diagram for the automated biometric identification and verification system is
shown below.
Figure 4.4 context level diagram for the automated biometric identification and verification
system.

74
A Dataflow Diagram (DFD) is a graphical representation of the flow of data through an
information system. The purpose is to provide a semantic bridge between users and system
developers. It enables the developer to represent the processes in an information system from the
viewpoint of data. DFD helps to visualize how the system operates, what the system accomplishes
and how it will be implemented, when it is refined with further specification. There are two types
of DFDs, both of which support a top-down approach to systems analysis, whereby analysts begin
by developing a general understanding of the system and gradually break components out into
greater detail:
4.3.4 Advantages of Dataflow Diagrams
i. It shows a simple graphical technique of the entire system which is easy to understand.
ii. It helps to define the boundaries of the proposed system.
iii. It is useful for communicating current system knowledge to the users.
4.3.4.1 Level 0 DFD for automated biometric identification and verification system
Figure 4.5 level 0 DFD for automated biometric identification and verification system

75
4.3.5 Entity Relationship Diagram
An Entity-relationship model (ERM) is an abstract and conceptual representation of data.
Entity Relationship modeling is a database modeling method, used to produce a type of conceptual
schema of a system.
An entity-relationship diagram is a data modeling technique that creates a graphical representation
of the entities, and the relationships between entities, within an information system.
The three main components of an ERD are:
 The entity is a person, object, place or event for which data is collected. For example, if
you consider the information system for a business, entities would include not only
customers, but the customer's address, and orders as well. The entity is represented by a
rectangle and labeled with a singular noun.
 The relationship is the interaction between the entities. In the example above, the customer
places an order, so the word "places" defines the relationship between that instance of a
customer and the order or orders that they place. A relationship may be represented by a
diamond shape, or more simply, by the line connecting the entities. In either case, verbs
are used to label the relationships.
 The cardinality defines the relationship between the entities in terms of numbers. An entity
may be optional: for example, a sales rep could have no customers or could have one or
many customers; or mandatory: for example, there must be at least one product listed in an
order. There are several different types of cardinality notation; crow's foot notation, used
here, is a common one. In crow's foot notation, a single bar indicates one, a double bar
indicates one and only one (for example, a single instance of a product can only be stored

Automated Biometric Identification and Verification for GYEEDA Applicants

Automated Biometric Identification and Verification for GYEEDA Applicants

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (17)

Semelhante a Automated Biometric Identification and Verification for GYEEDA Applicants

Semelhante a Automated Biometric Identification and Verification for GYEEDA Applicants (20)

Automated Biometric Identification and Verification for GYEEDA Applicants