This
is a sample Use-Case template. The UML specification does not include a
specific template, thus there is not "one" common template. As with all
things UML, you should modify this template to best fit your specific
needs.
Template
Use case name and identifier (unique identifier and short name of the use-case)
Objective
- What is the ultimate objective of the use-case. What is it trying to
achieve? What was the source of the use-case requirement?
Actors - Who is involved in the use-case? Which actors/stakeholders?
Flow of Events
Basic Flow - flow of events normally executed in the use-case
Alternative Flow - a secondary flow of events due to infrequent conditions
Exceptions - Exceptions that may happen during the execution of the use case
Includes (other use case IDs)
Special Requirements
- non-functional requirements (performance requirements, security
requirements, real-time requirements, data definitions, etc...).
Preconditions - Any condition that must be satisfied before the use case begins
Post conditions - The conditions that will be satisfied after the use case successfully completes
Notes/Issues - Any relevant notes or issues that need to be resolved
Sample Use Case Description (adapted from "UML2 Toolkit")
Use case name and identifier: U1 - Make Resevation
Objective: A library borrower can reserve an item that is currently checked out but has no pending reservations.
Actors: borrower
Flow of Events
Basic Flow
Initiated when a borrower chooses to make a reservation for an item
The system demarks the item as reserved and associates the borrower with the reservation
Alternative Flow - None
Exceptions - None
Includes (other use case IDs): None
Special Requirements
Performance: The transaction must return to the user within 5 seconds
Preconditions: The borrower is viewing a particular title that is currently available
Post conditions: The selected item is marked such that another borrower cannot reserve it or check it out
Notes/Issues: So far there is no nice way to figure out what a borrower has reserved