ATM System Design and Development

This report provides a comprehensive overview of the ATM system design and development process. It includes the identification of key stakeholders, functional and non-functional requirements, use case diagrams, UML domain model class diagrams, and software methods. The assignment also discusses the importance of integrated development environments, design application components, user interfaces, databases, and software methods in the development of an ATM system.

Running head: OBJECT MODELLING
Object modelling
Assessment 2
[Name of the student]
[Name of the university]

1OBJECT MODELLING
Table of Contents
Introduction 2
Functional and non-functional requirements 2
Use case diagram 5
Use Case describe 5
UML domain model class diagram 6
Design activities of SDLC 7
Environment 8
Designing Application Components 8
User interfaces 9
Database 9
Software methods 9
Conclusion 10
References 11

2OBJECT MODELLING
Introduction
ATM is considered to be an important part of our daily life which helps in transaction and
business. An automated teller machine (ATM) is nothing but a computerized telecommunication
machine which provides clients with various kinds of financial transactions (Kopardekar, 2014).
It provides money without the need of cashier, human clerk. ATM provides people with goods
quality like people can easily have money at the time of need or requirement. ATM system is
generally needed because the braches does not remain open all time.
In the coming pages of the report various functional and non-functional requirements of
machines has been discussed in details. A proper use case diagram with proper description has
been provided. An idea has been provided regarding UML class model diagram. Various kinds
of design activities of SDLC has been provided.
Functional and non-functional requirements
In implementation of new system, the main process is determining the user expectations
for this new ATM system. Therefore, this details are called requirements which must be
quantifiable, relevant and detailed. However, such requirements are known as functional
requirements or specification.
Functional requirements are defining such tasks that are being performed during the new
ATM system development for Collin’s ATM bank. In this document the functional requirements
are labeled as FR and non-functional requirements are labeled as NFR.
Functional requirement for Collin’s ATM:
FR-1: The ATM card reader much scan the account number from the card.

3OBJECT MODELLING
FR-2: if there are no operation is attempt on the system then it should be in idle state.
FR-3: The system shows a prompted to the users to enter the PIN after the card has been
successfully detected.
FR-4: The system will prompt a menu to display withdraw, check account balance,
deposit, money transfer as well as print the transaction.
FR-5: The cash dispenser must be in idle state to dispense cash.
FR-6: The transaction record is generated and it will print after each transaction made.
FR-7: Whenever the transaction is complete the card is automatically rejected.
FR-8: To deposit the money an automatic machine, the cash dispenser is aware of the
cash.
FR-9: The keypad of the ATM system must accept the input from the users.
FR-10: The transfer script determines that whether the paper and ink is sufficient for print
operation.
FR-11: To transfer the money to another account, this automated system must satisfy that
the recipient account number is valid.
FR-12: One user has three attempts to make money transfer or withdrawn.
FR-13: ATM can capture cards whenever the system observe that is an unauthorized user.
The non-functional requirements:

4OBJECT MODELLING
NFR-1: The Collin’s ATM system consist of card reader, keypad, display, cash dispenser,
printer as well as chute to deposit cash.
NFR-2: The ATM machine have a keypad where 10 buttons labelled with 0 to 9, cancel,
clear and okay button.
NFR-3: A card must be recognized by 5 second.
NFR-4: One user has only three attempts to enter correct PIN.
NFR-5: The ATM system must be secure.
NFR-6: The ATM system must have a schedule restart option.
NFR-7: The System will be open to refilled the cash dispenser with cash.
NFR-8: The system printer can be refilled with paper.

5OBJECT MODELLING
Use case diagram
Figure 1: Showing Use Case diagram
(Source: Created by author)
Use Case describe
Collin’s ATM bank: The Collin’s bank allows their clients to withdrawn, transfer money
to another account and deposit into their bank account. The above use case is initialized with a
customer punching the ATM card as well as withdrawn amount.
Actors:

6OBJECT MODELLING
 Bank’s Customer
 Banking system with automatic machine.
Trigger:
 One user can withdraw money from one of the account.
Preconditions:
 The Collin’s ATM is operational.
 The user must have a card to scan in the ATM card reader system.
Post Conditions:
 The Collin’s bank customer can receive their cash and optionally they can a receipt.
 Bank has recorded the details of the transaction and debited the withdraw amount from
the customer’s bank.
UML domain model class diagram
Figure 2: Showing UML class diagram
(Source: Created by author)

