(PDF) Distributed ATM System

Running head: THE DISTRIBUTED ATM SYSTEM
The Distributed ATM System
Name of the Student:
Name of the University:
Author note:

1
THE DISTRIBUTED ATM SYSTEM
Table of Contents
The ATM System Description.........................................................................................................2
Functional Requirements.............................................................................................................2
Non-Functional Requirements.....................................................................................................3
Overall structure and the Distributed System description...............................................................3
Tier Categorization..........................................................................................................................4
Basic Tier Implementation..........................................................................................................4
Tier 2............................................................................................................................................5
Diagrammatic Representations........................................................................................................5
UML Class Diagram....................................................................................................................6
Use Case Diagram.......................................................................................................................7
Activity Diagram.........................................................................................................................8
Sequence Diagram.......................................................................................................................9
Interface Design.........................................................................................................................10

2
THE DISTRIBUTED ATM SYSTEM
The ATM System Description
The ATM system is being designed keeping in mind the distributed functioning system of
any Banking organization. The ATMs or the Automated Teller Machines are the specialized
computerized systems or machines that allow the customers to access their bank accounts to
retrieve or deposit monetary amount into the same.
Functional Requirements
The functional requirements for the system are:
1. Card Login with valid PIN: The ATM system must allow users to insert their cards into
the machine and then login to their accounts using a valid PIN.
2. Language Selection: The system must allow the users to select their preferable language
form a list of the common languages from that area.
3. Money Withdrawal: The user must be able to insert the amount, which he wishes to
withdraw from his or her respective bank account.
4. Amount Validation: The system must ensure that the user has enough amount to make
their demanded transactions from the concerned account. In addition, the system must
also ensure that the denominations entered are valid and the ATM has the demands in its
stock.
5. Termination: The system must logout of the bank account immediately after one
transaction is made or even if the transaction is unsuccessful. Time-out terminations shall
also be considered.
6. Change PIN: The users should be able to change their existing PIN password.

3
THE DISTRIBUTED ATM SYSTEM
7. Receipt Generation: The system must compel the machine to print out the details of their
respective transactions in printed [1].
Non-Functional Requirements
The non-functional requirements for the system are:
1. Security: The system must ensure that all logins, queries and transactions take place over
a secured environment and network inside the system and the overall architecture
framework [2].
2. Robust: The banking system as a whole should not crash due to the failure of one client
node at any of the corresponding ATMs [3].
Overall structure and the Distributed System description
To comply by each functional and non-functional requirements, the overall structure of a
general ATM to be designed would include:
 Card reader
 Keypad
 Speaker
 Display screen
 Receipt printer
 Cash dispenser
Being an important part of the banking system, the system must have the abilities to
perform in a complex distributed network. It is possible that the user, a joint nominee and or the
bank officials, at the same point of time, are accessing a particular account. This gives rise to the

4
THE DISTRIBUTED ATM SYSTEM
concept to resource and process sharing over the ATM network. The banking system is
considered as the server that controls every transaction and account queries. Each ATM machine
that is being used by a customer can be considered as a client. The client punches the card and
enters the pin. This pin is passed on to the bank server where it matches the PIN number with the
card details by reading from the database and reverts back to the ATM display unit with a failure
or a success status. On successful login, the client’s claim to withdraw money is sent back to the
main server that processes the information and sends the amount to the host account. This host
account is the local account for the Host computer or server that acts as the intermediate between
the client and the bank’s main server. This host traces the amount and then provides the required
sum to the client. It must be noted that every query that is issued by the user to the system will be
first stored in the host server and then sent to the Bank server where this data will be processed
and sent back to the host and then to the display screen [4].
Concurrency may occur when the user is trying to access the same account from a web
source and the ATM at the same time. In such cases, the bank server has special Operating
System services to update the database in real time. Any changes made to the user’s account will
be reverted to the host server of the ATM if a session is in use. The bank as the server, may
choose to halt any transaction, and this shall be simultaneously affecting the ongoing transaction,
if it is not completed.
Tier Categorization
Basic Tier Implementation
The functional and some necessary non-functional units for the system that are to be
implemented here are:

5
THE DISTRIBUTED ATM SYSTEM
 Card validation
 PIN Validation
 Input / Output integration
 Amount withdrawal
 PIN changing
 Receipt printing
 Security: Encrypt all data that is sent out from the host server to the main bank server
node and vice versa. The keys for encryption must be sessional and be destroyed as soon
as a transaction is halted.
Tier 2
 Language selection: The interface is needed to be written in multiple languages and thse
options shall be offered to the user.
 Concurrency: Each client node will act as distinct objects that is trying to access the
same or different methods within their respective account class objects from the server.
 Robust: Keeping in mind that the same client end system will be live all across, the
system as whole shall not crash if one client node fails or halts. If one system is
compromised due to security reasons, it is only that particular host server that is affected
and not the entire system. This makes the faults more scalable and it is easy to recover
from the same [5].
 Enhance Security: Use 2nd-level biometric login [6].
Diagrammatic Representations

6
THE DISTRIBUTED ATM SYSTEM
The UML, behavioral and interface diagrams below provide a strong overview of the
system.
UML Class Diagram

7
THE DISTRIBUTED ATM SYSTEM

8
THE DISTRIBUTED ATM SYSTEM
Use Case Diagram

9
THE DISTRIBUTED ATM SYSTEM
Activity Diagram

10
THE DISTRIBUTED ATM SYSTEM
Sequence Diagram

11
THE DISTRIBUTED ATM SYSTEM
Interface Design

12
THE DISTRIBUTED ATM SYSTEM

13
THE DISTRIBUTED ATM SYSTEM

14
THE DISTRIBUTED ATM SYSTEM
References
[1] Wolf, Marilyn. Computers as components: principles of embedded computing system design.
Elsevier, 2012.
[6] Lavanya, K., and C. Naga Raju. "A comparative study on ATM Security with multimodal
biometric system." International Journal of Computer Science & Engineering Technology 4, no.
06 (2013).
[2] Padmapriya, V., and S. Prakasam. "Enhancing ATM security using fingerprint and GSM
technology." International Journal of Computer Applications 80, no. 16 (2013).
[3] Gluchshenko, Olga, and Peter Foerster. "Performance based approach to investigate
resilience and robustness of an ATM System." In 10th USA/Europe Air Traffic Management
Research and Development Seminar, pp. 10-13. 2013.
[5] Gluchshenko, Olga. "Definitions of disturbance, resilience and robustness in ATM context."
(2012).
[4] Oluwatosin, Haroon Shakirat. "Client-server model." IOSRJ Comput. Eng 16, no. 1 (2014):
2278-8727.