Use Case Reference
1.
Guidance for Use Case Template
Document each use case using the template shown in the Appendix. This section provides a description of each
.
section in the use case template
2.
Use Case Identification
2.1.
Use Case ID
Give each use case a unique integer sequence number identifier. Alternatively, use a hierarchical form: X.Y. Related
use cases can be grouped in the hierarchy.
2.2.
Use Case Name
State a concise, results-oriented name for the use case. These reflect the tasks the user needs to be able to accomplish
using the system. Include an action verb and a noun. Some examples:
View part number information.
Manually mark hypertext source and establish link to target.
Place an order for a CD with the updated software version.
2.3.
Use Case History
2.3.1 Created By
Supply the name of the person who initially documented this use case.
2.3.2 Date Created
Enter the date on which the use case was initially documented.
2.3.3 Last Updated By
Supply the name of the person who performed the most recent update to the use case description.
2.3.4 Date Last Updated
Enter the date on which the use case was most recently updated.
3.
Use Case Definition
3.1.
Actor
An actor is a person or other entity external to the software system being specified who interacts with the system and
performs use cases to accomplish tasks. Different actors often correspond to different user classes, or roles,
identified from the customer community that will use the product. Name the actor that will be initiating this use case
and any other actors who will participate in completing the use case.
3.2.
Description
Provide a brief description of the reason for and outcome of this use case, or a high-level description of the sequence
of actions and the outcome of executing the use case.
2