Purpose:

Allocate the requirements for each product component.

Objective:

Description:

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).

Inputs:

<?>

Outputs:

<?>

Controls:

<?>

Task Instructions:

Check for Consistency with Process Design Summary

    1. Using the Project Charter, Customer Requirements Document and Product Requirements Document, [the Lead Architect] is responsible for verifying in identifying inconsistencies if any, between the Business and  Customer Requirement Documents, Project Charter and the Process Design Summary Document.
    2. Using the Baseline Process Design Summary, the Lead Architect is responsible for updating the Process Design Summary to resolve any identified inconsistencies.
    3. Using the Updated Baseline Process Design Summary, [the Lead Architect] with support from [the Project Manager] is responsible for ensuring that all the inconsistencies found and the customer and product requirements documents are resolved effectively.