Scribd
Upload
62 views10 pages

UML Diagrams: Use Case Diagram

The document discusses UML use case diagrams. It explains that use case diagrams are used during requirements elicitation to represent external system behavior through actors and use cases. Actors represent user roles, while use cases describe system functionality. Relationships like <<includes>> and <<extends>> define how use cases relate to each other. An example use case diagram for purchasing a train ticket is provided to illustrate these concepts.

Uploaded by

Mohsin Chaudhary
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
62 views10 pages

UML Diagrams: Use Case Diagram

The document discusses UML use case diagrams. It explains that use case diagrams are used during requirements elicitation to represent external system behavior through actors and use cases. Actors represent user roles, while use cases describe system functionality. Relationships like <<includes>> and <<extends>> define how use cases relate to each other. An example use case diagram for purchasing a train ticket is provided to illustrate these concepts.

Uploaded by

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

UML Diagrams

Use Case Diagram


2 UML Core Conventions

 Rectangles are classes or instances


 Ovals are functions or use cases
 Instances are denoted with an underlined names
 myWatch:SimpleWatch
 Joe:Firefighter
 Types are denoted with non underlined names
 SimpleWatch
 Firefighter
 Diagrams are graphs
 Nodes are entities
 Arcs are relationships between entities

Use Case Diagrams March 2019


3 Use Case Diagrams

 Used during requirements elicitation


to represent external behavior
 Actors represent roles, that is, a type
of user of the system
 Use cases represent a sequence of
interaction for a type of functionality
 The use case model is the set of all use
cases.
 It is a complete description of the
functionality of the system and its
environment

Use Case Diagrams March 2019


4 Actors

 An actor models an external entity which


communicates with the system:
 User
 External system
 Physical environment
 An actor has a unique name and an optional
description.
 Examples:
 Passenger: A person in the train
 GPS satellite: Provides the system with GPS
coordinates

Use Case Diagrams March 2019


5 Use Case

 A use case represents a class of functionality provided by


the system as an event flow.
 A use case consists of:
 Unique name
 Participating actors
 Entry conditions
 Flow of events
 Exit conditions
 Special requirements

Use Case Diagrams March 2019


6 Use Case Diagram: Example
 Name: Purchase ticket
 Participating actor: Passenger
 Entry condition:
 Passenger standing in front of ticket distributor.
 Passenger has sufficient money to purchase ticket.
 Exit condition: Passenger has ticket. Anything missing?
 Event flow:
 Passenger selects the number of zones to be traveled.
 Distributor displays the amount due.
 Passenger inserts money, of at least the amount due.
 Distributor returns change.
 Distributor issues ticket. Exceptional cases!
Use Case Diagrams March 2019
7 The <<extends>> Relationship

 <<extends>> relationships represent


exceptional or seldom invoked cases.
 The exceptional event flows are factored
out of the main event flow for clarity.
 Use cases representing exceptional flows
can extend more than one use case.
 The direction of a <<extends>>
relationship is to the extended use case

Use Case Diagrams March 2019


8 The <<includes>> Relationship

 <<includes>> relationship
represents behavior that is factored
out of the use case.
 <<includes>> behavior is factored
out for reuse, not because it is an
exception.
 The direction of a <<includes>>
relationship is to the using use
case (unlike <<extends>>
relationships).

Use Case Diagrams March 2019


9

Use Case Diagrams March 2019


10 Use Case Diagrams: Summary

 Use case diagrams represent external behavior


 Use case diagrams are useful as an index into the use cases
 Use case descriptions provide meat of model, not the use case
diagrams.
 All use cases need to be described for the model to be useful.

Use Case Diagrams March 2019

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy