Biometric Fingerprint Based ATM Transaction

System

We accept the work contained in the report titled “Biometric Fingerprint Based
ATM Transaction System”, written by Mr. MUHAMMAD AWAIS and Mr. SYED
ADEES GILLANI as a confirmation to the required standard for the partial fulfill- ment
of the degree of Bachelor of Science in Computer Science.

Approved by ...:

Supervisor: Dr. MONEEB GOHAR

.....................................................................................

Internal Examiner: SIR USMAN SHAFIQ

.....................................................................................

External Examiner: ENGR. ASIF ALI

.....................................................................................

Project Coordinator: Dr. SUMAIRA KAUSAR

 .....................................................................................

Head of the Department: Dr. FAISAL BASHIR

..................................................................................... May

27, 2018

i
Abstract

Biometric system is a pattern identification system that recognizes an individual by

determining the originality of the physical features and behavioral characteristic of that
person. Of all the recently used biometric techniques, fingerprint identifica- tion
systems have gained the most popularity because of the prolonged existence of
fingerprints and its extensive use. Fingerprint is dependable biometric trait as it is
an idiosyncratic and dedicated. It is a technology that is increasingly used in various
fields like forensics and security purpose. The vital objective of our system is to make
ATM transaction more secure and user friendly. This system replaces traditional
ATM cards with fingerprint. Therefore, there is no need to carry ATM cards to perform
transactions. The money transaction can be made more secure without worrying
about the card to be lost. In our system we are using embedded system with biometrics
i.e. r305 sensor and UART microcontroller. The Fingerprint and the User ID of all
users are stored in the database. Fingerprints are used to identify whether the
Person is genuine. A Fingerprint scanner is used to acquire the fingerprint of the
individual, after which the system requests for the PIN (Personal Identification Number).
The user gets three chances to get him authenticated. If the fingerprints do not
match further authentication will be needed. After the ver- ification with the data stored
in the system database, the user is allowed to make transactions.

ii
Acknowledgements

Firstly, we have to thank the All-Mighty Allah, the Most Beneficent and the Most
Merciful, who gave us knowledge and strength to achieve this goal as our Final Year
Project. We have done our best but it would not have been possible without the
kind support and help of our families and teachers for their support throughout our
studies and project. We would also like to thank all of them. We would also like
to express our special thanks to Dr. Moneeb Gohar for his guidance, continuous
supervision and support. He provided us the help needed for the successful and
timely completion of our project.
.

Muhammad Awais

Syed Adees Gillani

Islamabad,Pakistan

iii
Contents

Abstract i

1 Introduction 1
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Problem Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.4 Project Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.5 Tools Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.5.1 System Requirement Analysis . . . . . . . . . . . . . . . . . . 2
1.5.2 System integration and testing. . . . . . . . . . . . . . . . . . 3
1.5.3 Research on the available tools and libraries . . . . . . . . . . 3
1.6 Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.7 System integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.7.1 Risks Involved: . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.7.2 Resource Requirement: . . . . . . . . . . . . . . . . . . . . . 4
1.8 Solution Application Areas . . . . . . . . . . . . . . . . . . . . . . . . 4
1.9 Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Literature Review 5
2.1 Previous Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1.1 Sichuan University . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1.2 Moheb R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1.3 Manvjeet Kaur . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.4 Clement Hob . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.5 Ratha M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.6 Anil Jain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.7 Mayank Vatsa . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.8 Proposed System . . . . . . . . . . . . . . . . . . . . . . . . . 7

3 Requirement Specifications 9
3.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.3 Document Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.4 System features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.4.1 Technical Field . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.4.2 System Environment . . . . . . . . . . . . . . . . . . . . . . . 10
3.5 Basic Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.6 User Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.7 Performance Requirements . . . . . . . . . . . . . . . . . . . . . . . . 11 iv
CONTENTS 5

3.8 Budget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.9 Database of Bank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.10 Users Fingerprint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.10.1 Transaction Authentication . . . . . . . . . . . . . . . . . . . 12
3.11 Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.11.1 Facility of aborting transaction . . . . . . . . . . . . . . . . . 12
3.11.2 Email code format . . . . . . . . . . . . . . . . . . . . . . . . 12
3.11.3 Facility of Email reentering . . . . . . . . . . . . . . . . . . . 12
3.11.4 Denial of specific services, if Email goes wrong . . . . . . . . . 12
3.11.5 Register finger . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.11.6 Facility of reentering the finger . . . . . . . . . . . . . . . . . 12
3.11.7 Denial of service, if fingerprint goes wrong . . . . . . . . . . . 13
3.12 Non-Functional Requirements . . . . . . . . . . . . . . . . . . . . . . 13
3.12.1 Scope: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.12.2 Functionality: . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.12.3 Usability: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.12.4 Reliability: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.12.5 Performance: . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.12.6 Security: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.13 Front End Description . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.14 Back End Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.15 Login Use Case I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.16 Sign Up Use Case II . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.17 Authentication Use Case III . . . . . . . . . . . . . . . . . . . . . . . 17

4 Design 19
4.1 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.1.1 Design Constraints . . . . . . . . . . . . . . . . . . . . . . . . 19
4.1.2 Sequence Diagram . . . . . . . . . . . . . . . . . . . . . . . . 19
4.1.3 Login Sequence Diagram . . . . . . . . . . . . . . . . . . . . . 19
4.1.4 Sign Up Sequence Diagram . . . . . . . . . . . . . . . . . . . 19
4.2 Software Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.3 Communication Interface . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.4 Performance Requirements . . . . . . . . . . . . . . . . . . . . . . . . 20
4.4.1 Performance prerequisite 1 . . . . . . . . . . . . . . . . . . . . 20
4.4.2 Performance prerequisite 2 . . . . . . . . . . . . . . . . . . . . 20
4.4.3 Performance prerequisite 3 . . . . . . . . . . . . . . . . . . . . 20
4.5 Other Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5 System Implementation 25
5.1 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1.1 Server-side system . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1.2 Web Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.2 System Internal Component . . . . . . . . . . . . . . . . . . . . . . . 25
5.2.1 Sign Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.2.2 Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.2.3 Deposit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.2.4 Withdraw . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.2.5 Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
CONTENTS 6

