Use case name |
States the use case name. Typically, the name
expresses the objective or observable result of the use case, such
as "Withdraw Cash" in the case of an ATM machine. |
Brief description |
Describes the role and purpose of the use case. |
Flow of events |
Presents the basic flow and alternative flows.
The flow of events describes the behavior of the system; it does not
describe how the system works, the details of the presentation, or
the details of the user interface. If information is exchanged, the
use case must be specific about what is passed back and forth. For
example, instead of describing an action as "the actor enters customer
information," indicate that "the actor enters the customer name and
address." |
Basic flow |
Describes the ideal, primary behavior of the
system. |
Alternative flows |
Describes exceptions or deviations from the
basic flow, such as how the system behaves when the actor enters an
incorrect user ID and the user authentication fails. |
Special requirements |
A nonfunctional requirement that is specific
to a use case but is not specified in the text of the use case flow
of events. Examples of special requirements include: legal and regulatory
requirements; application standards; quality attributes of the system,
including usability, reliability, performance, and supportability;
operating systems and environments; compatibility requirements; and
design constraints. |
Preconditions |
A state of the system that must be present before
a use case is performed. |
Post conditions |
A list of possible states for the system immediately
after a use case is finished. |
Extension points |
A point in the use-case flow of events at which
another use case is referenced. |