by

Use Case Diagram N.Aravindhraj,

AP/CSE
Sun Up Meeting
• Use Case Model
– Actors
– Scenarios
– Use Case
• Types and Formats
• Steps
• NextGen POS System Use Case Document
Agenda
• Components of Use Case Diagram
– Use Case
– Actors
– Relationships
• Includes
• Extends
• Generalization
• Example Use Case Diagrams
Three Main Components
• Use Case
• Actors
• Relationships
Use Case
• Use cases are used during requirements elicitation and analysis
to represent the functionality of the system.
• Use cases focus on the behavior of the system from an external
point of view.
• A use case describes a function provided by the system that
yields a visible result for an actor.
• Use case diagrams represent the functionality of the system
from a user’s point of view. They define the boundaries of the
system Use case
Actors
• Actors are external entities that interact with the system.
Examples of actors include a user role (e.g., a system
administrator, a bank customer, a bank teller) or another
system (e.g., a central database, a fabrication line).
• Actors have unique names and descriptions.
• The actors are outside the boundary of the system,
whereas the use cases are inside the boundary of the
system.
Relationships
• Actors and use cases communicate when information
is exchanged between them.
• Communication relationships are depicted by a solid
line between the actor and use case symbol.
• includes
• extends
Relationships - Includes
• Use case include is a directed relationship between two use cases which is used to show that
behavior of the included use case (the addition) is inserted into the behavior of
the including (the base) use case.
• Include relationship between use cases is shown by a dashed arrow with an open arrowhead
from the including (base) use case to the included (common part) use case. The arrow is
labelled with the keyword «include».
Relationships - Extends
• Extend is a directed relationship that specifies how and when the behaviour defined in usually
supplementary (optional) extending use case can be inserted into the behaviour defined in
the extended use case.
• Extend relationship is shown as a dashed line with an open arrowhead directed from the extending
use case to the extended (base) use case. The arrow is labelled with the keyword «extend».
Difference between includes and extends
• "Include" is used to extend the base use case and it is a must condition i.e.
included use case run must run successfully to complete base use.
– e.g. Consider a case of Email Service, here "Login" is a included use case
which must be run in order to send a Email (Base use case)

• "Exclude" on the other hand is optional use case which extends the base use
case, base use case can run successfully even without invoking/calling the
extending use case.
– e.g. Consider "Laptop Purchase" as base use case and "Additional Warranty"
as extending use case, here you can run base use case "Laptop Purchase"
even without taking additional warranty.
Generalization
• In UML modeling, a generalization relationship is a
relationship in which one model element (the child) is
based on another model element (the parent).
• Generalization relationships are used in class,
component, deployment, and use-case diagrams to
indicate that the child receives all of the attributes,
operations, and relationships that are defined in the
parent.
Sun Down Meeting

?
Thank you