Beruflich Dokumente
Kultur Dokumente
05-Use-Cases 1
We Will Cover
What is a use-case
Use-case versus user interaction
Use-Case diagrams
The constructs in the use-case diagrams
Capturing the use-case
High-level use-case
Extended use-case
Difference between use case and scenario
05-Use-Cases 2
What is a Use-Case
05-Use-Cases 3
User Goals versus User
Interactions
Consider the following when formatting a document
Define a style
Change a style
Copy a style from one document to the next
versus
Format a document
Ensure consistent formatting of two documents
The latter is a user goal
Something the user wants to achieve
The former are user interactions
Things the user does to the system to achieve the goal
05-Use-Cases 4
Goals and Interactions
05-Use-Cases 5
Use-Case Diagrams (POST)
Buy Item
Log In
Cashier Customer
Refund a Purchased Item
05-Use-Cases 6
Another Example
Set Limits
Trading Manager
Analyze Risk
includes
Valuation
includes
Price Deal
Trader
Capture Deal
Salesperson
extends
Adapted from Fowler UML Distilled
Includes Extends
You have a piece of behavior A use-case is similar to another
that is similar across many use one but does a little bit more
cases Put the normal behavior in one
Break this out as a separate use-case and the exceptional
use-case and let the other behavior somewhere else
ones include it Capture the normal behavior
Examples include Try to figure out what can go
wrong in each step
Valuation
Capture the exceptional cases in
Validate user interaction separate use-cases
Sanity check on sensor inputs
Makes it a lot easier to
Check for proper authorization
understand
05-Use-Cases 8
Setting the System Boundary
Buy Item
Log In
Cashier Customer
Refund a Purchased Item
Buy Item
05-Use-Cases 12
Embedded System
Onion Skin
*
Perception/Action
Sensors/Actuators
Interfaces
System
05-Use-Cases 13
Partial POST
POST
Buy Item
Log In
Cashier Customer
Refund a Purchased Item
Start Up
Manager
Manage Users
System Administrator
Adapted from Larman Applying UML and Patterns And a Lot More
MH
05-Use-Cases 14
POST Use-Case
05-Use-Cases 15
POST Expanded Use-Case
05-Use-Cases 16
The Home Heating System
*
Temp Sensor
Water Pump Water Valve
80 Off
70
On
Fuel 60
50
Control Panel
Temp Sensor
05-Use-Cases 18
Home Heating Use-Case Diagram
Home Heating
Power Up
Power Down
Home Owner
Change Temp.
MH
05-Use-Cases 19
Home Heating Use-Cases
Home Heating
MH
05-Use-Cases 21
Modified:
Home Heating Use-Cases
*
05-Use-Cases 22
Modified:
Home Heating Use-Cases
*
05-Use-Cases 23
Modified:
Home Heating Use-Cases
*
05-Use-Cases 24
Scenarios -- One Use Case
05-Use-Cases 25
Scenarios -- One Use Case
05-Use-Cases 26
HACS
05-Use-Cases 27
HACS Use-Case Diagram
HACS
Student
Distribute Grade
Get Solution
Instructor
Get Grade
MH
05-Use-Cases 28
HACS Use-Cases
05-Use-Cases 29
Alternate HACS
HACS
Configure HACS
Distribute Asignments
System Admin
Post Solutions
Distribute Grade
Student
Instructor
Remind Student
Submit Assignment
05-Use-Cases 30
MH
Alternate HACS Use-Cases
05-Use-Cases 31
When to use Use-Cases
In short, always!!!
Requirements is the toughest part of software development
Use-Cases is a powerful tool to understand
Who your users are (including interacting systems)
What functions the system shall provide
How these functions work at a high level
05-Use-Cases 32
How it Fits Together
Use-Case Diagram
Budget,
Schedule Draft Conceptual Model