Task: Describe the Business |
Detail a use-case scenario for a business.
Disciplines: Business Modeling
Purpose
To describe use cases in sufficient detail to validate the understanding of the business To ensure concurrence with stakeholder's expectations To support automation (system development)
Relationships
Roles | Primary Performer: Business Analyst | Additional Performers: Stakeholder
Inputs | Mandatory: Business Use Case Business Vision | Optional: None
Outputs | Business Use Case
Main Description
Portions of this task are from the Eclipse Process Framework 1.5, made available under the Eclipse Public License V1.0. See the Tool Mentor: Detailing Use Case Scenarios with IBM Rational Requirements Composer to understand how to use Requirements Composer to detail business use-case scenarios. See the Tool Mentor: Identify and Outline Business Requirements using IBM Rational Requirements Composer to understand how to use Requirements Composer to describe general business requirements.
Steps
Detail use cases and scenarios
Some business use cases and scenarios might need to be described in more detail to validate the understanding of the business and to support business refactoring or system development. 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. See Guideline: Detail Use Cases and Scenarios.
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.
Achieve concurrence
Review the detailed use cases and scenarios with relevant stakeholders to ensure consistency with the agreed vision. Assess quality and identify any required changes. See Guideline: Effective Requirement Reviews.
Key Considerations
Only detail the use-case scenarios that are scheduled for system development or business refactoring in the near term (in the next iteration or two). This helps avoid unnecessary rework. Not all use-case scenarios require detailing. Focus on those that are unclear, critical, high risk, or are required to fully communicate the scenario to the skill level of the consumer of the use case.
More Information
Concepts | Business Use Case
Guidelines | Effective Requirement Reviews
Tool Mentors | Detailing Use Case Scenarios with IBM Rational Requirements Composer Identify and Outline Business Requirements using IBM Rational Requirements Composer
© Copyright IBM Corp. 1987, 2009. All Rights Reserved.