5.2.6 Encryption-Decryption . . . . . . . . . . . . . . . . . . . . . 26
5.2.7 Email Generation . . . . . . . . . . . . . . . . . . . . . . . . 26
5.3 Tools and Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.3.1 .Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.3.2 Visual Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.3.3 Web Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.3.4 MySQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.4 Development Environment/Languages Used . . . . . . . . . . . . . . 27
5.5 Framework Access Security . . . . . . . . . . . . . . . . . . . . . . . . 27
5.6 Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.6.1 Phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.6.2 Phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.6.3 Phase 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.6.4 Phase 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

6 System Testing and Evaluation 29

6.1 Graphical User Interface Testing . . . . . . . . . . . . . . . . . . . . . 29
6.2 Usability Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.3 Software Performance Testing . . . . . . . . . . . . . . . . . . . . . . 29
6.4 Compatibility Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.5 Exception Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.6 Load Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.7 Installation Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.8 Testcases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.9 Testing and Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.9.1 Performance Testing: . . . . . . . . . . . . . . . . . . . . . . 33
6.9.2 Security Testing: . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.9.3 Non-Functional Testing: . . . . . . . . . . . . . . . . . . . . . 33

7 Conclusion 35
List of Figures

3.1 Use case 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.2 Use Case 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.3 Use Case 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.1 Activity Diagram 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.2 Sequence Diagram 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.3 Sequence Diagram 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.4 Sequence Diagram 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.5 Sequence Diagram 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.6 Sequence Diagram 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

vii
List of Tables

3.1 Use case 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.2 Use case 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.3 Use case 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.4 Use case 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.5 Use case 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

6.1 Test case 1 (sign up I) . . . . . . . . . . . . . . . . . . . . . . . . . . 31

6.2 Test case 2 (sign up II) . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.3 Test case 3 (Log in I) . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.4 Test case 4 (Log in II) . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.5 Test case 5 (Deposit I) . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.6 Test case 6 (Deposit II) . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.7 Test case 7 (With-Draw I) . . . . . . . . . . . . . . . . . . . . . . . . 32
6.8 Test case 8 (With-Draw II) . . . . . . . . . . . . . . . . . . . . . . . . 32
6.9 Test case 9 (Transfer I) . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.10 Test case 10 (Transfer II) . . . . . . . . . . . . . . . . . . . . . . . . . 33

viii
Chapter 1
Introduction

1.1 Overview
Technological advancement has played dynamic role in setting up Automated or
Computerized systems for the analysis of signatures which has significantly decreased the
issues in fraud. Automated biometric systems can be considered a reliable de- velopment
and have a noteworthy influence on all kinds of organizations. Many different
techniques for automated biometric systems have been proposed which are available in
the market, among which face recognition system, fingerprint recogni- tion system, vein
reader system etc. are very common in use and are employed at different level in
organizations. Biometric Attendance Systems provide the flexibility to identify the
person using different set of features such as face, finger prints, iris etc. and therefore
insures that no case of pilfering and fraud may occur. Biometrics are a smart are reliable
solutions to many problems faced during the past years.

1.2 Objective
Our object is to deliver security through biometric fingerprint authentication in auto-
mated transaction application proceeded by designing an application for fingerprint
identicality based on procedures that detect similar pattern.

1.3 Problem Description

The Traditional systems that are based on Pin Code security systems enable any- one
rather than the owner to access account, data and personal information easily which
indicates the fact that ATM systems are not fully secure and functional in these
cases. This ensures that the current system could be hijacked. The bio- metric
system offers several advantages over traditional security measures and is a noticeable
upgrade in security. Biometrics based security systems (fingerprint recog- nition) are far
most secure and accurate than traditional password or token-based security system and
accessed by the unauthorized user. Also, the traditional secu- rity systems are always
prone to accuracy as compared to biometrics which is more accurate. Traditional security
systems face the problem that they dont give solution to the problem of individuals
having multiple IDs. They give us a system in which an individual cant possess multiple
IDs and cant change his ID throughout his life

1
CHAPTER 1. INTRODUCTION 2

time. Each individual is identified through a unique Biometric identity throughout the
world. There is an issue of unregistered people for the bank that are not in the database
records. We can also perform new user registration at runtime through new
registration at ATM by fingerprint scans. In traditional security systems one ID can be
used by multiple individuals. For example, in case of a password based security system
a single password can be shared among multiple individuals and they can share the
resources allotted to a single individual. Biometric based secu- rity system doesnt allow
such a crime. Here each individual has a single unique ID and it cant be shared with any
other individual [1].

1.4 Project Scope

This project will define the security on new implementation bases which is more
secure than the current system being used. The current security of the system can be very
well compromised, in this particular situation the biometrics security easily prevails.
There is also a chance of saving your identity into a set of particular prints which will
redefine identity and increase security, mobility and availability of an interactive
environment. Database which has a secure line access through biometric encryption will
in terms affect overall security, decreasing the chances of system hacking or
penetration of firewall and defense systems inside the main system [2].

1.5 Tools Used

The Front-end interface will be fully dependent on .Net framework platform, with
Html and PHP as the programming linguistic due to these reasons:
1. Flexible interface that is non-technical and easy to use.
2. User information is secured and customizable.
3. The system operates on good performance and is highly reliable.
4. Interface is based on the principles of Human Computer Interaction and has been
made to be used at the best of its design.
5. MS SQL Server 2012 R2.
6. Visual Studio 2013.
7. .Net Framework 4.5 and 2.0.
8. Bootstrap with access to html for online Web portal.
In the process of database creation and development we are using MySQL Server-
side database due to the following reasons:
1. Inherent support and complete compatibility with .NET platform.
2. Elastic, Accessible and vigorous database architecture.
3. This system is preferred and used by innovative leading companies worldwide.
4. Easy to manage and secure data protection.

1.5.1 System Requirement Analysis

• Development of an ATM Web Simulator.

• To configure and integrate the fingerprint scanner to apprehend and store

fingerprints of different users.
CHAPTER 1. INTRODUCTION 3

• Designing a database for loading fingerprint templates, account number and

users information.

1.5.2 System integration and testing.

• Requirements Specification.

• Visit a Bank for information collecting.

• Collect and understand system requirements based on data provided/and gath- ered.

1.5.3 Research on the available tools and libraries

