Scribd
Upload
112 views15 pages

Use Case Diagrams

The document introduces use case diagrams and their components: 1) Actors represent anything that interacts with the system and are shown as stick figures. 2) Use cases describe a system's functionality from an actor's perspective as ovals. 3) A use case diagram visually depicts the relationships between actors and use cases through associations. It is used to model a system's context and requirements. The example use case diagram models the functionality of an ATM system with actors like customers and operators. Use cases include transactions like withdrawals while dependencies show extended and included behaviors.

Uploaded by

Razeen Ramzy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
112 views15 pages

Use Case Diagrams

The document introduces use case diagrams and their components: 1) Actors represent anything that interacts with the system and are shown as stick figures. 2) Use cases describe a system's functionality from an actor's perspective as ovals. 3) A use case diagram visually depicts the relationships between actors and use cases through associations. It is used to model a system's context and requirements. The example use case diagram models the functionality of an ATM system with actors like customers and operators. Use cases include transactions like withdrawals while dependencies show extended and included behaviors.

Uploaded by

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

Use Case Diagrams

1
Objectives
• To introduce use case diagrams

– Actors

– Use cases

– Dependency relationships between use cases


Actors
• An actor is anyone or anything that must interact
with the system.

• Actors are NOT part of the system

• In the UML, an actor is represented as a


stickman.
Use Cases
• A use case is a description of a set of sequences of
actions, including variants, that a system performs to
yield an observable result of value to an actor.

• A use case describes what a system does but it does not


specify how it does it.

• A use case typically represents a major piece of


functionality that is complete from beginning to end.
Use Cases (Cont’d)
• A use case must deliver something of value to an actor.

• The collection of use cases for a system constitute all


the defined ways the system may be used.

• In the UML, a use case is represented as an oval.


Use Case Diagrams
• A use case diagram is a diagram that shows a set of use cases
and actors and their relationships.

• Actors may be connected to use cases only by association.

• An association between an actor and a use case indicates that


the actor and the use case communicate with one another, each
one possibly sending and receiving messages.

• Use case diagrams are used to …


– Model the context of a system.
– Model the requirements of a system
ATM: Problem Description
• A bank has several automated teller machines (ATMs), which are
geographically distributed and connected via a wide area network to
a central server. Each ATM machine has a card reader, a cash
dispenser, a keyboard/display, and a receipt printer. By using the
ATM machine, a customer can withdraw cash from either a
checking or savings account, query the balance of an account, or
transfer funds from one account to another. A transaction is initiated
when a customer inserts an ATM card into the card reader.
Encoded on the magnetic strip on the back of the ATM card are the
card number, the start date, and the expiration date. Assuming the
card is recognized, the system validates the ATM card to determine
that the expiration date has not passed, that the user-entered PIN
(personal identification number) matches the PIN maintained by the
system, and that the card is not lost or stolen. The customer is
allowed three attempts to enter the correct PIN; the card is
confiscated if the third attempt fails. Cards that have been reported
lost or stolen are also confiscated.
ATM: Problem Description
(Cont’d)
• If the PIN is validated satisfactorily, the customer is prompted for a
withdrawal, query, or transfer transaction. Before a withdrawal
transaction can be approved, the system, determines that sufficient
funds exist in the requested account, that the maximum daily limit
will not be exceeded, and that there are sufficient funds at the local
cash dispenser. If the transaction is approved, the requested
amount of cash is dispensed, a receipt is printed containing
information about the transaction, and the card is ejected. Before a
transfer transaction can be approved, the system determines that
the customer has at least two accounts and that there are sufficient
funds in the account to be debited. For approved query and transfer
requests, a receipt is printed and the card is ejected. A customer
many cancel a transaction at any time; the transaction is terminated
and the card is ejected. Customer records, account records, and
debit card records are all maintained at the server.
ATM: Problem Description
(Cont’d)
• An ATM operator may start up and close down
the ATM to replenish the ATM cash dispenser
and for routine maintenance. It is assumed that
functionally to open and close accounts and to
create, update, and delete customer and debit
card records is provided by an existing system
and is not part of this problem.
ATM System
ATM: Use Case Model
Dependency Relationships
between Use Cases
• extend
– Specifies that the target use case extends the
behavior of the source use case.

• include
– Specifies that the source use case explicitly
incorporates the behavior of another use case
at a location specifies by the source.
ATM: Use Case Model
Cell Phone System
Cell Phone System: Use Case
Model

You might also like