Task: Detail Use-Case Scenarios |
This task describes how to detail a use-case scenarios for the system.
Disciplines: Requirements
Purpose
The purpose of this task is to describe use-case scenarios in sufficient detail to validate understanding of the requirements, to ensure concurrence with stakeholder expectations, and to permit software development to begin.
Relationships
Roles | Primary Performer: Analyst | Additional Performers: Architect Developer Stakeholder Tester
Inputs | Mandatory: Use Case | Optional: None
Outputs | Glossary Storyboard Use Case Use-Case Model
Steps
Detail use cases and scenarios
Some use cases and scenarios might need to be described in more detail to validate the understanding of the requirements and to permit software development to begin. This does not imply that all use cases and scenarios will be detailed prior to commencing implementation on them. The level of detail captured will vary depending upon the needs of the project and the complexity of the use case. Capture the use case and scenarios details in the use case specification.
Update Use-Case Model
Based on your work detailing use cases and scenarios, update the Use-Case Model. Add, remove or update Actors and Use Cases as required. For more information on creating and structuring your use case model see Guideline: Use-Case Model. For assistance in assessing the quality of your use-case model see Checklist: Use-Case Model.
Detail glossary terms
Review the flow of the use case or scenario. If information is exchanged, be specific about what is passed back and forth. Collaborate with stakeholders to ensure that you define newly discovered domain terms, or ambiguous terms properly in the glossary. If your understanding of the domain has improved, refine existing glossary terms.
Use storyboards to visualize and validate the scenario (as appropriate)
Achieve concurrence
Review the detailed use case and scenarios with relevant stakeholders and the development team to ensure consistency with the agreed vision. Assess quality and identify any required changes.
Key Considerations
To avoid unnecessary rework, only those use-case scenarios that are scheduled for implementation in the near term (in the next iteration or two) must be detailed. Not all use-case scenarios require detailing.
More Information
Checklists | General Requirements Use Case
Concepts | Essential Use Cases Functional Decomposition Requirements Storyboarding Traceability Use Case Use Case Granularity
Guidelines | Detail Use Cases and Scenarios Effective Requirement Reviews Requirement Pitfalls Strategies to Avoid Functional Decomposition Writing Requirements Statements
Tool Mentors | Create a Low Fidelity Storyboard Using IBM Rational Requirements Composer Detailing Use Case Scenarios with IBM Rational Requirements Composer Managing Use Cases Using RequisitePro
This program and the accompanying materials are made available under the Eclipse Public License V1.0, which accompanies this distribution. OpenUP Copyright © Copyright IBM Corp. 1987, 2009. All Rights Reserved.