UML has many types of diagrams. They all can be divided into two main categories. Some of their types represent structural information and some - the general types of behavior, e.g. different aspects of interactions.
The activity diagrams may be referred to the UML diagrams, being the graphical representations of workflows of actions and activities with support for iteration, concurrency, and choice. All the activity diagrams in the Unified Modeling Language are known to be intended to model both organizational and computational processes. There also may be the data flows intersecting with the related activities, showing the overall flow of control. They can also include other elements in order to show the flow of data between activities through one or more data stores.
In software engineering, any class diagram can be also referred to the Unified Modeling Language (UML). It is known to be a type of static structure diagram, being expected to describe the structure of a system in a way of showing the system's classes, their attributes, methods or operations as well as the relationships among objects.
Being the main building block of any object-oriented modeling, a class diagram is widely used for general conceptual modeling of the systematic of the application. It can be also used for the detailed modeling translating the models into programming code. They can also be used for any needed data modeling, representing the main elements, the interactions in the application as well as the classes to be programmed.
In order to further describe the behavior of the systems, the mentioned class diagrams can be complemented by either a UML state machine or a state diagram which may be also referred to be one of the UML diagrams. In order to create one of these, the ConceptDraw DIAGRAM diagramming and drawing software can be used.
The ATM UML Diagrams solution provides a selection of text boxes, pre-made templates, and icons that allow one to map the software process of any ATM (Automated Teller Machine) by using a variety of the professionally made UML examples for creating a unique design.
Being available for all the ConceptDraw DIAGRAM users, the ATM UML Diagrams solution may be especially useful for all the banking industry software specialists in order to design and to build the needed ATM solutions and systems.
There are a few samples that you see on this page which were created in the ConceptDraw DIAGRAM application by using the ATM UML Diagrams solution.
Some of the solution's capabilities as well as the professional results which you can achieve are all demonstrated here on this page.
All source documents are vector graphic documents which are always available for modifying, reviewing and/or
converting to many different formats, such as MS PowerPoint, PDF file, MS Visio, and many
other graphic ones from the ConceptDraw Solution Park or ConceptDraw STORE. The ATM UML Diagrams solution is available to all
ConceptDraw DIAGRAM users to get installed and used while working in the ConceptDraw DIAGRAM diagramming and drawing software.
Example 1: ATM Sequence Diagram
This diagram was created in ConceptDraw DIAGRAM using the Bank UML Sequence library from the ATM UML Diagrams solution. An experienced user spent 10 minutes creating this sample.
This sample deconstructs the process of interaction between customer, ATM and bank, and shows the transaction in a simple, clear manner. Using ConceptDraw DIAGRAM as a UML image creator, it is possible to display just one linear process, or create a more complex design.
Example 2: Bank Activity Diagram
This diagram was created in ConceptDraw DIAGRAM using the Bank UML State Machine Diagram library from the ATM UML Diagrams solution. An experienced user spent 10 minutes creating this sample.
By adding text to your design, you can create an information-rich drawing, that effectively combines professional UML elements and icons with written indicators. Large symbol libraries contained in the solution help you create your banking system design in moments.
Example 3: Bank ATM Use Case Diagram
This diagram was created in ConceptDraw DIAGRAM using the Bank UML Communication Diagram library from the ATM UML Diagrams solution. An experienced user spent 15 minutes creating this sample.
Here is a basic example of a use case diagram; that is, a diagram that shows all possible transactions available to a user, and the relationship with each one. ConceptDraw DIAGRAM provides a visual platform for displaying your ATM solutions.
Example 4: Class UML Diagram for Bank
This diagram was created in ConceptDraw DIAGRAM using the Bank UML Class Diagram library from the ATM UML Diagrams solution. An experienced user spent 15 minutes creating this sample.
A class diagram is useful when presenting more complex system data, particularly in a hierarchical 'class' system. Actions, relationships and dependencies are portrayed effectively, and library icons can be customized and filled with text.
Example 5: OPC Runtime Refinement View
This diagram was created in ConceptDraw DIAGRAM using the Bank UML Component Diagram from the ATM UML Diagrams solution. An experienced user spent 20 minutes creating this sample.
An example that gives a small idea as to how technical and detailed a drawing it is possible to create. Thanks to the wide variety of professional elements found in the ATM UML Diagrams solution, your UML examples will be universally understood.
After ConceptDraw DIAGRAM is installed, the ATM UML Diagrams solution can be purchased either from the Software Development area
of ConceptDraw STORE itself or from our online store.
Thus, you will be able to use the ATM UML Diagrams solution straight after.
How to install
First of all, make sure that both ConceptDraw STORE and ConceptDraw DIAGRAM applications are downloaded and installed on your computer. Next, install the
ATM UML Diagrams solution from the ConceptDraw STORE to use it in the ConceptDraw DIAGRAM application.
Start using the ATM UML Diagrams solution to make the professionally looking software engineering diagrams by adding the design elements
taken from the stencil libraries and editing the pre-made examples that can be found there.
Since their introduction in the 1960s, Automated Teller Machines (ATMs) have become ubiquitous on the high streets, providing 24-hour access to the funds in your bank. An ATM can exist in various guises - as a 'hole in the wall' near banks or shops, or as a free-standing unit in a restaurant or club — but the transaction process for the customer remains similar in each case. They are required to insert an ATM card, and enter a Personal Identification Number (PIN), which are then checked by the bank. After approval at this stage, the customer has a number of banking options available to them, including cash withdrawal, balance enquiry, and money transfer. The card is returned to the user after all transactions are finished.
Before the software code for an ATM, or any other system design, is written, it is necessary to create a visual representation of any object-oriented processes. This is done most effectively by creating a Unified Modeling Language (UML) diagram, using object-oriented modeling. UML works as a general purpose modeling language for software engineers or system analysts, offering a number of different diagram styles with which to visually depict all aspects of a software system.
For an ATM, there are a number of different processes, transactions and interactions that can be mapped in this way using UML diagrams, or different views of the same process can be shown using different styles of modeling language. Broadly speaking, UML diagrams are divided into two types - structural diagrams (static modeling), and behavioral diagrams (dynamic modeling). In the case of an ATM, this allows you to show the system architecture and the interaction and relationships between objects and actors (e.g., customer and bank), or the changes to these objects depending on transaction (e.g. wrong PIN number entered).
You will also need to decide if you diagram will use an object-oriented analysis (OOA) approach, or object oriented design (OOD). The difference being that the aim of the first is to create a model of the system's functional requirements that is independent of implementation constraints. Using the latter, a developer applies implementation constraints to the conceptual model produced in object-oriented analysis.
OOA using UML diagrams
Types of UML structure diagram:
Use case diagram — A common method when object-oriented modeling is to present a system in the form of a use case (Fig 1.), which define interactions between the user (or 'actor') and a system, to achieve a specific goal.
Fig 1. A simple use case diagram
Class diagram — a class diagram allows you to group together certain transactions and objects into distinct 'classes', and display there attributes and possible interactions. You might define one class of an ATM system as 'Customer', another as 'Account', and the diagram shows the attributes of each and any available actions (Fig 2.).
Fig 2. Class UML diagram for bank
Composite structure diagram — this form of diagram can be used to map physical components of a structure and there collaboration with each other. A composite structure diagram of an ATM machine would show elements such as the keypad, receipt printer, processor and modem, and how they interact (Fig 3.).
Fig 3. ATM UML Composite structure diagram
Object diagrams — they show a 'snapshot' of a system, by modeling its objects and their relationships at a specific point in time. Each object represents an instance of a class from a class diagram, and several objects may be created from one class. For an ATM system, an object diagram could show several distinct Account objects side by side, illustrating that they are all part of the bank’s account database.
Package diagram — 'package' is a term for when classes or objects are grouped together, and the diagram shows their hierarchical structure (Fig 4.).
Fig 4. ATM UML Package diagram for bank
Types of UML behavioral diagrams:
State machine diagram — this describes the possible 'state' of a system dependent on inputs and interactions. A diagram for an ATM could show all possible states, active, idle, out of service, and what input is required to reach each one.
Activity diagram — describes a linear, step-by-step process, and the actions and decisions available within it. It isolates a particular workflow, such as the steps needed for a successful customer purchase transaction (Fig 5.)
Fig 5. Activity diagram for a customer purchase order
Interaction diagrams — these are a subset of behavioral diagrams that include sequence, timing, communication and interactive overview diagrams. In a general sense, they focus on the interaction between objects and classes, and how they communicate with each other.
For instance, and ATM sequence diagram will show object interactions arranged in chronological sequence (Fig 6.). A timing diagram will model the time constraints imposed on state changes. An interactive overview diagram can combine elements from other types of diagram (e.g. activity, sequence) to present a summary of control flow.
Fig 6. A sequence diagram showing the order of interaction between user, ATM, and bank
OOD using UML diagrams
Object-oriented design works in tandem with object-oriented analysis — while OOA documents the ideal form of a process or system, and its objects or interactions, OOD works on defining exactly what those objects are, and what elements are necessary for the process to work effectively. This can be done using the deployment and component forms of UML diagrams.
Deployment diagram. In the case of an ATM machine, a deployment diagram might show the runtime requirements of the system, memory requirements, or other devices the system needs to execute (Fig 7.).
Fig 7. ATM UML Development diagram for bank
Component diagram. A component diagram would show the particular elements that make up an object — so perhaps the physical components of an ATM machine, which itself can be a single element on an activity diagram, use case diagram etc (Fig 8.).
Fig 8. OPC Runtime Refinement View
Even in the case of a specialist subject such as ATM system modeling, it is possible to see the wide range of applications for UML diagrams and object-oriented modeling methods. ConceptDraw DIAGRAM diagramming software, enhanced and expanded with the ATM UML Diagrams solution, offers the full range of icons, templates and design elements needed to faithfully represent ATM and banking information system architecture using UML standards.
The ATM UML Diagrams solution is useful for beginner and advanced users alike — samples are provided to help you get started, and there is a wealth of tutorial material on the ConceptDraw website in the shape of videos and user guides. More experienced users will appreciate a full range of vector stencil libraries and ConceptDraw DIAGRAM 's powerful software, that allows you to create your ATM UML diagram in a matter of moments.