Object Modelling and Design: A Detailed Report on ATM System

This report provides a comprehensive overview of the object modelling and design of an Automated Teller Machine (ATM) system. It begins by outlining the functional and non-functional requirements of the ATM, including card reading, PIN verification, transaction options, cash dispensing, and security measures. The report then presents a use case diagram illustrating the interactions between the customer and the ATM system, along with detailed descriptions of the use cases. Furthermore, a UML domain model class diagram is included to represent the system's structure and relationships. The design activities of the Software Development Life Cycle (SDLC) are discussed, focusing on planning, testing, deployment, maintenance, implementation, and documentation. The report also addresses the design environment, application components (key-switch, card reader, screen, keypad), user interfaces, database integration, and software methods involved in the ATM system's development. The document concludes by emphasizing the importance of a well-designed ATM system for efficient and secure financial transactions.

Running head: OBJECT MODELLING
Object Modelling
Name of Student-
Name of University-
Author’s Note-

1OBJECT MODELLING
Introduction
Automated Teller Machines are considered to be an important part of our life that helps
in money transaction from the banks avoiding the huge rush in banks (Hossian, Nawaz &
Grihan, 2013). An ATM is basically an electronic machine of telecommunication that helps the
customers involved in financial institutions so that they can perform transactions related to
finance, including cash withdrawal, deposits that are made through ATMs, transfer of funds,
obtaining the information of account, and many more at any time the user wants to. For the
transactions that are done through ATM, the user do not have to visit the banks not have to do
any interaction with the bank staff. ATMs are now considered to be a part of everyday life
(Duvey, Goyal & Hemrajani, 2013). An ATM is also known as electronic outlet of banks that
allows the customers to do basic transactions without the help of any bank branch officers or
staffs. The customers can do their transactions only with the help of the card and the secret pin
code that is provided to them. The concept of ATM was first in the year 1967 in London and
then spread throughout the globe (Kopardekar, 2014). ATM provides us with money when there
is a need without help of any third person.
This report consists of different functional as well as non-functional requirements of the
ATM machine. Details of the functional and non-functional units are described clearly. A use
case diagram is also provided along with a UML model diagram that can be stated for the
function of ATM. This report also provides with the activity of SDLC.

2OBJECT MODELLING
1. Functional and non-functional requirements
When a new system is implemented, the main goal of the system is to provide with all the
requirements that are demanded by the users. All the expectations of the system are to fulfilled
by the system that is designed. The system of the ATM that is designed is also expected to fulfill
the demands of the customers (Duvey, Goyal & Hemrajani, 2013). All the details to design a
ATM machine is known as the requirement of the machine and the requirements of the machines
should be designed in detailed, with relevant parts and the system should also be quantifiable.
There are mostly two types of requirements while designing a system, mostly functional
requirements and non-functional requirements.
To develop the ATM system of Collin bank, there are non-functional requirements that
are needed to perform all the tasks in the ATM. The functional requirements and the non-
functional requirements that are involved in making the Collin’s ATM are as follows:
The functional requirements for the ATM are:
 The first requirement of the ATM machine is the ATM card reader of the system. The
ATM card reader reads the card number of the card.
 The system is on the idle state is no such operations are performed on the system.
 The next function of the ATM system is that it prompts the user on the screen to enter the
ATM pin, after the detection of the card by the card reader.
 After entering the pin, the system shows a display with many options. The options are to
withdraw, money transfer, change pin, balance enquiry, deposit, mini statements. The
option on the screen actually varies from bank to bank (Sabatini, Gardi & Richardson,
2014).

3OBJECT MODELLING
 There is also a function of cash dispenser that is to be in idle state to deposit the cash.
 The system of ATM has a function for generating the recorded printed slip for the
transaction that occurs to the user (Buede & Miller, 2016). The system asks the user if the
user wants to generate a printed slip when transaction is completed.
 After the completion of the transaction, the card gets automatically rejected.
 For depositing the money, there should be a cash dispenser and the cash dispenser should
be aware of the amount of money that the user is depositing.
 The system of ATM also has a keypad function that is used to take input by the user.
 The script that is generated determines if there is availability of ink and paper so that the
printing process is done successfully.
 For transferring money from one bank to another, the account number of the receiver
should be available with the user.
 There are maximum of three attempts that the user can perform for particular transaction.
 The ATM transaction is not possible if the user is not an authenticated one and enter the
wrong pin more than three times.
Non-functional requirements of Collin’s ATM Bank:
 The ATM system of Collin consists of card reader, display, printer, cash dispenser, and
keypad.
 There is a keypad on the machine of the system that consists of 10 buttons that are
labeled with a number from 0 to 9 and there more buttons showing “OK”, “ENTER”,
“CANCEL”, “CLEAR”.
 The card reader should not take more than 5 sec to read the card.