7OBJECT MODELLING
Design activities of SDLC
Software Development Life Cycle (SDLC) is nothing but a kind of framework which
defines tasks performed at each and every step. SDLC is a kind of structure which is properly
followed by various development teams within the various software organization (Hossian,
Nawaz & Grihan, 2013). It generally focuses on the detail plan which can be used for
developing, maintaining and replacing of certain number of software’s. This life cycle is a
methodology which can be used for improving the quality of software and overall process of
development (Duvey, Goyal & Hemrajani, 2013). SDLC mainly consist of following kinds of
activities like planning, implementation, testing, documentation, deployment and maintenance,
Maintaining.
Planning: This is the most important portion of software development, gathering of
requirement or analysis. It can be easily achieved by skilled and software engineers in an
organization.
Implementation: Various software engineers generally starts writing code as the
requirement or need of Client.
Testing: This step in the software development model focus on finding detects or bugs
which may be present in the software.
Documentation: Each and every step in the project is generally documented for future
kind of references (Sezer et al., 2013). It also stores any kind of improvements made in the
software domain. The proper kind of design documentation is generally inclusive of having
application programming interface (API).
Deployment: Generally, software is deployed after proper kind of approval from release.

8OBJECT MODELLING
Maintaining: Software maintenance is generally for any kind of future references. At
any phase of time improvements in software domain can easily take longer time which is needed
for creating initial development of software.
Environment
Analysis or Design environment generally focus on planning and design stage of SDLC
model. In this environment, the main process focus on carrying out examination of the ATM
system (Sabatini et al., 2015). The development environment generally focuses on various stages
or phases of SDLC model. This is the particular kind of platform where various kinds of
software developments are carried out. Another kind of development environment is IDE or
integrated development environment. IDE (Integrated Development Environment) is nothing but
a platform which provides platforms which can be used for various kinds of development process
(Buede & Miller, 2016). It will also provide a platform which consist of certain processes which
can easily help the engineers to provide a convenient way for accessing certain number of
resources which is considered to be cost effective.
Designing Application Components
The main components of ATM will generally affect the proper kind of interaction
between ATM and various users. It consists of following things like:
Key –Switch: This switch is mainly used for start that is On and shutting down that is
OFF for any kind of ATM machine.
Card-Reader: A card reader should be there so that it can easily read ATM cards from
user end. An ATM card can be easily read by the help of magnetic stripe reader.
Screen: It is mainly used for displaying various kinds of messages to users.

9OBJECT MODELLING
Key pad: Key pads are generally used for entering various kinds of information to the
ATM.
Cash dispenser: A cash dispenser is there for dispensing various kinds of cashes.
Deposit Slot: A deposit slot is there for depositing cash or checks from various users.
Printer: A printer is there in ATM machines for printing various kinds of Receipts.
Communication / Network infrastructure: It is generally assumed that various kinds of
communication structure is used for communication with the bank along with any kind of
activities related to transaction (Ramasamy et al., 2013).
User interfaces
Human computer Interaction is well known term which is used for describing interaction
of interaction between users and computers (Buede & Miller, 2016). In other words, it can be
easily said that it focuses on methods which tells the computers to what to do and various kinds
of responses which is made by computer.
Database
Various kinds of bank officers like bank manager and other executive can easily access to
the ATM system information which is stored in the database of the bank. The information related
to various kinds of transaction is updated on regular basis on the database (Buede & Miller,
2016). All kind of interaction related to managers/offers with ATM can be easily conducted
through the database which is present in the bank (Sabatini, Gardi & Richardson, 2014).
Software methods
The network of ATM provides a software interface consist of:

10OBJECT MODELLING
 Software used by various banks.
 Transaction Management Software which is used for managing various kinds of
transaction and keeping track of resources shall be under the BMS version 2.0
 CSM version of 3.0 is used for card management software for verifying pin no
and login.
 Different kind of network software.
 For various kinds of active Yamaha codecs 367/98.
 Database which is used for records should consist of Oracle version 7.0.
Conclusion
From the above discussion can be easily concluded that this report is all about Collin
ATM system. All the functional and non-functional requirement of ATM system has been
discussed in details. A use case diagram with proper explanation and description has been
provided. UML domain model class diagram for various ATM system has been provided. Design
activities of SDLC has been discussed in brief. All the important stages of SDLC like planning,
implementation, Testing, Documentation, Deployment and maintenance has been discussed in
details. Various kinds of factors like environment, design application components, user
interfaces, Database, software method has been discussed in details. In the environment section
an idea has been provided regarding integrated development environment. Key design
components like switch, card reader, key pad, dispenser slot, communication and network
infrastructure has been discussed in details.

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.
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.
Kopardekar, P. H. (2014). Unmanned aerial system (UAS) traffic management (UTM): Enabling
low-altitude airspace and UAS operations.
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).
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.

12OBJECT MODELLING
Sezer, S., Scott-Hayward, S., Chouhan, P. K., Fraser, B., Lake, D., Finnegan, J., ... & Rao, N.
(2013). Are we ready for SDN? Implementation challenges for software-defined
networks. IEEE Communications Magazine, 51(7), 36-43.