LAB Assignments

05/06/09-02-2024
• Draw a User Interaction Function
for ATM System
• Use case model for ATM
Management System
• Class Diagram for ATM
Management System
• DFD Model for ATM Management
System
Use Case
Diagram
• Use Case Diagram
• Use case
Relationships
• Included use
cases
• Use Case Controllers
• Extended Use Cases
• Generalization
• Using Abstract Use
Cases
Design Model for Use Case Controllers
• Lifeline is depicted in a rectangle called head with its
name and type.
• The head is located on top of a vertical dashed line
(referred to as the stem).
• A lifeline portrays an object internal to the system
whereas actors depict objects external to the system.
Arrow directed towards a lifeline from an end point (unknow source) – failure message, system
crash or hardware failure
The warning might be generated for the user or other software/object that the lifeline is interacting with.
Since the destination is not known before hand, the Lost Message symbol is used.
• They are used when we need to restrict the flow of messages on the pretext of a condition being met. Guards
play an important role in letting software developers know the constraints attached to a system or a particular
process.
• To withdraw cash, having a balance greater than zero is a condition that must be met as shown below.
How to draw Sequence Diagrams?
• Identify the Scenario • Time and order
• List the participants • Conditions and loops
• Define lifelines • Parallel Execution
• Arrange lifelines • Review and Refine
• Add activation bars • Annotations and comments
• Draw messages • Documentations and Constraints
• Return Messages • Tools
• Sequence Diagram
• Collaborative Diagram
for ATM
Visibility
provides
Access
Rights
Parameter
Directionality
Perspectives of Class Diagram
Relationship between Classes
Inheritance
Cardinality
Aggregation The relationship is displayed as a solid line with
an unfilled diamond at the association end,
which is connected to the class that represents
the aggregate.

Composition Composition is displayed as a solid line with a

filled diamond at the association end, which is
connected to the class that represents the
whole or composite.

Dependency The relationship is displayed as a dashed line

with an open arrow.

Realization The Owner interface might specify methods for

acquiring property and disposing of property.
The Person and Corporation classes need to
implement these methods, possibly in very
different ways.
Class Diagram of Order System
GUI Interaction
Class
Diagram for
ATM
Design
elements in
DFD Diagram
Design elements
in DFD Diagram

Yourdon and
Coad Notation
Design elements
in DFD Diagram

Gane-Sarson
Notation
Logical Data Flow Diagram Example:
Grocery Store
Bank Account Data Flow Diagram
Physical Data Flow Diagram
Example: Grocery Store
Data Flow Diagram: Purchase
Management System
Data Flow Diagram: ECommerce
System
Student
Registration
System
• The ATM machine system DFD consists of DFD levels 0, 1, and 2. It uses entities, processes, and data to define the
whole system.
• DFD is not a UML Diagrams, but they complement each other in explaining the project activities, behaviors,
interactions, and structure.
• DFD also describes the steps involved in transferring data from one process to another.
• Advantages of the Data Flow Diagram :
•Visualization of system contents.
•Included in the system documentation file.
•Simple to grasp and understood by both programmers and users.
•Detailing of system components
•It also aids in comprehending a system’s operation and limitations.
DFD of ATM System Level 0

Transaction Details

0.0
User Info
ATM System ATM User

Confirmation Details
 1.1 1.2
Transaction
Manage Information Manage
Customer Transaction
Data Flow Diagram Level 1 of ATM Information Information
System
• The “detonated view” of the context
diagram is DFD Level 1 Customers
• Deepens the concept derived from the
Confirmation
context diagram Customer Information Details
• Specifically, level 1 shows the broader
details of ATM System DFD Level 0.
• This is to clarify the paths (flow) of data
and its transformation from input to 1.3
Cash and Receipts Confirmation Details
output. Release Cash
and Receipts
 Customer Information
2.2
Transaction
Manage
2.1 Information
Transaction
Customers
Data Flow Diagram Manage Information
Database
Level 2 of ATM Customer
Information
System Customers
Confirmation
• Highest abstraction
Details

Information
Transaction
of the data flow
diagram.
• This level broadens Customer Information
the idea from the Confirmation
DFD level 1. 2.3 Details
• It includes the sub- Cash and Receipts
processes from level
Release Cash Update
and Receipts
1 as well as the data
Transaction
that flows. Database
Confirmed Transaction