Biometric Fingerprint Based ATM Transaction System
Biometric Fingerprint Based ATM Transaction System
Biometric Fingerprint Based ATM Transaction System
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 ...:
.....................................................................................
.....................................................................................
.....................................................................................
..................................................................................... May
27, 2018
i
Abstract
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
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
7 Conclusion 35
List of Figures
vii
List of Tables
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
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].
• Collect and understand system requirements based on data provided/and gath- ered.
• Database development.
1.6 Testing
• Unit testing.
• System Testing.
• Final Documentation based as a user manual for high protection ATM systems with
fingerprint identification and user manual.
• 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.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.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.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.
• 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.
• Using the Hamming distance and triangular matching for fingerprint verifica- tion.
• Fingerprint verification algorithm using local structure matching.
CHAPTER 2. LITERATURE REVIEW 8
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].
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.
• 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.
• 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:
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
Design
19
CHAPTER 4. DESIGN 20
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
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.
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
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.
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
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
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.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.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.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
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.8 Testcases
• 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
[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.
[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