{"id":8706,"date":"2026-08-27T08:23:33","date_gmt":"2026-08-27T08:23:33","guid":{"rendered":"https:\/\/www.learn-vp.com\/in\/vpascode\/atm-system-use-case-diagram-plantuml-guide\/"},"modified":"2026-08-28T07:57:42","modified_gmt":"2026-08-28T07:57:42","slug":"atm-system-use-case-diagram-plantuml-guide","status":"publish","type":"vpascode","link":"https:\/\/www.learn-vp.com\/in\/vpascode\/atm-system-use-case-diagram-plantuml-guide\/","title":{"rendered":"Designing an ATM System Use Case Diagram with PlantUML"},"content":{"rendered":"

Introduction & System Overview<\/h2>\n

In the finance industry, clarity is currency. When designing complex banking systems like an Automated Teller Machine (ATM), understanding the interactions between users and the system is critical. A Use Case Diagram<\/strong> provides that high-level view, mapping out actors (such as Customers, Tellers, and Administrators) and their specific capabilities within the system.<\/p>\n

For software architects and developers, using a diagram-as-code<\/strong> approach offers significant advantages over traditional drag-and-drop tools. With VPasCode<\/strong>, you can version control your diagrams, collaborate via Git, and generate professional visuals instantly using PlantUML<\/strong>. In this masterclass, we will build a robust ATM System Use Case diagram, demonstrating how to structure actors, system boundaries, and relationships efficiently.<\/p>\n

Complete Diagram & Full Source Code<\/h2>\n

Before diving into the construction steps, here is the complete, finished diagram. You can view the visual output below and inspect the source code immediately following it.<\/p>\n

\"ATM<\/p>\n

Copy the complete source code below to replicate this diagram in VPasCode<\/strong> or any PlantUML<\/strong> editor.<\/p>\n

\r\n
\r\n PlantUML<\/span>\r\n \r\n <\/path><\/path><\/svg>\r\n Edit PlantUML in VPasCode<\/span>\r\n <\/a>\r\n <\/div>\r\n
\r\n 
@startuml\r\n!include https:\/\/static.visual-paradigm.com\/web\/resources\/plantuml-stdlib\/themes\/vp.puml\r\n\r\nleft to right direction\r\nskinparam packageStyle rectangle\r\n\r\ntitle ATM System Use Case Diagram\r\n\r\nactor Customer\r\nactor BankTeller\r\nactor Administrator\r\n\r\nrectangle \"ATM System\" {\r\n  usecase \"Withdraw Cash\" as UC1\r\n  usecase \"Deposit Cash\" as UC2\r\n  usecase \"Check Balance\" as UC3\r\n  usecase \"Transfer Funds\" as UC4\r\n  usecase \"Print Statement\" as UC5\r\n  usecase \"Change PIN\" as UC6\r\n  usecase \"Lock Account\" as UC7\r\n  usecase \"Manage Cards\" as UC8\r\n  usecase \"System Maintenance\" as UC9\r\n}\r\n\r\nCustomer --> UC1\r\nCustomer --> UC2\r\nCustomer --> UC3\r\nCustomer --> UC4\r\nCustomer --> UC5\r\nCustomer --> UC6\r\n\r\nBankTeller --> UC7\r\nBankTeller --> UC8\r\n\r\nAdministrator --> UC9\r\nAdministrator --> UC8\r\n\r\n\r\n@enduml<\/code><\/pre>                <\/div>\r\n                
\r\n                    \r\n                        <\/path><\/path><\/svg>\r\n                        Edit PlantUML in VPasCode<\/span>\r\n                    <\/a>\r\n                <\/div>\r\n            <\/div>\r\n            \n
Step-by-Step Breakdown & Thought Process<\/h2>\n
Building a professional diagram from scratch requires a logical flow. Here is how I approached the design of this ATM System Use Case diagram using VPasCode<\/strong>.<\/p>\n
1. Setting Up the Foundation<\/h3>\n
Every PlantUML<\/strong> diagram starts with the @startuml<\/code> directive. To ensure our diagram looks professional and aligns with modern design standards, I immediately included the VPasCode<\/strong> theme. This ensures consistent styling for actors, use cases, and system boundaries.<\/p>\n            
\r\n                                
\r\n                    PlantUML<\/span>\r\n                    \r\n                        <\/path><\/path><\/svg>\r\n                        Edit PlantUML in VPasCode<\/span>\r\n                    <\/a>\r\n                <\/div>\r\n                                
\r\n                    
@startuml\r\n!include https:\/\/static.visual-paradigm.com\/web\/resources\/plantuml-stdlib\/themes\/vp.puml<\/code><\/pre>                <\/div>\r\n                
\r\n                    \r\n                        <\/path><\/path><\/svg>\r\n                        Edit PlantUML in VPasCode<\/span>\r\n                    <\/a>\r\n                <\/div>\r\n            <\/div>\r\n            \n
2. Defining Direction and Style<\/h3>\n
For use case diagrams, a horizontal layout often reads better than a vertical one. I set the direction to left to right<\/code> and specified a rectangular style for the system boundary package. This creates a clean container for the system logic.<\/p>\n
left to right direction\r\nskinparam packageStyle rectangle<\/code><\/pre>\n
3. Declaring Actors and System Boundary<\/h3>\n
Next, I defined the title and the external actors interacting with the system. In this finance use case, we have three distinct roles: the Customer<\/strong> (primary user), the BankTeller<\/strong> (support staff), and the Administrator<\/strong> (system maintenance).<\/p>\n
I then enclosed the core functionality within a rectangle labeled “ATM System”. This boundary is crucial as it visually separates internal system processes from external entities.<\/p>\n            
\r\n                                
\r\n                    PlantUML<\/span>\r\n                    \r\n                        <\/path><\/path><\/svg>\r\n                        Edit PlantUML in VPasCode<\/span>\r\n                    <\/a>\r\n                <\/div>\r\n                                
\r\n                    
title ATM System Use Case Diagram\r\n\r\nactor Customer\r\nactor BankTeller\r\nactor Administrator\r\n\r\nrectangle \"ATM System\" {<\/code><\/pre>                <\/div>\r\n                
\r\n                    \r\n                        <\/path><\/path><\/svg>\r\n                        Edit PlantUML in VPasCode<\/span>\r\n                    <\/a>\r\n                <\/div>\r\n            <\/div>\r\n            \n
4. Mapping Use Cases and Relationships<\/h3>\n
Inside the system boundary, I defined nine distinct use cases, ranging from basic transactions like “Withdraw Cash” to administrative tasks like “System Maintenance”. I assigned unique IDs (UC1-UC9) to each use case. This makes it easier to reference them when drawing relationships.<\/p>\n
Finally, I mapped the interactions. The Customer<\/strong> connects to standard banking functions. The BankTeller<\/strong> handles account security and card management. The Administrator<\/strong> oversees maintenance and card management. Using the --><\/code> syntax clearly indicates the flow of interaction.<\/p>\n            
\r\n                                
\r\n                    PlantUML<\/span>\r\n                    \r\n                        <\/path><\/path><\/svg>\r\n                        Edit PlantUML in VPasCode<\/span>\r\n                    <\/a>\r\n                <\/div>\r\n                                
\r\n                    
Customer --> UC1\r\nCustomer --> UC2\r\n...\r\nBankTeller --> UC7\r\n...\r\nAdministrator --> UC9\r\n\r\n@enduml<\/code><\/pre>                <\/div>\r\n                
\r\n                    \r\n                        <\/path><\/path><\/svg>\r\n                        Edit PlantUML in VPasCode<\/span>\r\n                    <\/a>\r\n                <\/div>\r\n            <\/div>\r\n            \n
Key Takeaways & Best Practices<\/h2>\n