SlideShare a Scribd company logo
Lab 3: Use case diagram
Sec A, D, E.
Instructor
Farah Ahmed
Agenda / Topics
• UML diagram
• Type of UML diagram
• Use case diagram
• Use case scenario
• Purpose of Use case diagram
• Example of Use case diagram
• Conclusion
UML diagram
• UML stands for Unified Modeling Language. It’s a rich language to
model software solutions, application structures, system
behavior and business processes.
• A UML diagram is a diagram based on the UML (Unified Modeling
Language) with the purpose of visually representing a system
along with its main actors, roles, actions, artifacts or classes, in
order to better understand, alter, maintain, or document
information about the system.
• There are 14 UML diagram types to help you model these
behaviors.
List of UML diagram
So what are the different UML
diagram types? There are two main
categories; structure
diagrams and behavioral diagrams.
Structure Diagrams
Class Diagram
Component Diagram
Deployment Diagram
Object Diagram
Package Diagram
Profile Diagram
Composite Structure Diagram
Behavioral Diagrams
Use Case Diagram
Activity Diagram
State Machine Diagram
Sequence Diagram
Communication Diagram
Interaction Overview Diagram
Timing Diagram
Categories of
UML diagram
Structure diagrams show the things
in the modeled system. In a more
technical term, they show different
objects in a system.
Behavioral diagrams show what
should happen in a system. They
describe how the objects interact
with each other to create a
functioning system.
List of UML diagram
UML diagram
The most frequently used ones in software
development are:
• Use Case diagrams,
• Class diagrams, and
• Sequence diagrams.
Use case diagram
An Overview of Modeling Use Case
Diagram
• Use-case diagrams present a high-level view of
system usage as viewed from an outsider's (actor's)
perspective.
• These diagrams show the functionality of a system
or a class and how the system interacts with the
outside world.
• Use-case diagrams can be used during analysis to
capture the system requirements and to
understand how the system should work.
• During the design phase, use-case diagrams specify
the behavior of the system as implemented.
a Use case
diagram
A UML use case diagram is the primary form of
system/software requirements for a new software
program underdeveloped.
Use cases specify the expected behavior (what),
and not the exact method of making it happen
(how).
Use cases once specified can be denoted both
textual and visual representation (i.e. use case
diagram).
A key concept of use case modeling is that it helps
us design a system from the end user's perspective.
It is an effective technique for communicating
system behavior in the user's terms by specifying all
externally visible system behavior.
Purpose of a use case diagram
Specify the
context of a
system
Capture the
requirements of
a system
•Validate a
systems
architecture
Drive
implementation
and generate
test cases
Developed by
analysts
together with
domain experts
Use case diagrams are typically developed in the early stage of development and people often apply use case modeling for the
following purposes:
Use Case Diagram at a Glance
A standard form of use case diagram is defined in the
Unified Modeling Language in the Use Case Diagram
example:
Use Case Diagram at a Glance
Actor
• Someone interacts with use case (system function).
• Named by noun.
• Actor plays a role in the business
• Similar to the concept of user, but a user can play
different roles
• For example:
• A prof. can be instructor and also researcher
• plays 2 roles with two systems
• Actor triggers use case(s).
• Actor has a responsibility toward the system (inputs),
and Actor has expectations from the system (outputs).
Use case Diagram
Use Case
• System function (process - automated or
manual)
• Named by verb + Noun (or Noun Phrase).
• i.e. Do something
• Each Actor must be linked to a use case,
while some use cases may not be linked to
actors.
Use case Diagram
Communication Link
•The participation of an actor in
is shown by connecting an actor
case by a solid link.
•Actors may be connected to use
associations, indicating that the
the use case communicate with
using messages.
Use case Diagram
Boundary of system
• The system boundary is potentially the entire
system as defined in the requirements
document.
• For large and complex systems, each module
may be the system boundary.
• For example, for an ERP system for an
organization, each of the modules such as
personnel, payroll, accounting, etc.
• can form a system boundary for use cases
specific to each of these business functions.
• The entire system can span all of these modules
depicting the overall system boundary
Structuring
Use Case
Diagram with
Relationships
• Use cases share different kinds of relationships.
Defining the relationship between two use cases is
the decision of the software analysts of the use case
diagram. A relationship between two use cases is
basically modeling the dependency between the two
use cases. The reuse of an existing use case by using
different types of relationships reduces the overall
effort required in developing a system.
Use case relationship
Extends
•Indicates that an "Invalid Password" use case
may include (subject to specified in the
extension) the behavior specified by base use
case "Login Account".
•Depict with a directed arrow having a dotted
line. The tip of arrowhead points to the base
use case and the child use case is connected at
the base of the arrow.
•The stereotype "<<extends>>" identifies as an
extend relationship
Use case relationship
Include
• When a use case is depicted as using the functionality of another
use case, the relationship between the use cases is named as include
or uses relationship.
• A use case includes the functionality described in another use case
as a part of its business process flow.
• A uses relationship from base use case to child use case indicates
that an instance of the base use case will include the behavior as
specified in the child use case.
• An include relationship is depicted with a directed arrow having a
dotted line. The tip of arrowhead points to the child use case and the
parent use case connected at the base of the arrow.
• The stereotype "<<include>>" identifies the relationship as an
include relationship.
Use case relationship
Generalization
•A generalization relationship is a parent-child
relationship between use cases.
•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.
Example of Use Case
Diagram
Use Case Example - Association
Link
• A Use Case diagram illustrates
a set of use cases for a system,
i.e. the actors and the
relationships between the
actors and use cases.
Example of Use Case
Diagram
Use Case Example - Include
Relationship
• The include relationship adds
additional functionality not
specified in the base use case.
The <<Include>> relationship is
used to include common
behavior from an included use
case into a base use case in
order to support the reuse of
common behavior.
Example of Use Case
Diagram
Use Case Example - Extend
Relationship
• The extend relationships are
important because they show
optional functionality or system
behavior.
• The <<extend>> relationship is
used to include optional behavior
from an extending use case in an
extended use case.
• Look at the use case diagram
example. It shows an extend
connector and an extension point
"Search".
Example of Use Case
Diagram
Use Case Example -
Generalization Relationship
• A generalization relationship
means that a child use case
inherits the behavior and
meaning of the parent use case.
The child may add or override
the behavior of the parent.
• The figure provides a use case
example by showing two
generalization connectors that
connect between the three use
cases.
Example of Use Case Diagram – Vehicle Sales Systems
As you can see even a
system as big as a vehicle
sales system contains not
more than 10 use cases!
That's the beauty of use
case modeling.
How to identify actor?
Often, people find it easiest to start the requirements elicitation process by identifying the actors. The
following questions can help you identify the actors of your system (Schneider and Winters - 1998):
• Who uses the system?
• Who installs the system?
• Who starts up the system?
• Who maintains the system?
• Who shuts down the system?
• What other systems use this system?
• Who gets information from this system?
• Who provides information to the system?
• Does anything happen automatically at a present time?
How to identify Use Cases?
Identifying the Use Cases, and then the scenario-based elicitation process carries on by asking what
externally visible, observable value that each actor desires. The following questions can be asked to
identify use cases, once your actors have been identified (Schneider and Winters - 1998):
• What functions will the actor want from the system?
• Does the system store information? What actors will create, read, update or delete this information?
• Does the system need to notify an actor about changes in the internal state?
• Are there any external events the system must know about? What actor informs the system of those
events?
Use case scenario
What is a use case scenario
A use case represents the actions
that are required to enable or
abandon a goal. A use case has
multiple “paths” that can be taken
by any user at any one time. A use
case scenario is a single path
through the use case.
A use case defines all of the paths that lead to the success of
the use case.The use case also defines all the paths that lead
to the abandonment of the use case without achieving its goal.
Each unique combination of those paths that can be taken by
an actor during a single “pass” through the use case is a use
case scenario.
When do you use each
construct?
• A scenario is an actual sequence of interactions
(i.e., an instance) describing one specific situation;
a use case is a general sequence of interactions (i.e.,
a class) describing all possible scenarios
associated with a situation.

