Professional Documents
Culture Documents
05-Use-Cases
We Will Cover
What is a use-case
Use-Case diagrams
High-level use-case
Extended use-case
Difference between use case and scenario
05-Use-Cases
What is a Use-Case
Format a document
Request an elevator
05-Use-Cases
versus
Format a document
Ensure consistent formatting of two documents
Define a style
Change a style
Copy a style from one document to the next
05-Use-Cases
Thus, start with the user goals and then refine the user
goals into several (many) user interactions
05-Use-Cases
POST
Buy Item
Log In
Cashier
Customer
Refund a Purchased Item
05-Use-Cases
Another Example
Set Limits
Update Accounts
Trading Manager
Accounting System
Analyze Risk
includes
Valuation
includes
Price Deal
Trader
Capture Deal
extends
Salesperson
05-Use-Cases
Limit Exceeded
Includes
Valuation
Validate user interaction
Sanity check on sensor inputs
Check for proper authorization
05-Use-Cases
Extends
B u y Ite m
L o g In
C a s h ie r
C u s to m e r
R e fu n d a P u rc h a s e d Ite m
05-Use-Cases
11
M H
A Different Boundary
Buy Item
05-Use-Cases
12
Embedded System
Onion Skin
*
Perception/Action
Sensors/Actuators
Interfaces
System
05-Use-Cases
13
Partial POST
PO ST
B u y Ite m
L o g In
C a s h ie r
C u s to m e r
R e fu n d a P u rc h a s e d Ite m
S ta rt U p
M anager
M a n a g e U s e rs
S y s t e m A d m in is t r a t o r
Adapted from Larman Applying UML and Patterns
05-Use-Cases
A n d a L o t M o re
M H
14
POST Use-Case
Use case:
Actors:
Type:
Description:
Buy Item
Customer (initiator), Cashier
Primary
The Customer arrives at the
checkout with items to purchase.
The Cashier records the purchase
items and collects a payment.
On completion the Customer
leaves with the items
05-Use-Cases
15
Cross Ref.:
Use-Cases:
Buy Item
Customer (initiator), Cashier
Primary and essential
The Customer arrives at the checkout with items
to purchase. The Cashier records the purchase
items and collects a payment. On completion the
Customer leaves with the items.
Requirements XX, YY, and ZZ
Cashier must have completed the Log In use-case
05-Use-Cases
16
*
Temp Sensor
Water Pump
Hot Water
Water Valve
Home
Controller
Burner
Fuel Valve
90
80
70
Fuel
Off
On
60
50
Control Panel
Temp Sensor
05-Use-Cases
18
Power Down
Hom e O wner
C hange Tem p.
M H
05-Use-Cases
19
Cross Ref.:
Use-Cases:
05-Use-Cases
20
Power Up
includes
includes
Power Down
Adjust Temp
includes
Home Owner
includes
Change Temp.
Temp. Low
MH
05-Use-Cases
21
Modified:
Home Heating Use-Cases
*
Use case:
Power Up
Actors:
Home Owner (initiator)
Type:
Primary and essential
Description: The Home Owner turns the power on.
Cross Ref.:
Use-Cases:
05-Use-Cases
22
Modified:
Home Heating Use-Cases
*
Use case:
Actors:
Type:
Description:
Cross Ref.:
Use-Cases:
05-Use-Cases
Adjust Temp
System (initiator)
Secondary and essential
Check the temperature in each room. For each room:
Below target: Perform Temp Low
Above target: Perform Temp High
Requirements XX, YY, and ZZ
Temp Low, Temp High
23
Modified:
Home Heating Use-Cases
*
Use case:
Actors:
Type:
Description:
Cross Ref.:
Use-Cases:
05-Use-Cases
Temp Low
System (initiator)
Secondary and essential
Open room valve, start pump if not started.
If water temp falls below threshold,
open fuel value and ignite burner.
Requirements XX, YY, and ZZ
None
24
Power-up
Ignite burner
05-Use-Cases
All temps OK
Open valves
Start pump
25
Open valves
Ignite burner
Start pump
Burner fails
05-Use-Cases
Stop pump
Notify error
26
HACS
05-Use-Cases
27
D is tr ib u te A s ig n m e n ts
R e m in d S tu d e n t
G e t A s s ig n m e n t
S y s te m A d m in
P o s t S o lu tio n s
S u b m it A s s ig n m e n t
S tu d e n t
D is tr ib u t e G r a d e
G e t S o lu tio n
In s tru c to r
G e t G ra d e
05-Use-Cases
28
M H
HACS Use-Cases
Use case:
Actors:
Type:
Description:
Distribute Assignments
Instructor (initiator)
Primary and essential
The Instructor completes an assignment and submits
it to the system. The instructor will also submit the
due date and the class the assignment is assigned for.
Cross Ref.:
Use-Cases:
05-Use-Cases
29
Alternate HACS
HACS
C o n f ig u r e H A C S
D is t r ib u t e A s ig n m e n t s
S y s t e m A d m in
P o s t S o lu tio n s
D is t r ib u t e G r a d e
S tu d e n t
In s tru c to r
R e m in d S tu d e n t
S u b m it A s s ig n m e n t
05-Use-Cases
30
M H
05-Use-Cases
31
In short, always!!!
Requirements is the toughest part of software development
05-Use-Cases
32
Prototypes
Requirements Specification
Use-Cases
a. All High Level
b. Some Expanded
Use-Case Diagram
Budget,
Schedule
05-Use-Cases