• Acquiring necessary software and hardware for fingerprint identification and
verification.
• System Design and Implementation.

• Design of an ATM simulator.

• Fingerprint scanner configuration.

• Database development.

1.6 Testing
• Unit testing.

• System Testing.

• Documentation based on working prototypes.

1.7 System integration.

• Integration of components.

• Final Documentation based as a user manual for high protection ATM systems with
fingerprint identification and user manual.

1.7.1 Risks Involved:

• Financial institutions considered their systems security information confiden- tial.

• Thumb print maybe damaged, to counter this face we will use two fingers for
fingerprint recognition.

• If the device used for fingerprint recognition, scanner is faulty then we will use
another as a backup.
CHAPTER 1. INTRODUCTION 4

1.7.2 Resource Requirement:

Finding the Fingerprint scanner for fingerprint image recognition and processing
based on patterns inside the palm and fingers. Prototype for an ATM system to be
implemented using the fingerprint sensors.

1.8 Solution Application Areas

Security issues will be resolved in all banking areas as biometric system is
secure. Viability of the user as biometric cannot be elapsed with more security to personal
information. All banking areas will be covered as the safety of bank customers
money. Also, the processing time will increase with the cost to set up the system
for these purposes [3].

1.9 Motivation
We are doing this final year project in order to ease the security reason and threats
specifically in ATM Banking system. We will implement all of our set of skills, from the
knowledge me and my partner learned during the time spent in university. In this way
we will move forward with a strong belief of achieving a goal within the given
period of time. Hence, improving our programming skills [4].
Chapter 2

Literature Review

This chapter will discuss the literature review of the Biometric Based ATM Transac- tion
System. The existing systems that generate manual scheduling for the desired projects
will be discussed in this chapter. An increase in security concerns has brought on
renewed attention for research on biometric methods in recent years. The rise in
terrorism and the worlds reaction towards it has led governments and individuals to
become more proactive in the case of security issues, leading everyone to take more
action. Every individual has a need to protect their homes, assets, possessions, and
working environments. This need leads to security becoming one of the top daily
priorities for an individual. There already exist several biometric techniques for
verification, with more being developed and improved day by day, with the most
successful of these techniques end up being used for security and law enforcement
applications. One such technique is fingerprint recognition, which is considered as
the most powerful biometric technique for the most secure authen- tication, as
every individual has their own distinct set of fingerprints. As sensor technologies
advance, and demands for biometrics increase, the biometric industry is being driven to
develop newer and newer technologies. Increase in commercial incentives is leading
to new technologies being developed for person identification, with each technology
having its drawbacks and strong points within the niche mar- ket. This chapter will
continue to review some well-known biometric techniques, especially fingerprint
sensors.

2.1 Previous Works

2.1.1 Sichuan University
Proposed an adaptive pore model which would extract fingerprint pores [16]. A
skeletonizing method or an isotropic pore model are used to extract sweat pores
which can be used for automated fingerprint recognition. The fingerprint image to be
used is divided into blocks. A localized pore model for each block is determined and the
pores from each block are extracted using a matched filter.

2.1.2 Moheb R
Proposed extracting images off of the web and deducing the regions of the ex-
tracted images corresponding to skin color[17]. The performance evaluation pre-

5
CHAPTER 2. LITERATURE REVIEW 6

sented showed the performance and accuracy of the system in extracting the web
images before loading the web page and after loading it from a local host or server and
showed the result in the number of images extracted. The results also compare the two
skin detection techniques by the number of detected pixels.

2.1.3 Manvjeet Kaur

Proposed using minutiae extraction technique for fingerprint verification[18]. The
technique was implemented into a system but the problem with minutiae matching was
the handling of poor quality impressions.

2.1.4 Clement Hob

Proposed national identity e-commerce, and access to computer networks are some
scenarios that require reliable authentication. Using passwords or magnetic cards
can pose security ricks, as passwords can be found out and cards can be stolen.
Biometrics verification such as fingerprint sensing is much more reliable for authen-
tication.

2.1.5 Ratha M
Proposed an adaptive flow alignment-based dissection or binarization algorithm[5]. In
this method the placement field is calculated to acquire the crest guidelines at
each point in the image. To sector the ridges, a 16x16 booth focused on along
the ridge bearing is considered around each pixel. The prognosis sum along the
ridge bearing is calculated. The centers of the ridges appear as crowning points in
the forecast. The ridge skeleton thus obtained is smoothened by morphological
operation. Finally, intricacies are detected by locating end points and divergences in the
dispersed binary image.

2.1.6 Anil Jain

Proposed using Level 3 features for verification using 1000 ppi fingerprint scans[19]. A
three-level hierarchy can be used to describe fingerprint friction ridge details. Most
fingerprint identification systems only use Level 1 (pattern) or Level 2 (minutiae
points) features. Level 3 features includes using the pores and ridges contours which
contain important discriminatory information.

2.1.7 Mayank Vatsa

Proposed the combining of Level 1, minutiae, with Level 3, pores and ridges fea-
tures[6]. A fast and improved fingerprint verification method was presented, using a
Level 2 minutiae algorithm which first uses image transformations based on Taylor series
transformations to perform a coarse registration, and then a thin plate spline (TPS)
transformation to perform a fine record-keeping.
CHAPTER 2. LITERATURE REVIEW 7

2.1.8 Proposed System

Critically reviewing the literature concludes that most of the security in forensics, law
enforcement and security systems uses biometrics such as retina scans, facial
recognition, iris scans, fingerprints, etc. for authentication and verification. Among the
aforementioned techniques, fingerprint biometrics has been the most popular and has a
wide array of applications in a variety, if not all, disciplines of engineering.
Fingerprint biometrics are gaining attention due to the following reasons:
• Every individual has a unique fingerprint.

• Imitating more than one feature for a fingerprint is a difficult task.

• There is no complexity involved in memorizing the authentication tools such as

keys and passwords.
There have been many important works carried out and algorithms developed for
the classification, compression, and verification of fingerprints. Every algorithm has its
own set of limitations, which make it fail to properly act as a unique biometric system.
Some of the observations noted from the literature are:
• Every sensor has its own quality and image format when capturing fingerprints.
The precision of the scanner determines the quality of the fingerprint.

• When an image format is changed to a standard one for pre/post-processing of an

