Object Modelling: Detailed Analysis of the Collins ATM System

This report presents an object-oriented analysis of the Collins ATM system, focusing on the development of a prototype to understand transaction mechanisms and cash withdrawal processes. It outlines the aims and objectives, which include reducing system complexity and establishing rules between system modules, represented in UML modelling. The report identifies functional requirements such as card and PIN verification, withdrawal transactions, balance inquiries, and fund transfers, alongside non-functional requirements like usability, reliability, and security. Three key use cases—PIN verification, session timeout, and cash withdrawal—are identified and analyzed. The report includes sequence diagrams for each use case, illustrating message flows between different modules. The conclusion emphasizes the utility of sequence diagrams in identifying message exchanges and reducing errors in the final software, ultimately improving the efficiency of the Collins ATM operation. The report also includes a comprehensive bibliography of related sources.

Running head: OBJECT MODELLING
Object Modelling: Collins ATM
Name of the Student
Name of the University
Author’s Note

1
OBJECT MODELLING
Table of Contents
Introduction................................................................................................................................2
Aims.......................................................................................................................................2
Objectives...............................................................................................................................2
Functional and Non Functional Requirement............................................................................3
Identification of three important Use case.............................................................................5
Use Case.....................................................................................................................................6
Sequence Diagram for the Use case.......................................................................................7
Conclusion..................................................................................................................................9
Bibliography.............................................................................................................................11

2
OBJECT MODELLING
Introduction
The report is prepared based on Collins ATM case study for the development of the
prototype and learn the mechanism for transaction and withdrawing cash from ATM. For the
development of the ATM system the model should meet the different key requirements such
as recognition of the cards, verification of the pin from the customer, selection of the account,
transaction from the account, generation of receipt and report. The object modelling is used
for the analysis of the complexity and the problem that are faced for interacting with the
different modules and performing it as a relation set. The report mainly focuses on the
successful authentication for withdrawing the cash from the ATM machine.
Aims
The main aim of the report is to reduce the complexity of the ATM system and set the
rules between the modules of the system for its representation in the UML modelling. The
best engineering practices should be applied for the identification of the sequence of the flow
of the task involved for the proper working of the ATM system. An object oriented analysis
should be looked and the different areas for the development of the ATM system should be
identified for the identification of the objects and the entities that are related with the problem
domain and create a static model for the structuring the ATM system. The system sequence
diagram is created from the use case diagram for the identification of the sequence of the
process involved in different operation of the ATM machine.
Objectives
The main objectives for the development of the sequence diagram for the ATM case
study are as follows:
 Analysis of the use case model and identification of the flow of the task involved for
the management of the ATM machine.

3
OBJECT MODELLING
 Analysis of the class diagram and the functional requirement of the system for the
Collins ATM and facilitating the customer for performing the different activities.
 To eliminate the errors in the ATM machine such that the failures in the transaction
can be recorded and the different types of accounts are handled for the completion of
the transaction.
 To connect with the database of the bank and update the database on each of the
transaction for the identification of the sequence diagram.
Functional and Non Functional Requirement
The functional requirement identified for the development of the ATM system are
listed below:
Card verification – The car inserted by the customer should be verified for the
detection of the user name and the account ID and create a transaction link for the system.
Verification of PIN - The user inputs the PIN in the ATM machine for the validation
of the user account and entering into the withdrawal mode.
Withdrawal transaction – it is used by taking inputs from the user such as selection
of the account type, verification of the successful amount of balance for the transaction and
generate a transaction receipt.
Change PIN – This option is provided to the user for increasing the security of the
account. The user can change the pin by verification of the account and entering the old pin
into the ATM machine.
Enquiry for Balance – The user can verify the details of the account and find the
available balance in the account by selecting the balance enquiry option in the ATM machine
and know the details before withdrawing cash from the account.

4
OBJECT MODELLING
Transfer – Different account of the user or other personnel can be selected by
entering into the fund transfer mode and entering the account number of the personnel to
whom the fund is needed to be transferred.
Invalid rejection – If a wrong Pin is entered in the ATM machine more than three
times a request is sent from the ATM machine to block the card. This increases the security
of the ATM transaction.
Session Time Out – For the successful transaction a session time should be allocated
for the user within which the user needs to complete the transaction process otherwise the
transaction is marked as failed.
Deposit Transaction – The user can deposit cash with successfully verification of the
user account into the ATM machine.
The non-functional requirement identified for the development of the Collin’s ATM are listed
below:
Usability – The interface of the ATM should be developed such that the user needs to
spend minimum time for taking out cash from the ATM machine. The different options
available for the user must be given to the user for increasing the efficiency of the system.
Reliability – The ATM system must respond to the query of the user and the database
should be updated at a minimal time for increasing the accuracy and integrating with the
banking facility.
Confidentiality – The ATM machine must be installed in a secure location and kept
under surveillance for prevention of the misuse of the system. The information should be kept
secured and secured links should be used for connecting with the bank servers.