More Related Content

PPT
Use Case Diagram
PDF
Use case diagrams
PPT
Usecase Presentation
PPTX
Presentation Use Case Diagram and Use Case Specification.pptx
PPT
Uml diagrams
PDF
CS8592-OOAD Lecture Notes Unit-3
PPTX
Ch5- Software Engineering 9
PPT
Use case Diagram
Use Case Diagram
Use case diagrams
Usecase Presentation
Presentation Use Case Diagram and Use Case Specification.pptx
Uml diagrams
CS8592-OOAD Lecture Notes Unit-3
Ch5- Software Engineering 9
Use case Diagram

What's hot (20)

PPT
Flow oriented modeling
PPT
Unit 1( modelling concepts & class modeling)
PPT
Use Case Diagram
PPT
Slides chapter 3
PPT
Requirement analysis and specification, software engineering
PPT
Software Prototyping
PPTX
Use case diagram
PDF
Object diagram
PDF
Requirement engineering process
PPT
SE CHAPTER 2 PROCESS MODELS
PPT
System Models in Software Engineering SE7
PPTX
PPT
Slides chapters 13-14
PPT
UML Architecture and Views
PPTX
Ch7-Software Engineering 9
PDF
Software Engineering : OOAD using UML
PPT
10 component diagram
PPT
5- Requirement.ppt
PDF
Architecture Design in Software Engineering
PPTX
Uml Presentation
Flow oriented modeling
Unit 1( modelling concepts & class modeling)
Use Case Diagram
Slides chapter 3
Requirement analysis and specification, software engineering
Software Prototyping
Use case diagram
Object diagram
Requirement engineering process
SE CHAPTER 2 PROCESS MODELS
System Models in Software Engineering SE7
Slides chapters 13-14
UML Architecture and Views
Ch7-Software Engineering 9
Software Engineering : OOAD using UML
10 component diagram
5- Requirement.ppt
Architecture Design in Software Engineering
Uml Presentation
Ad