4OBJECT MODELLING
 Security of the ATM falls under the non-functional requirement of the system. There
should be security for the system.
 There are only three attempts available with the user to give the pin correctly.
 The slip printer of the system should be replaced when finished.
 The cash dispenser should be refilled with cash when needed.
 There should be a restart option r every ATM machine.
2. Use case diagram
Figure 1: Use Case diagram
(Source: Created by author)

5OBJECT MODELLING
Description of Use Case Model
The Collin’s ATM bank will allow their clients to withdraw money, transfer money from
one account to another, and also helps in depositing money in their bank account (Ramasamy et
al., 2013). The use case stated here gives the details of ATM system of the for a customer
withdrawing money from the ATM.
Actors:
Customer from the banks
The banking system has automatic system
Trigger:
Only one user can withdraw money from one account at a time.
Preconditions:
The system of the ATM of Collin is operational.
A card should be present with the user to have a successful transaction.
Post Conditions:
A receipt is generated by the ATM of Collin’s Bank after the transaction and this is done
optionally.
The details of the transaction is received by the bank after withdrawal of money and amount is
debited from the account of the customer.

6OBJECT MODELLING
3. UML domain model class diagram
Figure 2: UML class diagram
(Source: Created by author)
4. Design activities of SDLC
SDLC (Software Development Life Cycle) is basically a framework or a structure that
defines the tasks that are performed while carrying out a project. The SDLC of a project details
all the procedures that are involved in each step while carrying the project (Sabatini et al., 2015).
The structure that defines properly the different development teams in different software
organizations. The SDLC generally focuses on detailed plan that are basically used to develop

7OBJECT MODELLING
the software, maintain the software, and also replace the software. The quality of software that is
designed is basically improvised by the methodologies that are involved in the life cycle of the
software (Kim, Jeong & Park, 2016). The activities that are involved in SDLC are planning,
testing, deployment, maintenance, implementation and documentation.
Planning: The most important area of developing software is the planning part. Planning
involves gathering of information, analysis and requirement, and then developing the software
finally (Kabir, Din & Hameed, 2017). Planning can be easily done by skilled as well as engineers
involved with the software in that organization.
Testing: This is a stage where after developing some parts of the software, the system is
tested partially and if there exists any defects, they are being corrected.
Deployment: The deployment of the software is done only after the client gives approval
to the design and completion of the software .
Maintaining: The maintenance is basically future reference. The maintenance usually
takes much time and is done entire life of the software because the software is to be maintained
throughout its life (Magdum et al., 2018). The maintenance process takes longer time than any
other processes.
Implementation: The system that is made is to be implemented finally with the codes
that are required to build the software.
Documentation: In documentation, all the procedures that were followed to make the
software are noted down (Kuhn, Balke & Wood, 2017). All the steps are noted, and documented

8OBJECT MODELLING
for future use. If any improvements are done in the software, then those are documented in the
documentation.
Environment
The design environment mainly focus on the design state and the planning state of the
Software development Life Cycle. Analysis is also done through planning. The main aim of the
SDLC process is carrying out the transaction process successfully in ATM system. The
environment of development basically aims on different phases and stages of SDLC model
(Gupta, Solanki & Serajuddin, 2016). In this ATM model, there are different platforms that carry
out different types of software developments in different stages of SDLC model. Different
models are carried out in different phases. Another environment of development is carried out in
system development is the IDE method or commonly known as Integrated Development
Environment (García et al., 2015). The IDE is basically a platform that provides platforms for
carrying out different types of processes. IDE also provides platform that has certain types of
processes that helps the engineers to with certain resources for accessing and the platform is cost
effective.
Designing the Components of Application
The main components involved while making the system of ATM mainly affects the
interaction that takes place in between the users and the ATM machine. The components of the
ATM system are mainly:
Key-Switch: The switch -pad is basically used for starting the ATM machine or turning
off the ATM.

9OBJECT MODELLING
Card-Reader: A card-reader is used by the system so that the system can read the data of
the card that are given by the users. There are magnetic strips on the card reader so that the ATM
reader will be able to read the card easily.
Screen: The screen is used for displaying the messages for the users (Onyesolu &
Okpala, 2017). The screen is basically used for the communication purpose between the user and
the ATM machine.
Key-pad: The key-pads are used to enter different types of information in the ATM.
Communication or Network infrastructure: This is a communication structure that is
used for communication with the bank with all the updates regarding the transaction of the users
User interfaces
The interaction that takes place between the user and the computer is commonly known
as the Human computer interaction that basically describes the interaction between the two
nodes. The human computer interaction aims on the methods that tells the computers what
humans are instructing and the responses from the system are also involved in user interface.
Database
The details of the bank account and the user details are all stored in the database of the
bank (Prasanthi et al., 2014). So, the managers can access the data regarding the customer from
anywhere he likes to. The system of ATM and the database system of the bank is connected.
When a transaction takes place in the ATM system, the database of the banks gets updated with
the newly transaction that is made.

