Sequence Diagram for ATM System

In this article, I will give you an idea how to create a Sequence Diagram for ATM System. Aside from this idea, you can get the ATM System, which will be useful for your DBMS studies.

What is ATM System Sequence Diagram?

The Sequence Diagram for ATM System is a created Unified Modeling Language (UML) diagram that depicts the flow of messages or events between objects in a management system.

Further, It aids in the depiction of the sequence of messages sent between actors and objects. Sequence diagrams can also explain how the ATM System should govern the structures between things in greater detail.

How to make an ATM Withdrawal Sequence Diagram?

Sequence diagrams are excellent for depicting how elements in a system interact over time. Consider how a banking customer interacts with an ATM to withdraw cash.

We can begin by thinking about the characters we’ll use. We need to represent the user, the ATM, and the database in our example. These items don’t need to be defined just yet. They will be generated automatically as we describe the encounters.

The first encounter is straightforward. The card is inserted into the ATM by the user.

-Insert card-> ATM -User -Insert card-> ATM -Us

Create a labeled arrow with the word “user” to describe the message that is being sent from the user to the ATM. Simply press the hyphen key, then type the label “insert card,” and it will recognize that you are sending a message. Simply autocomplete the arrow after entering the label to finish your first contact.

The ATM must then check the bank database to ensure that the card number is correct. This message will be described using syntax that will display an activation bar to indicate that the database object is active, or instantiated, at this point in the process.

So we retype the syntax to create a “card number” message between the ATM and the database, and the arrow autocompletes. We’ll use the + key to add an activation bar to the diagram this time.

  • Database -> ATM- Card number

This is a reply message, as the database will respond to the ATM with a response. Simply add a hyphen after that arrow in the “card OK” message that the database sends to the ATM to signify this. In this scenario, the hyphen functions as a negative sign to end the activation bar, causing the message to be sent back at the end of the bar.

Database- Accepted Card->ATM

The user must now enter their PIN into the ATM. This is a simple scenario of the ATM sending messages to the user and the user sending messages to the ATM. To show activation bars and identify which object is instantiated, we’ll add a + at the end once more.

-Pin request->+ User ATM

The user enters the PIN and the information is transmitted to the ATM.

User -Pin-> ATM

The ATM must now verify the database once more to ensure that the PIN is correct. Remember to include the plus symbol!

ATM -Pin Check->+ Database

The database checks that the PIN is correct and sends a message back to the ATM.

Database- Pin is correct->- ATM

At this stage, the user must choose what they wish to accomplish, therefore the ATM displays a choice of options.

Option menu->+ User at the ATM

The user makes a cash withdrawal request. The ATM then asks for the amount to be withdrawn, and the user selects the amount to be withdrawn. Throughout this interaction, the activation bar remains with the user.

User – Request for a withdrawal -> ATM

ATM- Amount request-> User

After the amount has been chosen, the ATM must send a message to the database to verify that the customer’s account has sufficient funds. It’s worth noting that the activation bar is also gone.

Check the funds at the ATM-> Database

This message can be interpreted in two ways. In one, the user has sufficient funds and is able to withdraw money. The user does not have sufficient funds in the other case, and the request is declined.

The alt operator is used to indicate this. To get this working, type forward slash and alt, then write a description for the condition you want to depict. The first situation we’ll go over is when the transaction has been approved.

/alter Transaction has been accepted

This section of the procedure will be framed by it. When generating this frame, it’s critical that you hit the TAB key after each line. Each line is indented, and the entire section is nested in the frame.

A response message is the database’s response to the ATM if there are sufficient funds. An arrow with a dotted line can be used to demonstrate this. To do this, simply put a period after the hyphen.

Sufficient funds-> Database ATM

Remember to indent the line with the TAB key!

If the user has sufficient funds in their account, the ATM will dispense cash, the user will accept the cash, and the ATM will then return the card to the user (or in some cases, the card will be returned before the cash).

User dispenses cash from an ATM

Take cash from the ATM if you’re a user.

Return card to ATM-> User

But our flowchart doesn’t stop there. Unfortunately, the user’s account may be insufficiently funded. In this situation, we’ll keep the alt fragment going until the user receives a rejection message and their card, but no cash.

/alter Transaction has been rejected

Insufficient funds in the database -> ATM

Show details about ATM rejections-> User

Return the card to the ATM-> User

So, while our hypothetical user may go away empty-handed from the ATM, we hope you walk away from this example with a clear grasp of how to design a simple sequence diagram.

ATM System Simple Sequence Diagram (UML)

In this tutorial, I’ll show you how to draw the ATM System’s Sequence diagram. This illustration will show you how the system and the actor should interact with one another. This will also teach you how to construct the system so that it can achieve the desired behavior.

Design of an ATM System Sequence Diagram
The diagram I’ll show you is a thorough representation of the sequence of events that occur in an ATM system.

This well-designed sequence diagram can illustrate programmers and readers the order in which messages are exchanged between the actor and the objects. In creating this sequence diagram we used Lucidchart.

The conditions and interactions are shown in the figure, and these interactions are critical for the evolution of the ATM System.

To assist you in designing the ATM System, a series of notifications are displayed and labeled. If you come up with new ideas, you can change the design. You can also expand on this design and use it as a blueprint for your project.

By drawing a sequence diagram, you will be able to comprehend and educate yourself on how the ATM System operates. Because it determines the objects, actors, messages, and interactions that are needed.


To summarized, we have discussed about the sequence diagram of ATM System, and how to create an activity diagram for ATM System and login.


If you have inquiries or suggestions about Sequence Diagram for ATM System, just leave us your comments below. We would be glad to hear to concerns and suggestions and be part of your learning.

Leave a Comment