Purpose:
Establish and maintain product and product component requirements, which are based n the customer requirements.
Objective:
Description:
The customer functional and quality attribute requirements can be expressed in the customer’s terms and can be nontechnical descriptions. The product requirements are the expression of these requirements in technical terms that can be used for design decisions. An example of this translation is found in the first House of Quality Function Deployment, which maps customer desires into technical parameters. For instance, “solid sounding door” may be mapped to size, weight, fit, dampening, and resonant frequencies.
Product and product component requirements address the satisfaction of customer, business, and project objectives and associated attributes, such as effectiveness and affordability.
Derived requirements also address the needs of other lifecycle phases (e.g., production, operations, disposal) to the extent compatible with business objectives.
RASIC:
Inputs:
- Draft Project Charter
- Draft Customer Requirements Document
Outputs:
<?>
Controls:
<?>
Task Instructions:
Derive Product Requirements
- Using the Draft Project Charter, and the Draft Customer Requirements Document, [the Business Analyst] consulting with [the Product Owner] is responsible for deriving a Draft Customer Requirements Document.
Prioritize Requirements
- Using the Draft Customer Requirements, and the Draft Product Requirements Document, [the Business Analyst] consulting with [the Product Owner] is responsible for prioritizing the Product requirements based on the prioritization of the parent Customer Requirements and its impact on cost, schedule, functionality, risk and performance.
Derive System Requirements
- Using the Draft Customer Requirements, Use Cases and the Draft Product Requirements Document, [the Business Analyst] consulting with [the Product Owner] is responsible for deriving Additional Product and/or system requirements.
Prioritize System Requirements
- Using the Draft Customer Requirements, and the Draft Product Requirements Document, [the Business Analyst] consulting with [the Product Owner] is responsible for prioritizing the System Requirements based on the prioritization of the parent Customer Requirements and its impact on cost, schedule, functionality, risk and performance.