algorithm, the image quality is further deteriorated.
• Existing algorithms are unable to handle the low-quality images.

• Algorithms are unable to categorize low image quality fingerprints.

• Fingerprint verification needs extensive search time.

• Combining the minutiae details with the orientation angle in order to form a feature
template is a difficult task.
• Algorithms are unable to handle fingerprints with noisy backgrounds which
leads to getting inaccurate features, thus increasing the false acceptance rate FAR
or reducing the false rejection rate FRR during classification and match- ing.
• Extensive storage space needed to store the fingerprints in uncompressed for- mat.

To be able to surpass the aforementioned limitations in the research, it is proposed to

improve the following:
• Contour detector model based on feedback for classifications of fingerprints.

• Using the Hamming distance and triangular matching for fingerprint verifica- tion.
• Fingerprint verification algorithm using local structure matching.
CHAPTER 2. LITERATURE REVIEW 8

• Adaptive polyphaser sub-band decomposition structures and adaptive lifting

schemes for fingerprint image compression.
The proposed improvements are expected to return more accurate fingerprint cat-
aloguing with minimum FAR and FRR, and compressed fingerprints of a higher
image quality. An entrenched crypto-biometric verification structure for ATM bank- ing
structures has also been developed for authentication, along with a multi-modal biometric
system which combines fingerprint and iris characteristics to increase the system security
[7].
Chapter 3

Requirement Specifications

3.1 Purpose
The software requirements specified also provide the complete description of the
functions and the specified of the automated transaction system installed within a
bank. The purpose of this project is to provide secure access to the automated
transaction machines. This requirements specification document defines Exterior In-
terface, Presentation and Software System Characterizes requirements of automated
transaction system incorporated within a machine or a web portal. This document is for
the purpose of being used as an official document. The following group is also entitled
to this document including but not limited to Developers for the purpose of
maintaining the software and new releases of the firmware, Management, Testers and
Project Engineers.

3.2 Scope
The Automated Transaction Machine is designed to operate 24/7 and hence allows the
bank clients to carry out their small everyday transactions in a secure manner. All data is
held and secured at the encrypted database. The user side is connected to the client side
using secure protocols over the internet. This software facilitates the user to perform
various transactions in his account without going to bank. This software offers benefits
such cash withdrawals, balance transfers, deposits, inquiries, credit card advances and
other banking related operations for customers. It also allows the administrator to
fix the tariffs and rules as and when required. The software takes as input the
login Id and the bank account number of the user for login purposes. The outputs
then comprise of an interactive display that lets the user select the desirable function
that he wants to perform [8].

3.3 Document Overview

The document is limited to two chapters for the overview of purpose of the docu- ment.
First, we will provide the full description of the project that is dependent on
Fingerprint biometric based automated transaction machines with state of the art
security. The details provided below about the various requirements and various
hardware/software are given/defined below:

9
CHAPTER 3. REQUIREMENT SPECIFICATIONS 10

Overall Description:
The Automated transaction system incorporates numerous GUI menus as well as the
device for fingerprint sensor, to provide high safety. It delivers secure admittance to the
account of a client. The Automated transaction system must be able to provide the
following facilities to the client:
• Enter Email: A customer is required to provide a valid email address through- out
the use of his/her account.
• Change Email: A customer or user can also change the registered email from
his/her account that is also sync with the generated messages.
• Enroll Finger: A customer is also required to provide a valid fingerprint mes- sage
that is used to link as an account extension.
• Change Fingerprint: A customer can hence change the fingerprint provided
for registration from his/her account.

3.4 System features

3.4.1 Technical Field
The present invention or development of an application system as our project relates to a
Biometric fingerprint identification system using a fingerprint for identification of people
using fingerprint matching and more particularly to a fingerprint identi- fication system in
which a fingerprint identifying function is added to an operating system (”OS”) of an
electronic money transfer system, or the fingerprint is used a key for a door or the
fingerprint is encoded into a cipher key.

3.4.2 System Environment

Most use cases for the project are based on the admin user as most of functionality for the
application is on the customer/client side which needs to be monitored by a moderator
or administrator. The administrator will have access to all phases of the
application/software and will be able to manage scheduling and generation of
emails and text message at run-time on user account access. The customer/client will
only be able to confirm transactions based on his/her biometric fingerprints [9].

3.5 Basic Functionality

Following are the basic functionality of the application:
• Customer to login and view account, make transaction, update and edit dif- ferent
data/records limited to his/her account only.
• Email Scheduling and message generation on run-time.

• Withdrawal and Balance check from account.

• Biometric fingerprint reader and match from database.

CHAPTER 3. REQUIREMENT SPECIFICATIONS 11

• Data and information regarding account credentials stored in fingerprint database.

• Card Rejection on login failure or invalid account credentials.

3.6 User Characteristics.

This application/system has a very simple and easy user interface. The privilege
levels are:
• The customer will only be able to make transactions, balance transfer, account info
update and delete from his/her account only and will not be allowed
privileges except their account limitations.
• Administrator can add and modify any data and Scheduling systems.

• The administrator will be a single entity and will be added to the database.

• The moderator will be able to monitor false use of the current system and will have
privilege over ban and summation of the current system.

3.7 Performance Requirements

Since we are developing an application that is optimized in size and consumption
of resources, we should not have to worry regarding the hardware and performance
requirement. The recommended system/hardware specifications would be:
• 1 CPU with 1 GB RAM running Windows XP or greater version of Windows.

• Server to Simulate the ATM system and Database.

• Enough hardware and cloud storage space to install and backup important
project files in case of accidental lost or deletion of data.

3.8 Budget
The budget will only be required in the development phase for two things:

• The acquiring and usability of a PC.

• Fingerprint Scanner system.

3.9 Database of Bank

Database of bank means it has all records and information about the user. It consists of
users info such as name, bank id, bank accounts, account type and so on. This
technology is addition to past technology with addition of users fingerprint which
makes this technology so efficient and secure.
CHAPTER 3. REQUIREMENT SPECIFICATIONS 12

3.10 Users Fingerprint

Users fingerprint is also a part of the database. These fingerprints are required
when there is need to carry out any transaction. Every transaction is validated by
fingerprints of the corresponding user. While carrying out transactions every user
needs to SCAN his/her fingerprint on the machine.

