Use case specification outline
A use case specification provides textual detail for a use case. You can use this sample outline to create your own use case specification documents.
|Use case name||States the use case name. Typically, the name expresses the objective or
observable result of the use case, such as
Withdraw Cashin the case of an automatic teller 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||Nonfunctional requirements that are specific to a use case but are not specified in the text of the use case flow of events. Examples of special requirements include these factors: 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 starts.|
|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.|