Casos De Uso

NOTE: This template is shareware downloaded from www.processimpact.com. All shareware payments are donated to the Norm Kerth Benefit Fund to help a consultant who is disabled with a brain injury. Please visit http://www.processimpact.com/norm_kerth.html to make a shareware payment ($10 suggested). Thank you!

Use Cases
for

Version 1.0 approved

Prepared by

eLearning versions ofseveral popular Process Impact training seminars are available at www.processimpact.com/elearning.shtml, including “In Search of Excellent Requirements,” “Exploring User Requirements with Use Cases,” and “Writing High-Quality Requirements.”

Copyright © 2004 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.

Use Cases for

Page 1

1. Guidance for Use CaseTemplate
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 aconcise, 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 theperson 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. Actors
An actor is aperson 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 usecase.

Use Cases for

Page 2

3.2. 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.

3.3. 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 theoutcome of executing the use case.

3.4. 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.

3.5. Postconditions
Describe the state of the system at the conclusion ofthe 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.

3.6. Normal Flow
Provide a detailed description of the user actions and system responses that will take place during execution of the use case under normal, expected conditions. This dialog sequence will ultimately lead toaccomplishing 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 ?” This is best done as a numbered list of actions performed by the actor, alternating with responses provided by the system. The normal flow is numbered “X.0”, where “X” is the Use Case ID.

3.7. Alternative Flows
Document other, legitimate usage...