Task: Detail System-Wide Requirements |  |
This task details one or more requirement that does not apply to a specific use case.
Disciplines: Requirements
Purpose
The purpose of this task is to describe one or more system-wide requirements 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: System-WideRequirements | Optional: Use Case
Outputs | Glossary System-WideRequirements
Steps
Detail system-wide requirements
Some system-wide requirements may need to be clarified or described in more detail. New requirements may be discovered while the use cases and scenarios are detailed, and new requirements may have been submitted as change requests. Collaborate with stakeholders to capture, refine and validate those requirements that will have an impact on near term, planned work or are deemed architecturally significant.
Detail glossary terms
Review the system-wide requirements and 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 system-wide requirements 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 requirements that are scheduled for implementation in the near term (in the next iteration or two) should be detailed.
More Information
Guidelines | Developing System-Wide Requirements Specification Effective Requirement Reviews
This program and the accompanying materials are made available under the Eclipse Public License V1.0, which accompanies this distribution. OpenUP Copyright