Similar to Lab 3 Introduction to the UML - how to create a use case diagram (20)

PPT
05 use case
PPTX
Use Case Modeling In UML
PPTX
Lesson02_Use Case Diagrams
PPTX
Use Case Diagram.pptx
PDF
Use case diagrams
PPT
Uml diagrams usecase
PPTX
Lecture#04, use case diagram
PPTX
Lecture no 8 use case modeling and use case diagrams
PDF
Lecture 3 cst205 cst281-oop
PPTX
Use case modeling & analysis v 1
PPTX
Use Case Modelling.pptx
PPTX
USE case diagrams.ppt.pptx..............
PPTX
Basic Behavioral Modeling
PPT
Use case modeling
PDF
UseCaseDiagrams.pdf shhsja whuwbwnwhwywbw
PPT
Lect_07_Use Case Diagram.ppt use case diagram
PDF
use case diagram
PPTX
usecase (1).pptx
PPTX
unit-3-Interactions&Usecases.pptxunit-3-Interactions&Usecases.pptx
PPTX
Use Case
05 use case
Use Case Modeling In UML
Lesson02_Use Case Diagrams
Use Case Diagram.pptx
Use case diagrams
Uml diagrams usecase
Lecture#04, use case diagram
Lecture no 8 use case modeling and use case diagrams
Lecture 3 cst205 cst281-oop
Use case modeling & analysis v 1
Use Case Modelling.pptx
USE case diagrams.ppt.pptx..............
Basic Behavioral Modeling
Use case modeling
UseCaseDiagrams.pdf shhsja whuwbwnwhwywbw
Lect_07_Use Case Diagram.ppt use case diagram
use case diagram
usecase (1).pptx
unit-3-Interactions&Usecases.pptxunit-3-Interactions&Usecases.pptx
Use Case
Ad

Recently uploaded (20)

PDF
Automation-in-Manufacturing-Chapter-Introduction.pdf
PDF
Model Code of Practice - Construction Work - 21102022 .pdf
PPTX
Infosys Presentation by1.Riyan Bagwan 2.Samadhan Naiknavare 3.Gaurav Shinde 4...
PDF
Mohammad Mahdi Farshadian CV - Prospective PhD Student 2026
PPTX
M Tech Sem 1 Civil Engineering Environmental Sciences.pptx
PPT
Project quality management in manufacturing
PPTX
KTU 2019 -S7-MCN 401 MODULE 2-VINAY.pptx
PPTX
FINAL REVIEW FOR COPD DIANOSIS FOR PULMONARY DISEASE.pptx
PPTX
Welding lecture in detail for understanding
PPTX
Geodesy 1.pptx...............................................
PPTX
OOP with Java - Java Introduction (Basics)
PDF
The CXO Playbook 2025 – Future-Ready Strategies for C-Suite Leaders Cerebrai...
PPTX
CYBER-CRIMES AND SECURITY A guide to understanding
PDF
Digital Logic Computer Design lecture notes
PPTX
Foundation to blockchain - A guide to Blockchain Tech
PPTX
bas. eng. economics group 4 presentation 1.pptx
PPTX
CH1 Production IntroductoryConcepts.pptx
DOCX
573137875-Attendance-Management-System-original
PDF
composite construction of structures.pdf
PPTX
Sustainable Sites - Green Building Construction
Automation-in-Manufacturing-Chapter-Introduction.pdf
Model Code of Practice - Construction Work - 21102022 .pdf
Infosys Presentation by1.Riyan Bagwan 2.Samadhan Naiknavare 3.Gaurav Shinde 4...
Mohammad Mahdi Farshadian CV - Prospective PhD Student 2026
M Tech Sem 1 Civil Engineering Environmental Sciences.pptx
Project quality management in manufacturing
KTU 2019 -S7-MCN 401 MODULE 2-VINAY.pptx
FINAL REVIEW FOR COPD DIANOSIS FOR PULMONARY DISEASE.pptx
Welding lecture in detail for understanding
Geodesy 1.pptx...............................................
OOP with Java - Java Introduction (Basics)
The CXO Playbook 2025 – Future-Ready Strategies for C-Suite Leaders Cerebrai...
CYBER-CRIMES AND SECURITY A guide to understanding
Digital Logic Computer Design lecture notes
Foundation to blockchain - A guide to Blockchain Tech
bas. eng. economics group 4 presentation 1.pptx
CH1 Production IntroductoryConcepts.pptx
573137875-Attendance-Management-System-original
composite construction of structures.pdf
Sustainable Sites - Green Building Construction

