Outcomes
As a result of the successful implementation of this process:
-
Stakeholder agreement on high-level requirements is achieved before the solution is designed, developed, and
deployed
-
Detailed requirements are evolved iteratively with solution design, development, and testing
-
Trade-offs between requirements and solution are managed to maximize stakeholder value
-
An accurate understanding of solution requirements exists, enhancing the probability that the correct solution will
be created
-
Customer, stakeholder, and user requirements are clearly defined and documented
-
Traceability is maintained between requirements and solution specifications derived from them
-
Rework due to incorrect or misunderstood requirements is minimized
Scope
This process focuses on translating or elaborating agreed customer (business) requirements and IT stakeholder-generated
requirements or constraints into solution-specific terms, within the context of a defined solution project or program.
It includes establishing operational requirements engineering approaches.
Examples often cited include IEEE 830 Recommended practice for software requirements specifications, IEEE Software
Engineering Body of Knowledge, CMMI and the ITIL® V-model (ITIL Service Transition).3
Includes
-
Business context modeling
-
Collecting, understanding, validating, formalizing and documenting solution requirements
-
Clarifying, analyzing, and refining the requirements from the Stakeholder Requirements Management process
-
Ongoing management of requirements for this solution
-
The complete Solution Requirements taxonomy, including:
-
Functional requirements
-
Non-functional requirements, under headings such as Service Management and Compliance
-
Deployment requirements (packaging, education, and training)
-
Usability requirements
-
Change cases and scalability requirements
-
Testing requirements
-
Stakeholder acceptance criteria
-
Solution life cycle requirements, including solution shutdown and retirement
-
Risk and feasibility analysis of requirements
-
Requirements baseline generation and traceability audits
-
Service management considerations
-
Business modeling discipline and requirements management discipline
Excludes
-
Translation from requirements to design specification (Solution Analysis and Design)
-
The life cycle management of customer wants and needs through agreed, prioritized business requirements
(Stakeholder Requirements Management)
-
Configuration Management
1IBM® Rational Unified Process
2IBM Rational Unified Process
3See ITIL Service Design, p167
|