3.10.1 Transaction Authentication

This is the step which authenticates the transaction i.e. whether valid or invalid
user is carrying out the transaction through his/her fingerprints and this step makes
transactions process secure and safe.

3.11 Functional Requirements

The designed interface and backend of the web portal will redefine the automated teller
machine having:
1. A device used to detect and store fingerprints.
2. A customer input console mainly keyboards and display that is used for interac- tion
with the customer, entering information and filling text boxes etc.

3.11.1 Facility of aborting transaction

A customer must be able to abort a transaction in progress by pressing the cancel key
instead if responding to a request from the machine.

3.11.2 Email code format

The email provided should be of proper format and contain @ symbols.

3.11.3 Facility of Email reentering

If the customers email is invalid, the customer will be required to re-enter the email
information before a specific transaction can be proceeded.

3.11.4 Denial of specific services, if Email goes wrong

If the customer is unable to successfully enter the email address, the service would be
denied for the particular users.

3.11.5 Register finger

Put your finger on top of the device and allow it to record the fingerprint.

3.11.6 Facility of reentering the finger

If the clients Fingerprint is inacceptable, the customer will be essential to re-enroll the
impression before an operation can proceed.
CHAPTER 3. REQUIREMENT SPECIFICATIONS 13

3.11.7 Denial of service, if fingerprint goes wrong

If the customer is unsuccessful in enrolling his/her fingerprint after three tries, the service
would be denied for that specific user until the timeout.

3.12 Non-Functional Requirements

There are some requirements that can said to be non-functional in nature. Specifi- cally,
in these terms the constraints the system must obey are also called the qual- ities of the
system. Other various forms of non-functional requirements are service requirements and
non-behavioral requirements.

3.12.1 Scope:
The scope of this project is to allow the user to get Secure transactions and account
access with the best scope of security transactions out there.

3.12.2 Functionality:
The system includes multiple functionality with access to Deposited Amount, With-
drawn, Transferred, Receipt is generated and User has complete access to his/her
account with some limitations.

3.12.3 Usability:
The Web portal or interface is independent of the users skills. Non-technical users are
also able to use the system with ease. The interface follows all the basic principles of
Human Computer Interaction.

3.12.4 Reliability:
The system is reliable to not make any human errors with lag and error debug com-
patibility. The system shows confirmation of reliable use and information tracking.

3.12.5 Performance:
The performance is independent of the user and completely depends on the device for
execution. The interface and software runs at optimal performance on all supported
browsers and multiple platforms.

3.12.6 Security:
The fingerprint provided by the user to the system requires complete security and all
information for these expense and purposes is secured with end-to-end encryp- tion
system. The Automated system must not store the information or data in its database, for
that reason a database is created external to the users limitations. [11].
CHAPTER 3. REQUIREMENT SPECIFICATIONS 14

3.13 Front End Description

The Front-end interface will be fully dependent on .Net framework platform, with
Html and C sharp as the programming linguistic due to these reasons:
1. Flexible interface that is non-technical and easy to use.
2. User information is secured and customizable.
3. The system operates on good performance and is highly reliable.
4. Interface is based on the principles of Human Computer Interaction and has been
made to be used at the best of its design.

3.14 Back End Description

In the process of database creation and development we are using MySQL Server- side
database due to the following reasons:
1. Inherent support and complete compatibility with .NET platform.
2. Elastic, Accessible and vigorous database architecture.
3. This system is preferred and used by innovative leading companies worldwide.
4. Easy to manage and secure data protection.
CHAPTER 3. REQUIREMENT SPECIFICATIONS 15

3.15 Login Use Case I

Figure 3.1: Use case 1

Table 3.1: Use case 1

CHAPTER 3. REQUIREMENT SPECIFICATIONS 16

3.16 Sign Up Use Case II

Figure 3.2: Use Case 2

Table 3.2: Use case 2

CHAPTER 3. REQUIREMENT SPECIFICATIONS 17

3.17 Authentication Use Case III

Figure 3.3: Use Case 3

Table 3.3: Use case 3

Table 3.4: Use case 4

CHAPTER 3. REQUIREMENT SPECIFICATIONS 18

Table 3.5: Use case 5

Chapter 4

Design

4.1 System Architecture

The system has many basic functionalities of a traditional Automated Transaction System
but does not require the Card or PIN code like in the traditional systems. It also has a
draw back that if the current designed prototype system does not have a valid fingerprint
identification due to any number of cases it can result in not being able to log into the
system.

4.1.1 Design Constraints

The specific constraints in terms of design can be specified as internet connection
is an important constraint in running the basic web portal needed to execute the
system capabilities. As all systems need data from the database, so in terms an
internet connection is necessary. Database is shared between the systems and secure
encryption on the user end and secure decryption on the server side is put into
action. The web portal and the end system will be constrained by the capacity of internet
and database used. Moreover, no specified device is ready for these systems as all
devices or platform in support of the latest system can execute the browser
capabilities to run this application. The design also functions for a module that
matches fingerprints.

4.1.2 Sequence Diagram

Sequence diagram is used to show interaction between different object of the system.
Web Sequence Diagram is tool used to draw the sequence diagram.

4.1.3 Login Sequence Diagram

The following is the sequence diagram of the Login into an Application. It tell the
sequence of how to login into an Application.

4.1.4 Sign Up Sequence Diagram

The following is the sequence diagram of the Login into an Application. It tell the
sequence of how to login into an Application.

19
CHAPTER 4. DESIGN 20

4.2 Software Interface

The software being operated on the fingerprint scanner has to provide:

• The software that is being used by multiple banks.

• Networking software used to correspond with the device.

The detailed specification of the software interface is in detail not needed to be

specified in this document.

4.3 Communication Interface

As long as the performance requirement is specified, there is no need to restrict the
fingerprint scanner to operate on a single or specified network protocol.

4.4 Performance Requirements

4.4.1 Performance prerequisite 1
In case of failure the error message should be displayed for at least 30 seconds.

4.4.2 Performance prerequisite 2

In the case/scenario that there is no response from server due to invalid credentials or no
record found in database after/within 2 minutes the card/fingerprint is disallowed with an
error message.

4.4.3 Performance prerequisite 3

Each system or bank may be dispensation transactions from several Fingerprint
based scanner on the similar occasion [12].

