Scribd
Upload
570 views

Atm Uml Diagram

An ATM allows bank customers to access financial transactions without a bank teller. Customers can check balances, deposit funds, withdraw cash, and transfer funds using their bank card and PIN. An ATM technician provides maintenance and repairs. The diagram shows the relationships between customers, the bank, and the ATM for different transactions.

Uploaded by

Mintesinot Melese
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
570 views

Atm Uml Diagram

An ATM allows bank customers to access financial transactions without a bank teller. Customers can check balances, deposit funds, withdraw cash, and transfer funds using their bank card and PIN. An ATM technician provides maintenance and repairs. The diagram shows the relationships between customers, the bank, and the ATM for different transactions.

Uploaded by

Mintesinot Melese
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

An automated teller machine (ATM) or the automatic banking machine (ABM) is a banking

subsystem (subject) that provides bank customers with access to financial transactions in a
public space without the need for a cashier, clerk, or bank teller.
Customer (actor) uses bank ATM to Check Balances of his/her bank accounts, Deposit
Funds, Withdraw Cash and/or Transfer Funds (use cases). ATM
Technician provides Maintenance and Repairs. All these use cases also involve Bank actor
whether it is related to customer transactions or to the ATM servicing.

An example of use case diagram for Bank ATM subsystem - top level use cases.
On most bank ATMs, the customer is authenticated by inserting a plastic ATM card and entering
a personal identification number (PIN). Customer Authentication use case is required for every
ATM transaction so we show it as include relationship. Including this use case as well as
transaction generalizations make the ATM Transaction an abstract use case.
Bank ATM Transactions and Customer Authentication Use Cases Example.
Customer may need some help from the ATM. ATM Transaction use case
is extended via extension point called menu by the ATM Help use case whenever ATM
Transaction is at the location specified by the menu and the bank customer requests help, e.g.
by selecting Help menu item.

Bank ATM Maintenance, Repair, Diagnostics Use Cases Example.


ATM Technician maintains or repairs Bank ATM. Maintenance use case
includes Replenishing ATM with cash, ink or printer paper, Upgrades of hardware, firmware or
software, and remote or on-site Diagnostics. Diagnostics is also included in (shared
with) Repair use case.
Hospital Management
UML Class Diagram Example
This is an example of a hospital domain model diagram. The domain model for the Hospital
Management System is represented by several class diagrams. The purpose of the diagram
is to show and explain hospital structure, staff, relationships with patients, and patient
treatment terminology.
On the diagram below a Person could be associated with different Hospitals, and a Hospital
could employ or serve multiple Persons. Person class has derived
attributes name and homeAddress. Name represents full name and could be combined from
title, given (or first) name, middle name, and family (or last) name. Patient class has derived
attribute age which could be calculated based on her or his birth date and current date or
hospital admission date.
The Patient class inherits attributes from the Person class. Several inherited
attributes name, gender, and birthDate are shown with prepended caret '^' symbol (new
notation introduced in UML 2.5).
Class diagram is a graph of classifier elements connected by their various static relationships. A “class”
diagram may also contain interfaces, packages, relationships, and even instances,
such as objects and links. Perhaps a better name would be “static structural diagram”, but “class diagram”
is shorter and well established.

Object diagram on the other hand is a graph of instances, including objects and data values. A static
object diagram is an instance of a class diagram. It shows a snapshot of the detailed state of a system at a
point in time. The use of object diagrams is fairly limited, mainly to show examples of data structures.

The actual differences lie in their purpose. A Class diagram shows your classes and their relationships.
An Object Model Diagram shows the interaction between objects at some point, during run time.

A Class Diagram will show what the Objects in your system consist of (members) and what they are
capable of doing (methods) mostly static. In contrast, an Object Diagram will show how objects in your
system are interacting with each other at some point in time, and what values those objects contain when
the program is in this state.

class diagram is a graph of Classifier elements connected by their various static


relationships. Note that a “class” diagram may also contain interfaces, packages,
relationships, and even instances, such as objects and links. Perhaps a better name would
be “static structural diagram”, but “class diagram” is shorter and well established.

object diagram

is a graph of instances, including objects and data values. A static object diagram is an
instance of a class diagram; it shows a snapshot of the detailed state of a system at a point
in time. The use of object diagrams is fairly limited, mainly to show examples of data
structures.

In simple words...

Class diagram shows a collection of declarative (static) model elements, such as classes, types, and
their contents and relationships.

Object diagram encompasses objects and their relationships at a point in time. It may be considered a
special case of a class diagram or a collaboration diagram.
class diagram

object diagram
Difference between object diagram and class diagram

A Class Diagram will show what the Objects in your system consist of (members) and what
they are capable of doing (methods).

In contrast, an Object Diagram will show how objects in your system are interacting with
each other at some point in time, and what values those objects contain when the program
is in this state.

You might also like