Purpose:

Customer requirements are refined and elaborated to develop product and product component requirements.

Objective:

<?>

Description:

Customer requirements are analyzed in conjunction with the development of the operational concept to derive more detailed and precise sets of requirements called “product and product component requirements.” Product and product component requirements address the needs associated with each product lifecycle phase. Derived requirements arise from constraints; consideration of issues implied but not explicitly stated in the customer requirements baseline; factors introduced by the selected architecture, product lifecycle, and design; and the developer’s unique business considerations.

The requirements are reexamined with each successive, lower-level set of requirements and architecture, and the preferred product concept is refined. The requirements are allocated to product functions and product components, including objects, people, and processes. In the case of iterative or incremental development, the requirements are also allocated to iterations or increments based on customer priorities, technology issues, and project objectives. The traceability of requirements to functions, objects, tests, issues, or other entities is documented. The allocated requirements and functions (or other logical entities) are the basis for synthesizing the technical solution; however, as the architecture is defined or emerges, it serves as the ultimate basis for directing the allocation of requirements to the solution. As internal components are developed, additional interfaces are defined, and interface requirements are established.

Inputs:

<?>

Outputs:

<?>

Controls:

<?>

Task Instructions:

Establish Product and Product Component Requirements

    1. Using the <?>, [the ?] with support from <?> is responsible for developing requirements in technical terms necessary for the product and product component design.
    2. Using the <?>, [the ?] with support from <?> is responsible for deriving requirements that result from design decisions.
    3. Using the <?>, [the ?] with support from <?> is responsible for developing architectural requirements capturing critical quality attributes and quality attribute measures necessary for establishing the product architecture and design.
    4. Using the <?>, [the ?] with support from <?> is responsible for establishing and maintaining relationships between requirements for consideration during change management and requirements allocation.

Allocate Product Component Requirements

    1. Using the <?>, [the ?] with support from <?> is responsible for allocating requirements to functions.
    2. Using the <?>, [the ?] with support from <?> is responsible for allocating requirements to product components and the architecture.
    3. Using the <?>, [the ?] with support from <?> is responsible for allocating design constraints to product components and the architecture.
    4. Using the <?>, [the ?] with support from <?> is responsible for allocating requirements to delivery increments.
    5. Using the <?>, [the ?] with support from <?> is responsible for documenting relationships among allocated requirements.

Identify Interface Requirements

    1. Using the <?>, [the ?] with support from <?> is responsible for identifying interfaces both external to the product and internal to the product (e.g., between functional partitions or objects). 
    2. Using the <?>, [the ?] with support from <?> is responsible for developing the requirements for the identified interfaces