4.5 Other Requirements

The Biometric Fingerprint based transaction system scanner must be able to use
several data formats according to some of the data formats that are provided by
the databases of different systems or banks. A common transaction should have all the
properties of a Database transaction or data retrieval (Atomicity, Consistency, Isolation,
Durability) [13].
CHAPTER 4. DESIGN 21

Figure 4.1: Activity Diagram 1

This is the activity diagram of the transaction portal, it tells that how the
activities will be carried out. The whole activity of the application is summarized in the
following diagram.
CHAPTER 4. DESIGN 22

Figure 4.2: Sequence Diagram 2

The following is the sequence diagram of the Sign up information. As you can see
from the figure above, the user interacts with three basic entities of the trans- action
system. The most important Sign up information provided to the system is enrollement
of users fingerprint, when the fingerprint and email are verified then the information is
generated and account is successfully created.

Figure 4.3: Sequence Diagram 3

The following is the sequence diagram of the Log In Screen. As you can see from the
figure above, the user interacts with three basic entities of the transaction sys- tem. The
most important Login information provided to the system is identification of fingerprint,
when the fingerprint and email are verified then the information is generated and
the user is Logged In.
CHAPTER 4. DESIGN 23

Figure 4.4: Sequence Diagram 4

The following is the sequence diagram of the Deposited Amount. As you can see
from the figure above, the user interacts with three basic entities of the transaction
system. When the user is successfully Logged In to his/her account, the user can
perform a deposit amount function. However, If the user enters a negative amount is
redirected to the same page. An email is generated if this process is successful.

Figure 4.5: Sequence Diagram 5

The following is the sequence diagram of the With Drawn Amount. As you
can see from the figure above, the user interacts with three basic entities of the
transaction system. When the user is successfully Logged In to his/her account, the user
can perform a withdraw amount function. Moreover, If user enters the amount which is
not present in his/her account then the user is redirected to the same page. An email is
generated when the transaction is successful.
CHAPTER 4. DESIGN 24

Figure 4.6: Sequence Diagram 6

The following is the sequence diagram of the Transfer Amount. When the user is
successfully Logged In to his/her account, the user can perform a transfer amount
function, in which the user has to provide correct account information and amount. An
email is generated when the amount transfer is successful.
Chapter 5

System Implementation

5.1 System Architecture

The existing system provides many functionalities and is an improvisation over the
traditional Automated Transaction Machines, but it also features a draw back as no
Card or Pin is required, if the user is unable to provide the biometric fingerprint due to a
number of reasons, he/she will not be able to login to this system. So, it is imperative
that some changes can still be made into the system.

5.1.1 Server-side system

This application can be installed/run on all supported browsers and a number of
different platform that support similar framework applications. Only the user is able to
use this application on this stage. The user is enabled to log into his/her account and alter
the information restricted to their use only. The user can also perform all the basic
transactions inside the system. Their account activity is also listed, and all information is
secured through encryption. Moreover, an online receipt will also be generated
depending on any activity that the user performs in the system.

5.1.2 Web Portal

Web portal will be on web server for user access purpose only. The user can
use this application to add, delete, update and view information. User can also use this
application to edit his account in terms of amount and transactions.

5.2 System Internal Component

5.2.1 Sign Up
The web portal for fingerprint-based ATM system requires a sign-up process to
register an account into the system database. Once the user is registered into the system,
he/she can access all the features of the application. The user has to add their email
address, name, basic information and fingerprint. To activate his/her account the
verification of his fingerprint and correct email is required.

25
CHAPTER 5. SYSTEM IMPLEMENTATION 26

5.2.2 Login
For login purposes into the system, the user will provide a valid email and fingerprint that
is already registered into the system or saved in the system database. Hence, if the user is
not logged into the system due to security reasons an error message is displayed. This
method is efficient for fast access and security in a manner that the user cannot access
someone elses account.

5.2.3 Deposit
This system functionality allows the user to deposit an amount into their account once
the user is logged into the system and database. The requirements for a
successful deposit is that the user must successfully be logged into the system and he/she
should not enter a negative amount that isnt defined in system parameters. Once the user
deposits an amount into the account an email is generated on their address.

5.2.4 Withdraw
The use of this application can also withdraw an amount from their account. There are
two basic requirements for this function to take place. The user must already be
logged into the system and connected to the database. The user must enter a valid
amount for withdrawal that is already present in his/her account. Once the user
successfully withdraws an amount, a mail is generated to their email address.

5.2.5 Transfer
The user is also entitled to another functionality. The user can transfer an amount from
his/her account to another account, provided that there is an account number for the
account being transferred to and the user should be logged into the system. If the amount
ready for transfer is not present in primary account, an error message is generated,
logging the user out of the system. On the case of successful transfer an email is
generated entitled of the amount that was transferred.

5.2.6 Encryption-Decryption
The main functionality of the system that makes it so secure is the end-to-end 3D mapped
encryption used for securing the system. All the data entered into the system at
any point including but not limited to passwords, emails, fingerprints, personal info,
account info etc. are all encrypted at one point before sending it to the database system
and then decrypted at that point.

5.2.7 Email Generation

The one functionality of the system is that it can generate a conformation email and sends
an email on users email account on every transaction he/she perform. This
functionality makes the system more secure and helpful for the user that he/she can know
his/her transactions record.
CHAPTER 5. SYSTEM IMPLEMENTATION 27

5.3 Tools and Technology

There are many techniques which are being used in fingerprint based Automated
Transaction system, some of which are being used here below.

5.3.1 .Net
.Net programming language is used to create the back-end of the system responsible for
all the functionality inside the system.

5.3.2 Visual Studio

Visual Studio is a tool developed by Microsoft to develop web applications and an
environment of Visual Editor and Code Editor. It was used in the development of Web
portal for the system interface and functionalities.

5.3.3 Web Tools

HTML, CSS and Bootstrap are the web tools used to create the front-end design of the
system which makes the system more user friendly and reliable for the user.

5.3.4 MySQL
MYSQL is a relational database management system developed by Oracle and is
used to store and retrieve data placed in the Hosted Internet Server. It is the also the
backend of the system used to create a database responsible for handling all the data sync
and storage inside the system.

5.4 Development Environment/Languages Used

