Fingerprint Based ATM System
Fingerprint Based ATM System
Fingerprint Based ATM System
Prepared by :
G Shalom Shreyan
Aryan Raj Shaw
Divyanshi Yadav
Harsh Pandey
Karunesh Bamanjogi
Table of Contents
1. Introduction
1.1 Purpose & Scope
1.2 Target Audience
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
1.5 Overview
3. UML Diagrams
3.1 Use case diagram
3.2 Class Diagram
3.3 Sequence Diagram
3.4 Activity Diagram
3.5 Communication Diagram
Introduction
This document provides a description of the technical design for an Fingerprint based
ATM system. This document’s primary purpose is to describe the technical vision for how
business requirements will be realized. This document provides an architectural
overview of the system to depict different aspects of the system. This document also
functions as a foundational reference point for developers.
● Development Team
● IT Management
● Support Staff
It is assumed that the reader has a technical background in software design and development.
1.4 References
1. https://lucid.app/documents#/
2. https://docs.google.com/document/d/1gQRBjxOc8DICDJOIeQMjG3VaVLc-pFmbSMu
ExT4SFV8/edit
1.5 Overview
This software design document gives details about the various hardware and software
interface requirements. The remainder of this document is divided into three sections that
provide a full description of the project for the bank’s ATM with fingerprint security.
2.1 Description
The DFD of a Fingerprint based ATM system depicts how data enters and leaves the
system, what changes the information, and where data is stored, with representation of
the processes in the information system from the viewpoint of data.
This DFD lets you visualize how the ATM system will operate, what the system
accomplishes and how it will be implemented. It may be used as a communication tool
between a system analyst and any person redesigning a system.
The data flow diagram for the fingerprint based ATM system consists of Three levels.
These levels are Context level, Level 0 and Level 1.
2.2 Components
1. Circle: A circle shows a process that transforms data inputs into data outputs.
2. Data Flow: A curved line shows the flow of data into or out of a process or data
store.
3. Data Store: A set of parallel lines shows a place for the collection of data items. A
data store indicates that the data is stored which can be used at a later stage or by
the other processes in a different order. The data store can have an element or
group of elements.
It is the very first level of a data flow diagram. it is supposed to represent the system as a
single process with its relationship to all the external entities, in simpler words we can say
that it identifies all the sources and the sinks for a system.
The processes listed in the context level are then further divided into subprocesses in the
next level.The DFD of this level is shown below:
2.4 Level 0 DFD:
At this level, only the interacting inputs and outputs with a system are described.This level
helps us to identify all the manageable subprocesses in the system. The other level contains
more information about these subprocesses. The DFD of this level is shown below:
2.5 Level 1-n DFD:
In this system we only require three levels, so this is the last level of the DFD. This level
provides more detailed information about the processes involved . It identifies the actual data
flow and the data stores of the ATM system. The DFD of this level is shown below:
2.5 Process Decomposition:
It depicts a top-down development of a data flow diagram starting with the system inputs and
the system outputs.lt allows us to organize your overall DFD in a series of levels so that each
level provides successively more detail about a portion of the level above it.
Decomposing the process will help in initializing the sub diagram, the objects from the
upper-level to link to the sub-process. It's easier to automatically retrieve global objects, such
as external entities or data stores and create object shortcuts, if need be.
Unified Modeling Language Diagram
The use case diagram graphically demonstrates the different ways that a user might
interact with the system.It helps in describing the high-level functions and scope of a
system.The use cases and actors in use-case diagram depicts what the system does
and how the actors use it. It illustrates and defines the context and requirements of
either an entire system or the important parts of the Fingerprint based ATM system.
3.2 Class Diagram
A class diagram models the static view of a system. It comprises the classes, interfaces,
and collaborations of a system; and the relationships between them.Here in this class
diagram we are showing the different classes consisting of different components of our
system.
3.3 Sequence Diagram
The Sequence Diagrams for Fingerprint based ATM show cash withdrawal,
money transfer, view account details and tutorial sequences. All these sequences can
be demonstrated in a single sequence diagram but that will get very complex with loops
and branches, which is one disadvantage of sequence diagram hence it is preferred to
break it into 4 different sequences for clear understanding.
3.4 Activity Diagram