Lab 3 Introduction to the UML - how to create a use case diagram

  • 1. Lab 3: Use case diagram Sec A, D, E. Instructor Farah Ahmed
  • 2. Agenda / Topics • UML diagram • Type of UML diagram • Use case diagram • Use case scenario • Purpose of Use case diagram • Example of Use case diagram • Conclusion
  • 3. UML diagram • UML stands for Unified Modeling Language. It’s a rich language to model software solutions, application structures, system behavior and business processes. • A UML diagram is a diagram based on the UML (Unified Modeling Language) with the purpose of visually representing a system along with its main actors, roles, actions, artifacts or classes, in order to better understand, alter, maintain, or document information about the system. • There are 14 UML diagram types to help you model these behaviors.
  • 4. List of UML diagram So what are the different UML diagram types? There are two main categories; structure diagrams and behavioral diagrams. Structure Diagrams Class Diagram Component Diagram Deployment Diagram Object Diagram Package Diagram Profile Diagram Composite Structure Diagram Behavioral Diagrams Use Case Diagram Activity Diagram State Machine Diagram Sequence Diagram Communication Diagram Interaction Overview Diagram Timing Diagram
  • 5. Categories of UML diagram Structure diagrams show the things in the modeled system. In a more technical term, they show different objects in a system. Behavioral diagrams show what should happen in a system. They describe how the objects interact with each other to create a functioning system.
  • 6. List of UML diagram
  • 7. UML diagram The most frequently used ones in software development are: • Use Case diagrams, • Class diagrams, and • Sequence diagrams.
  • 9. An Overview of Modeling Use Case Diagram • Use-case diagrams present a high-level view of system usage as viewed from an outsider's (actor's) perspective. • These diagrams show the functionality of a system or a class and how the system interacts with the outside world. • Use-case diagrams can be used during analysis to capture the system requirements and to understand how the system should work. • During the design phase, use-case diagrams specify the behavior of the system as implemented.
  • 10. a Use case diagram A UML use case diagram is the primary form of system/software requirements for a new software program underdeveloped. Use cases specify the expected behavior (what), and not the exact method of making it happen (how). Use cases once specified can be denoted both textual and visual representation (i.e. use case diagram). A key concept of use case modeling is that it helps us design a system from the end user's perspective. It is an effective technique for communicating system behavior in the user's terms by specifying all externally visible system behavior.
  • 11. Purpose of a use case diagram Specify the context of a system Capture the requirements of a system •Validate a systems architecture Drive implementation and generate test cases Developed by analysts together with domain experts Use case diagrams are typically developed in the early stage of development and people often apply use case modeling for the following purposes:
  • 12. Use Case Diagram at a Glance A standard form of use case diagram is defined in the Unified Modeling Language in the Use Case Diagram example:
  • 13. Use Case Diagram at a Glance Actor • Someone interacts with use case (system function). • Named by noun. • Actor plays a role in the business • Similar to the concept of user, but a user can play different roles • For example: • A prof. can be instructor and also researcher • plays 2 roles with two systems • Actor triggers use case(s). • Actor has a responsibility toward the system (inputs), and Actor has expectations from the system (outputs).
  • 14. Use case Diagram Use Case • System function (process - automated or manual) • Named by verb + Noun (or Noun Phrase). • i.e. Do something • Each Actor must be linked to a use case, while some use cases may not be linked to actors.
  • 15. Use case Diagram Communication Link •The participation of an actor in is shown by connecting an actor case by a solid link. •Actors may be connected to use associations, indicating that the the use case communicate with using messages.
  • 16. Use case Diagram Boundary of system • The system boundary is potentially the entire system as defined in the requirements document. • For large and complex systems, each module may be the system boundary. • For example, for an ERP system for an organization, each of the modules such as personnel, payroll, accounting, etc. • can form a system boundary for use cases specific to each of these business functions. • The entire system can span all of these modules depicting the overall system boundary
  • 17. Structuring Use Case Diagram with Relationships • Use cases share different kinds of relationships. Defining the relationship between two use cases is the decision of the software analysts of the use case diagram. A relationship between two use cases is basically modeling the dependency between the two use cases. The reuse of an existing use case by using different types of relationships reduces the overall effort required in developing a system.
  • 18. Use case relationship Extends •Indicates that an "Invalid Password" use case may include (subject to specified in the extension) the behavior specified by base use case "Login Account". •Depict with a directed arrow having a dotted line. The tip of arrowhead points to the base use case and the child use case is connected at the base of the arrow. •The stereotype "<<extends>>" identifies as an extend relationship
  • 19. Use case relationship Include • When a use case is depicted as using the functionality of another use case, the relationship between the use cases is named as include or uses relationship. • A use case includes the functionality described in another use case as a part of its business process flow. • A uses relationship from base use case to child use case indicates that an instance of the base use case will include the behavior as specified in the child use case. • An include relationship is depicted with a directed arrow having a dotted line. The tip of arrowhead points to the child use case and the parent use case connected at the base of the arrow. • The stereotype "<<include>>" identifies the relationship as an include relationship.
  • 20. Use case relationship Generalization •A generalization relationship is a parent-child relationship between use cases. •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.
  • 21. Example of Use Case Diagram Use Case Example - Association Link • A Use Case diagram illustrates a set of use cases for a system, i.e. the actors and the relationships between the actors and use cases.
  • 22. Example of Use Case Diagram Use Case Example - Include Relationship • The include relationship adds additional functionality not specified in the base use case. The <<Include>> relationship is used to include common behavior from an included use case into a base use case in order to support the reuse of common behavior.
  • 23. Example of Use Case Diagram Use Case Example - Extend Relationship • The extend relationships are important because they show optional functionality or system behavior. • The <<extend>> relationship is used to include optional behavior from an extending use case in an extended use case. • Look at the use case diagram example. It shows an extend connector and an extension point "Search".
  • 24. Example of Use Case Diagram Use Case Example - Generalization Relationship • A generalization relationship means that a child use case inherits the behavior and meaning of the parent use case. The child may add or override the behavior of the parent. • The figure provides a use case example by showing two generalization connectors that connect between the three use cases.
  • 25. Example of Use Case Diagram – Vehicle Sales Systems As you can see even a system as big as a vehicle sales system contains not more than 10 use cases! That's the beauty of use case modeling.
  • 26. How to identify actor? Often, people find it easiest to start the requirements elicitation process by identifying the actors. The following questions can help you identify the actors of your system (Schneider and Winters - 1998): • Who uses the system? • Who installs the system? • Who starts up the system? • Who maintains the system? • Who shuts down the system? • What other systems use this system? • Who gets information from this system? • Who provides information to the system? • Does anything happen automatically at a present time?
  • 27. How to identify Use Cases? Identifying the Use Cases, and then the scenario-based elicitation process carries on by asking what externally visible, observable value that each actor desires. The following questions can be asked to identify use cases, once your actors have been identified (Schneider and Winters - 1998): • What functions will the actor want from the system? • Does the system store information? What actors will create, read, update or delete this information? • Does the system need to notify an actor about changes in the internal state? • Are there any external events the system must know about? What actor informs the system of those events?
  • 29. What is a use case scenario A use case represents the actions that are required to enable or abandon a goal. A use case has multiple “paths” that can be taken by any user at any one time. A use case scenario is a single path through the use case. A use case defines all of the paths that lead to the success of the use case.The use case also defines all the paths that lead to the abandonment of the use case without achieving its goal. Each unique combination of those paths that can be taken by an actor during a single “pass” through the use case is a use case scenario.
  • 30. When do you use each construct? • A scenario is an actual sequence of interactions (i.e., an instance) describing one specific situation; a use case is a general sequence of interactions (i.e., a class) describing all possible scenarios associated with a situation.

Editor's Notes

  • #2: 1
  • #26: As you can see even a system as big as a vehicle sales system contains not more than 10 use cases! That's the beauty of use case modeling. The use case model also shows the use of extend and include. Besides, there are associations that connect between actors and use cases.