3.3 Use Case Model
TO DO: Provide a use case diagram that will encapsulate the
entire system and all actors.
3.3.1 Use Case #1 (use case name and unique identifier
- e.g. U1)
TO DO: Provide a specification for each use case diagram
Author - Identify team member who wrote this use case
Purpose - What is the basic objective of the use-case. What is
it trying to achieve?
Requirements Traceability - Identify all requirements traced
to this use case
Priority - What is the priority. Low, Medium, High.
Importance of this use case being completed and functioning
properly when system is depolyed
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
Actors - Actors (human, system, devices, etc.) that trigger the
use case to execute or provide input to the use case
Extends - If this is an extension use case, identify which use
case(s) it extends
Flow of Events
1. Basic Flow - flow of events normally executed in the
use-case
2. Alternative Flow - a secondary flow of events due to
infrequent conditions
3. Exceptions - Exceptions that may happen during the
execution of the use case
Includes (other use case IDs)
Notes/Issues - Any relevant notes or issues that need to be
resolved