The main development language used is .net framework which enabled us to make the
whole backend of the Fingerprint (Biometric) Based Automated Transaction system.
The system is also encrypted and decrypted using 3D mapped technology. Visual Studio
is a tool and .NET is the language used in making of a Web Portal. SQL was used in the
creation of database system for the creation, input and retrieval of data inside the system.

5.5 Framework Access Security

The security for framework access is dependent on the security used on the backend of
the system which is proceeded with encryption modules on the user end and
decryption module on server/database end.

5.6 Methodology
This application is developed by using Incremental Model, because requirements
will be change according to the user suggestions. The system includes multiple
CHAPTER 5. SYSTEM IMPLEMENTATION 28

functionality with complete access of the basic transaction functions. We have used an
improvisational method for system creation and implementation. Development of this
application was done in different phases:

5.6.1 Phase 1
In this phase the fingerprint identification was done using unique fingerprint match- ing
algorithms with the help of Secugen biometric identification device with a success
matching rate above 90 percent.

5.6.2 Phase 2
In this phase Web Portal was developed, for the user access purpose only, through web
portal the user will be able to create account, login into his/her account, and will be able
to perform certain functions like, deposit amount, withdraw amount and transfer
amount.

5.6.3 Phase 3
In this phase the encryption-decryption modules were developed in accordance with the
database on server side and web portal on the user side. The email module was integrated
with the main system for the purposes of email generation etc. The user can also update
his/her account after all the modules are developed in this phase.

5.6.4 Phase 4
In this phase an interactive and proper interface of the application was designed.
And all the components of the system were integrated with each other. In this phase
system was ready for deployment and testing.
Chapter 6

System Testing and Evaluation

System testing of software or hardware is testing conducted on a complete, integrated

system to evaluate the systems compliance with its specified requirements. Software
testing technique is the process of checking and evaluating whether the system is
performing the tasks it was supposed to do or not. The following are some of the
software testing techniques.:
• Usability Testing.
• Interface Testing.
• Performance Testing.
• Compatibility Testing.

6.1 Graphical User Interface Testing

Our Web portal redefines simplicity in a way that the user can access his account and
credentials, including creating a new account through just the introductory page of
our portal. Everything is defined on the portal to help the user and guide him through the
process. Even the users with no knowledge of the system or skills required to log into
their accounts are guided through the process and are able to log in.

6.2 Usability Testing

Our application and system upon which it is being carried out, requires no technical
experience to use. The system we built has a Web portal through which the user
can access his account, this only requires physical implementation by which the user
implements his fingerprint on the system and can hence log into the system to access all
the functionalities of his account.

6.3 Software Performance Testing

Our Fingerprint based ATM system requires no exceptional hardware capabilities, the
system has minimal response time, low system hardware utilization which ac-
counts for great overall performance in the system. The system is easy to maintain

29
CHAPTER 6. SYSTEM TESTING AND EVALUATION 30

and requires no external help in maintaining. In the unfortunate case of system fail- ure,
the recoverability of the system requires it to be restored to the default/original state in
which the system was created. The system is also reliable because it re- sponds to
user in similar way as it was designed. The system usability can be defined in an easy
was as descriptive definition of everything is provided. Our system secu- rity is the main
measure of its success as the system is secure than the traditional systems and requires
authentication of physical fingerprint and email. Data integrity is authenticated and
encrypted using 3D map, so data cannot be manipulated in any way by the hackers
or data integrity evaluators.

6.4 Compatibility Testing

The basic prototype of our system operates in such a way that the web portal requires
minimal hardware capabilities and supports all the latest browsers for loading the web
portal including but not limited to, Firefox, Google Chrome, Internet Explorer, Safari,
Opera Etc. The portal is compatible to run on all devices that include the browser
and internet compatibility with a fingerprint device attached to detect the physical print
of the User. The platform version is 1.0 and requires devices specification of at
least a biometric fingerprint detection device and a core Atom or later compatibility
of processor support with latest browser integration support system.

6.5 Exception Handling

• Exception handling is integrated in the following modules of the application.
• Login: Imperative to sign up in case of registration.
• Sign In: Requires input within defined parameters.
• Fingerprint: Required to match both the input or exceptions are generated in the
system.
• Account Info: Appropriate account info no provided will generate an error
message within the system.

6.6 Load Testing

The load testing was performed on few platforms and devices but no such behavior in
time, requirement gathering, or load balancing was detected that we could perform a load
testing variation on the system. The system however showed nominal changes in
performance (hardly noticeable) and performed with no errors and lag (cause for
debugging) on any particular system.

6.7 Installation Testing

Since the prototype of our main system is operating on web-based applications, it
requires no installation on multiple systems. Moreover, depending on the Web
CHAPTER 6. SYSTEM TESTING AND EVALUATION 31

portal it can hence be installed/operated on different platforms each of which has an

internet functionality and browser or portal support. Installing the system or in this case
executing it on a platform only requires internet and browser support on any compatible
device with input modules to input information.

6.8 Testcases

Table 6.1: Test case 1 (sign up I)

Table 6.2: Test case 2 (sign up II)

Table 6.3: Test case 3 (Log in I)

Table 6.4: Test case 4 (Log in II)

CHAPTER 6. SYSTEM TESTING AND EVALUATION 32

Table 6.5: Test case 5 (Deposit I)

Table 6.6: Test case 6 (Deposit II)

Table 6.7: Test case 7 (With-Draw I)

Table 6.8: Test case 8 (With-Draw II)

CHAPTER 6. SYSTEM TESTING AND EVALUATION 33

Table 6.9: Test case 9 (Transfer I)

Table 6.10: Test case 10 (Transfer II)

6.9 Testing and Results

The test results indicate that our system is efficient in running, accuracy is mostly
dependent on the user. Hence the results can be expressed and represented in this way:

6.9.1 Performance Testing:

Technology stack was chosen which itself has proven capabilities so there were
no worries about poor performance as user load increases. .Net framework runs all the
latest sites with support for all media and Brower on multiple platformed devices.

6.9.2 Security Testing:

Security testing was performed at the end of implementation, as the target audience of the
system enables only register users to Login and use the system. We have used
160-bit encryption for security testing and has so far proved to be successful. There are
also other security measures installed for security enhancement inside the system which
prevents unauthorized user from accessing the system and is an intergral part of security
testing.

