What is a Use Case Diagram?

Use cases are a set of actions, services, and functions that the system needs to perform
The purpose of a use case diagram in UML is to demonstrate the different ways that a user might
interact with a system.

Why Make Use Case Diagrams?

Use case diagrams are valuable for visualizing the functional requirements of a system that will
translate into design choices and development priorities.
They also help identify any internal or external factors that may influence the system and should
be taken into consideration.
They provide a good high level analysis from outside the system. Use case diagrams specify how
the system interacts with actors without worrying about the details of how that functionality is
implemented.

Use case diagram components | relationships

Visual
Notation Description
Representation

Actor
The users that interact with a system. An actor can be a person, an
organization, or an outside system that interacts with your application
or system. They must be external objects that produce or consume
data.
There are 2 types of actors
Primary Actors – who initiate a use case. E.g. – a person who
withdraw money from the ATM
Secondary Actors – who has involvement in a use case. E.g. - Server
Use Case

Horizontally shaped ovals that represent system function (process -

automated or manual)

Each Actor must be linked to a use case, while some use cases may
not be linked to actors.

Communication Link
A line between actors and use cases, it represent which actor is
interacting with which use case.

Boundary of system
Draw your system's boundaries using a rectangle that contains use
cases. Place actors outside the system's boundaries.
 Use Case Relationship Visual Representation

<<extend>> Print
Extends <-----------------
withdraw
It shows optional behavior. Receipt

Include
It shows mandatory behavior.

Generalization
A generalization relationship is a parent-child
relationship between use cases.
A generalization relationship is a parent-child
relationship between actors.
The child use case is an enhancement of the parent
use case.
Generalization is shown as a directed arrow with a
triangle arrowhead.
The child use case is connected at the base of the
arrow. The tip of the arrow is connected to the parent
use case.
Steps to create Use Case Diagram
1. Identify the actors.
2. Identify use cases
3. Identify include and extend use cases
4. Identify generalization
5. Identify relationship &
6. Draw system boundaries.

Tips for UML Use Case Diagrams

When thinking of use cases, think of the end goal of a user. They don't want to "login" or "sign
up." That's not a use case. The use case is more like "make a purchase."
Actors don't have names. They're not "Bob." They represent the role of someone interacting with
the system.
Keep your names short and the size of your use cases consistent for a professional look.