0% found this document useful (0 votes)
32 views26 pages

Lecture 2

The document discusses use case diagrams in UML modeling. It describes the elements of a use case diagram including systems, actors, use cases and relationships. It provides examples of how to represent these elements and relationships in a use case diagram.

Uploaded by

NINGA gaming
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
0% found this document useful (0 votes)
32 views26 pages

Lecture 2

The document discusses use case diagrams in UML modeling. It describes the elements of a use case diagram including systems, actors, use cases and relationships. It provides examples of how to represent these elements and relationships in a use case diagram.

Uploaded by

NINGA gaming
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/ 26

Software Engineering

Lecture 2

[These slides are adapted from Software Engineering: A Practitioner’s Approach, Roger S.
Pressman © 2015 & Software Engineering, Ian Somerville © 2015 ]
INTRODUCTION TO UML USE CASE DIAGRAMS
Unified Modeling Language (UML)
The Unified Modeling Language (UML) is a widely used method of visualizing and documenting software systems design or
information system design. During requirement modelling, a system analyst can utilize the UML to represent the information system
from a user’s view point.
Why UML for Modeling
• Use graphical notation to communicate more clearly than natural language (imprecise)
and code(too detailed).

• Help acquire an overall view of a system.

• UML is not dependent on any one language or technology.

• UML moves us from fragmentation to standardization.


Types of UML Diagrams
Use Case Diagram

Class Diagram

Sequence Diagram

Collaboration Diagram

State Transition Diagram etc.


UML - Use Case Diagrams
• Use Case Diagrams capture requirements. Clarify exactly what the
system is supposed to do. Displays the relationship among actors and use
cases. Different from traditional flow chart.

• Use Case Diagrams are defined as diagrams that capture the system’s
functionality and requirement.

• In UML, use-case diagrams model the behavior of a system and help to


capture the requirements of the system. Use-case diagrams describe the
high-level functions and scope of a system. These diagrams also identify the
interactions between the system and its actors.

• Behavior is how someone acts.


Use Case Diagram

Elements of Use Case Diagrams

✓ Systems
✓ Actors
✓ Use Cases
✓ Relationships
Use Case Diagram

Systems
Website
Software Design
Application
Business Process
Etc.
Use Case Diagram

Actors
An actor is a person, organization, or external system that plays a role in one
or more interactions with your system

An actor, initiates a use case by requesting the system to perform a function


or process.

Primary Actor (initiates the use of the system)

Secondary Actor (Reactionary)


Primary Actor Secondary Actor
Use Case Diagram

Use Case
Represents an action that accomplishes some sort of task
within the system.

Example:
Banking application is going to allow a Customer to log in, check their balances,
transfer funds between accounts, and make payments towards bills.
Use Case Diagram
Use Case Diagram

Relationships
(Association)

Communication between an actor and a use case;


represented by a solid line.
Relationships

Generalization: It is a relationship between two


entities such that one entity (child) inherits the
functionality of another entity (parent). It can exist
between two actors or two use cases. It is
represented by an arrow in the direction of the
parent use case or actor.

Represented by a line with a triangular arrow head


toward the parent use case.
Use Case Diagram

Relationships

Extend Include

Optional behavior Mandatory

- Base Use Case is - Base Use Case is


complete by itself incomplete by itself

- Extended Use Case is - Included Use Case is


an optional required
Use Case Diagram
Use Case Diagram
Use Case Diagram

Someone can:
- Withdraw the
amount

- Check balance

- Reset Pin

- Maintenance
Use Case Diagram
Use Case Diagram

Include: a dotted line labeled <<include>> beginning at base use case and ending with an arrows
pointing to the include use case. An “Include” relationship is used to indicate that a particular Use Case
must include another use case to perform its function.
<<include>>

Extend: a dotted line labeled <<extend>> with an arrow toward the base case. The extending use case
may add behavior to the base use case. The base class declares “extension points”.

<<extend>>
BANK ATM USE CASE
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.
BANK ATM USE CASE
Draw a use case diagram for the following problem:

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


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.
Thank you

You might also like