Use Case: | |
Version: | 1.0 |
Description: | |
Scope: | |
Level: | |
Primary Actor(s): | |
Trigger: |
Assumptions:
Preconditions: | |
Success End Condition: | |
Failed End Condition: | |
Assumptions: |
Main Scenario:
Exception Scenarios:
Extensions:
Other Information:
The first thing you will want to do is make it your own by customizing the template to meet your organization. For example, I found that the version number was not valuable because we used a configuration management system to maintain the documents. Therefore, the most recent copy was at the tip of the archive -- a much simpler solution.
Next, you need to create some "Use Case Standards." In my organizations, we number the main flow steps. When an exception occurs, we put
Next time, using Activity Diagrams to Describe Use Cases
No comments:
Post a Comment