5
OBJECT MODELLING
Identification of three important Use case
The three important use case are identified for the Collin’s ATM system that are listed below:
 Verification of the User PIN
 Session Time out
 Cash Withdrawal
Verification of the User PIN – The ATM machine needs to verify the Pin inputted by the
user for the validation of the account and enable the transaction. Here the actor is the
customer using the ATM machine and the objects are the ATM machine, card reader and the
customer console. When the customer inserts the ATM card in the machine the card reader
verifies the car and the message is returned to the ATM machine. The customer console takes
the input from the customer for verification of the PIN and it is verified for proceeding with
the next stage of the transaction.
Session Time out – The main actor for the Time out sequence diagram is the customer
and the objects are the card reader, ATM, Session, Customer Console and the transaction. On
successful verification of the PIN provided by the user the user a session is created for
performing the transaction and after completion of the transaction the card is ejected from the
ATM machine with a proper message.
Cash Withdrawal – For withdrawing cash from the ATM machine the user needs to
complete the validation of the user account and the system connects with the database of the
bank server for updating the transaction procedure. If there is a failure in the link the
transaction is rolled backed and a message is displayed showing transaction failed.

6
OBJECT MODELLING
Use Case
Ten use case diagram is provided for the Collin’s ATM case study and it is used for the
identification of the interaction between the different components and the modules used for
running the ATM system. It is required to be assumed that the software development team
and the designer team share the same platform for the development of the software and the
development of the interaction diagram helps in development of a common structure and
develop the information system sharing the same goals and objectives for the development of
the Collins ATM system. The object modelling helps in reducing the risk of
miscommunication and the documentation of the model is also important for resolving the
errors in the current system and increasing the efficiency of the development procedure.

7
OBJECT MODELLING
Sequence Diagram for the Use case
Sequence Diagram for Session
It is developed form the use case for defining the session that is created for enabling the user
to withdraw money, view balance or deposit money using the ATM machine. The main
process has different sub process and the flow of the information from one subsystem to
another is shown with the help of the arrow. When the user inserts the card the message flows
from the card reader to the ATM system. Then after the verification process the session is
created and the process is transferred to the other sub module of the ATM.

8
OBJECT MODELLING
Sequence Diagram for PIN verification
For the verification of the Pin the main process is the customer and the other sub processes
are the ATM, card reader and the customer console. After the verification of the car is
completed the information is passed to the customer from the customer console to take the
input from the user. The details of the pin are forwarded to the customer and the customer
console validates the pin for connecting the user with the banking server.

9
OBJECT MODELLING
Sequence Diagram for cash withdrawal
After the verification of the Pin the customer can withdraw money from the ATM and here
the main sub process are the Customer, Card reader, ATM, Session, Customer console and
the Transaction. When the Pin is verified the session is created and a checking of the balance
is made for enabling the transaction of money and updating the bank server.
Conclusion
From the above report it can be concluded that with the development of the system
sequence diagram the steps involved for sending messages between the different modules can
be identified. The development of the system sequence diagram is involved in the software
design phase of the software development model and it is used for the identification of the
data between the different objects for the creation of the relation between the objects. The
communication between the different objects and the relation between them are identified for

10
OBJECT MODELLING
eliminating the complexity of the system and reduce the number of errors on the final
software developed for the management of the operation of the Collin’s ATM.

11
OBJECT MODELLING
Bibliography
Adams, K. (2015). Non-functional requirements in systems analysis and design (Vol. 28).
Springer.
Alshamrani, A., & Bahattab, A. (2015). A comparison between three SDLC models waterfall
model, spiral model, and Incremental/Iterative model. International Journal of
Computer Science Issues (IJCSI), 12(1), 106.
Coronel, C., & Morris, S. (2016). Database systems: design, implementation, & management.
Cengage Learning.
Eckhardt, J., Vogelsang, A., & Fernández, D. M. (2016, May). Are" Non-functional"
Requirements really Non-functional? An Investigation of Non-functional
Requirements in Practice. In Software Engineering (ICSE), 2016 IEEE/ACM 38th
International Conference on (pp. 832-842). IEEE.
GUPTA, R. S., & LAXMI, V. (2015). Software Development Life Cycle (SDLC)
Implementationin Information Technology & Management. International Journal of
Recent Advances in Information Technology & Management, 1(1).
Hasan, M. M., Loucopoulos, P., & Nikolaidou, M. (2014). Classification and qualitative
analysis of non-functional requirements approaches. In Enterprise, Business-Process
and Information Systems Modeling (pp. 348-362). Springer, Berlin, Heidelberg.
Jamro, M. (2015). SysML Modeling of Functional and Non-functional Requirements for IEC
61131-3 Control Systems. In Progress in Automation, Robotics and Measuring
Techniques(pp. 91-100). Springer International Publishing.