UML Diagrams - ATM
UML Diagrams - ATM
ATM
Contents
• PROBLEM STATEMENT -ATM
• ATM – USECASE DIAGRAM
• ATM – CLASS DIAGRAM
• ATM – SEQUENCE DIAGRAM
• ATM – COLLABORATION DIAGRAM
• ATM – STATE DIAGRAM
• ATM – ACTIVITY DIAGRAM
Problem Statement -ATM
• When user want to withdraw money, first he need to insert the ATM card into the ATM
machine. The ATM machine will then verify the card is an valid ATM card or not. If the card
is invalid, the system will shows the error message and eject the card. If the card is valid,
then the system will ask the user to enter the PIN code. Once the user has entered the PIN
code, then the system will verify the Account and PIN with the Bank.
• If the PIN is invalid the system will ask the user to re-enter the PIN. If the PIN is valid, then
the system will ask the user to select what action that he want's to perform. If user select
withdraw money, then the system will ask the user to enter the amount that he want to
withdraw. The system will then check for the account balance of the user. If the balance is
enough, withdraw is success. The system will then display the withdraw success message,
eject the ATM card to the user, and dispense the cash to the user. If the balance is not
enough, the system will display error message indicate that withdraw was fail. User can re-
enter the amount that he want to withdraw, or simply cancel the action.
Problem Statement -ATM
• In order to communicate with the Bank, the ATM system need the
help from the Bank Consortium. The Bank Consortium act as the
middle man between the ATM system and the Bank. All request and
response between the ATM system and the Bank will pass through
the consortium.
Requirement Elicitation
• Requirement elicitation for ATM UML diagrams involves gathering and
defining functional and non-functional requirements to represent the
system accurately.
Usecase Diagram
The "Rank" column represents the priority or importance assigned to each use case.
High: Functions that are essential and most commonly used (e.g., withdrawing money or checking balance).
Medium: Functions that are important but not as frequently used or critical as high-priority ones (e.g., transferring money
or login).
Low: Functions that are less critical or infrequently used (e.g., depositing money).
Usecase Diagram
USER LOGIN
Usecase diagram- Use cases
TRANSFER MONEY
WITHDRAW MONEY
Usecase diagram- Use cases