Diseño

Use Cases
for
<Project>
Version 1.0 approved
Prepared by <author>
<organization>
<date created>
Revision History

Name | Date | Reason For Changes | Version |
| | | |
| | | |

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.Use Case Identification
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.
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. Someexamples:
0 View part number information.
1 Manually mark hypertext source and establish link to target.
2 Place an order for a CD with the updated software version.
Use Case History
Created By
Supply the name of the person who initially documented this use case.
Date Created
Enter the date on which the use case was initially documented.
Last Updated By
Supply the name of the personwho performed the most recent update to the use case description.
Date Last Updated
Enter the date on which the use case was most recently updated.
Use Case Definition
Actors
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.
Trigger
Identify the event that initiates the use case. This could be an external business event or system event that causes the use case to begin, or it could be the first step in the normal flow.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.
Preconditions
List any activities that must take place, or any conditions that must be true, before the use case can be started. Number each precondition. Examples:
1. User’s identity has been authenticated.2. User’s computer has sufficient free memory available to launch task.
Postconditions
Describe the state of the system at the conclusion of the use case execution. Number each postcondition. Examples:
1. Document contains only valid SGML tags.
2. Price of item in database has been updated with new value.
Normal Flow
Provide a detailed description of the user actions and systemresponses that will take place during execution of the use case under normal, expected conditions. This dialog sequence will ultimately lead to accomplishing the goal stated in the use case name and description. This description may be written as an answer to the hypothetical question, “How do I <accomplish the task stated in the use case name>?” This is best done as a numbered list of actionsperformed by the actor, alternating with responses provided by the system. The normal flow is numbered “X.0”, where “X” is the Use Case ID.
Alternative Flows
Document other, legitimate usage scenarios that can take place within this use case separately in this section. State the alternative flow, and describe any differences in the sequence of steps that take place. Number each alternative flowin the form “X.Y”, where “X” is the Use Case ID and Y is a sequence number for the alternative flow. For example, “5.3” would indicate the third alternative flow for use case number 5.
Exceptions
Describe any anticipated error conditions that could occur during execution of the use case, and define how the system is to respond to those conditions. Also, describe how the system is to respond if...