Allocate the requirements for each product component.
Refer to the Technical Solution (TS) (CMMI-DEV) process area for more information about selecting product component solutions.
The product architecture provides the basis for allocating product requirements to product components. The requirements for product components of the defined solution include allocation of product performance; design constraints; and fit, form, and function to meet requirements and facilitate production. In cases where a higher level requirement specifies a quality attribute that will be the responsibility of more than one product component, the quality attribute can sometimes be partitioned for unique allocation to each product component as a derived requirement, however, other times the shared requirement should instead be allocated directly to the architecture.
For example, allocation of shared requirements to the architecture would describe how a performance requirement (e.g., on responsiveness) is budgeted among components so as to account in an end-to-end manner for realization of the requirement. This concept of shared requirements can extend to other architecturally significant quality attributes (e.g., security, reliability).
Example Work Products
- Requirement allocation sheets
- Provisional requirement allocations
- Design constraints
- Derived requirements
- Relationships among derived requirements
1. Allocate requirements to functions.
2. Allocate requirements to product components and the architecture.
3. Allocate design constraints to product components and the architecture.
4. Allocate requirements to delivery increments.
5. Document relationships among allocated requirements.
Relationships include dependencies in which a change in one requirement may affect other requirements.