6.9.3 Non-Functional Testing:

As per the requirements for system performance, a few of the basic non-functional testing
characteristics were tested which are mentioned as follows:
• Reliability Testing.
CHAPTER 6. SYSTEM TESTING AND EVALUATION 34

• Maintainability Testing.

• Performance Testing.

• Exception Handling.

• Efficicency Testing.

• Load Testing.
Chapter 7
Conclusion

• Fingerprint Based Automated Transaction system is developed for users who have
security issues regarding the traditional ATM system.
• While working on the project, we learnt the practicality and aspects of Sys-
tem Development Life Cycle including requirement gathering and analysis,
designing, implementation and testing.

• This project has also used extensive coding in (.net) framework which has
helped us in making a single system composed of different modules and func-
tions/components that are integrated with each other.

• Fingerprint Based (Biometric) system has helped secure the traditional system by
decreasing the margin for stolen identity and data integrity manipulation. It has
helped us in improving programming and software management skills, it has also
helped us in making a secure and reliable system for users.
• The features of fingerprint image detection require a secure and stable con-
nection to the central database from the user. The encryption used in this
system is 3D mapped which ensures that all the password, Identities and fin-
gerprint authentication are secure and protected. Hence no data manipulation or
third-party handling is used.

• Future work will also focus on stabilizing the retinal features for protection
as an enhancement to biometric verification technologies. This will also help in
setting up a matching dictionary as to narrow the load of matching similar imagery
in extensively large databases.

35
Bibliography

[1] Fingerprint Authentication for ATM”, Slideshare.net, 2017. [Online]. Avail-

able: https://www.slideshare.net/ParasGarg14/fingerprint-authentication-for- atm-
68167292. [Accessed: 05- Jan- 2017].
[2] Efficient Thinning Algorithms Design and Implementation of an Efficient Thin- ning
Algorithms Published by Kluwer Academic Publishers, 20 Das

[3] Fingerprint Image Enhancement: Algorithm and Performance Evaluation. Au- thor
Hong, L., Wan, Y. and Jain, A.
[4] Avinash Shinde1, Rounak Sathe1, Prakash Sutar1, Prof.R.Sadakale2.

[5] Bank information security news, training, education - BankInfoSecurity”, Bank-

infosecurity.com, 2017. [Online]. Available: http://www.bankinfosecurity.com/.
[Accessed: 04- Jan- 2017].

[6] UKEssays. (2018). Fingerprint based identification. [online] Available at:

https://www.ukessays.com/essays/information-systems/fingerprint-based-
identification.php [Accessed 04 Jan. 2018].

[7] . Iqbal, A., Smith, K. and Pridham, G. (2018). FINGERPRINT

based ATM security System — Rectifier — Transformer. [online] Scribd.
Available at: https://www.scribd.com/document/131602953/FINGERPRINT- based-
ATM-security-System [Accessed 04 Jan. 2018].

[8] . MTech Projects. (2018). Fingerprint Liveness Detection From Single Im- age
Using Low-Level Features and Shape Analysis. [online] Available at:
https://www.mtechprojects.com/electron-device-letters/75912-fingerprint- liveness-
detection-from-single-image-using-low-level-features-and-shape- analysis.html
[Accessed 04 Jan. 2018].
[9] Ijeijournal.com. (2018). Loading. [online] Available at:
http://www.ijeijournal.com/papers/Vol.3-Iss.11/D030112228.pdf [Accessed
04 Jan. 2018].

[10] . My Circuits 9. (2018). Fingerprint Based ATM Access System Project Ab-
stract. [online] Available at: http://www.mycircuits9.com/2015/03/fingerprint-
based-atm-access-system.html [Accessed 04 Jan. 2018].
[11] . Lin Hong, Wan Yifei, Anil Jain. Fingerprint image enhancement: algorithm and
performance evaluation[J]. IEEE Transactions on Pattern Analysis and Ma- chine
intelligence. 1998, 20(8): 777-789.

36
BIBLIOGRAPHY 37

[12] . ESaatci, V Tavsanogh. Fingerprint image enhancement using CNN gabor-Cpe

filter[C]. Proceedings of the 7th IEEE International Workshop on Cellular Neural
Networks and their Applications 2002: 377-382.
[13] . Barth, H. Schaeper, C. Schmidla, T. Nordmann, H. Kiel, M. van der Broeck, H.
Yurdagel, Y. Wieczorek, C. Hecht, F. Sauer, D.U., Development of a universal
adaptive battery charger as an educational project, Power Electronics Specialists
Conference, 2008. PESC 2008. IEEE, 15-19 June 2008, Pg 1839 1845.
[14] Weidong Xiao, William G. Dunford, Patrick r. Palmer and Antoine Capel,
Regulation of Photovoltaic Voltage, IEEE Trans. Industrial Electronics, vol. 54 no.3,
pp. 1365-1373, June 2007.
[15] Robert Hastings, Ridge Enhancement in Fingerprint Images Using Oriented
Diffusion, IEEE Computer Society on Digital Image Computing Techniques and
Applications, pp. 245-252, (2007).
[16] Sichuan University, ”Adaptive pore model”, www.researchgate.net/, 2018. [On-
line]. Available: https://www.researchgate.net/

[17] World Academy Of Science, Engineering And Technology and International

Journal Of Computer, Electrical, Automation, Control And Information Engi-
neering Vol:1, No:3, 2007, ”An Approach to Image Extraction and Accurate Skin
Detection from Web Pages”, 2018.
[18] I. Walsh, ”The Growing Role of Digital Identity in eCom-
merce”, Blog.eschergroup.com, 2018. [Online]. Available:
https://blog.eschergroup.com/the-growing-role-of-digital-identity-in-
ecommerce. [Accessed: 03- May- 2018].

[19] Waset.org, 2018. [Online]. Available: https://waset.org/publications/14355/fingerprint-

verification-system-using-minutiae-extraction-technique. [Accessed: 03- May-
2018].

[20] ”Journal of Information Processing Systems”, 2018. [Online]. Available:

https://pdfs.semanticscholar.org/5095/8208cdbeac5d438267a2f20f07663acfaf52.pdf.
[Accessed: 03- May- 2018].