10OBJECT MODELLING
Software methods
The system of ATM provides an interface of software. The networks that the ATM
system consists of are: all the software that are used by different banks, the software that is
responsible for transaction is used for the management of different kinds of resources and
transactions. There should be a CSM of version 3.0 that us basically used for management of
card and used to verify the pin and the login details of the user. The database should also have
Oracle to store the records.
Conclusion
In this report, a detailed structure of the Collision ATM Bank is shown that includes the
ATM system of the bank. The functional as well as non-functional requirements that are used to
complete the procedures of system are structured in details in this report. There is also a use case
diagram that shows the transaction procedures of the ATM with the user and all the actions are
explained clearly that takes place in the system. Detailed of design activities are detailed in this
report including the components, user interfaces, database, and the method of software are
discussed.

11OBJECT MODELLING
References
Buede, D. M., & Miller, W. D. (2016). The engineering design of systems: models and methods.
John Wiley & Sons.
Duvey, A. A., Goyal, D., &Hemrajani, D. N. (2013). A reliable ATM protocol and comparative
analysis on various parameters with other ATM protocols. International Journal of
Communication and Computer Technologies, 1(56), 192-197.
Duvey, A. A., Goyal, D., &Hemrajani, D. N. (2013). A reliable ATM protocol and comparative
analysis on various parameters with other ATM protocols. International Journal of
Communication and Computer Technologies, 1(56), 192-197.
García, D. V., Otte, A., Willemsen, A. T., Dierckx, R. A., Doorduin, J., & Holstege, G. (2015).
Altered Regional Cerebral Blood Flow in Chronic Whiplash Associated Disorder. PET
Imaging of Mild Traumatic Brain Injury and Whiplash Associated Disorder, 149.
Gupta, S. S., Solanki, N., & Serajuddin, A. T. (2016). Investigation of thermal and viscoelastic
properties of polymers relevant to hot melt extrusion, IV: Affinisol™ HPMC HME
polymers. AAPS PharmSciTech, 17(1), 148-157.
Hossian, F. S., Nawaz, A., &Grihan, K. (2013). Biometric authentication scheme for ATM
banking system using energy efficient AES processor. International Journal of
Information and Computer Science, 2(4), 57-63.

12OBJECT MODELLING
Kabir, G., Din, A. M., & Hameed, B. H. (2017). Pyrolysis of oil palm mesocarp fiber and palm
frond in a slow-heating fixed-bed reactor: A comparative study. Bioresource
technology, 241, 563-572.
Kim, Y. H., Jeong, B. Y., & Park, M. H. (2016). Universal User Interface Design of ATM Touch
Screen Based on the Reaction Time. Journal of the Ergonomics Society of Korea, 35(5).
Kopardekar, P. H. (2014). Unmanned aerial system (UAS) traffic management (UTM): Enabling
low-altitude airspace and UAS operations.
Kuhn, B., Balke, K., & Wood, N. (2017). Active Traffic Management (ATM) Implementation and
Operations Guide(No. FHWA-HOP-17-056).
Magdum, D., Patil, T., Suman, M., & Patil, T. M. (2018). Designing Talking ATM System for
People with Visual Impairments. International Journal of Engineering &
Technology, 7(2.7), 657-660.
Onyesolu, M. O., & Okpala, A. C. (2017). Improving Security Using a Three-Tier
Authentication for Automated Teller Machine (ATM). International Journal of Computer
Network and Information Security, 9(10), 50.
Prasanthi, B. V., Jyothi, U. P., Sridevi, B., & Krishna, T. V. (2014). Security Enhancement of
ATM System with Fingerprint and DNA Data. International Journal of Advanced
Research in Computer Science and Software Engineering.
Ramasamy, S., Sabatini, R., Gardi, A. G., & Liu, Y. (2013). Novel flight management system for
real-time 4-dimensional trajectory based operations. In AIAA Guidance, Navigation, and
Control (GNC) Conference (p. 4763).

13OBJECT MODELLING
Sabatini, R., Gardi, A., & Richardson, M. (2014). LIDAR obstacle warning and avoidance
system for unmanned aircraft. International Journal of Mechanical, Aerospace,
Industrial and Mechatronics Engineering, 8(4), 718-729.
Sabatini, R., Gardi, A., Ramasamy, S., Kistan, T., & Marino, M. (2015). Modern avionics and
ATM systems for green operations. Encyclopedia of Aerospace Engineering.