Transform stakeholder needs, expectations, constraints, and interfaces into customer requirements.

The various inputs from the relevant stakeholders must be consolidated, missing information must be obtained, and conflicts must be resolved in documenting the recognized set of customer requirements. The customer requirements may include needs, expectations, and constraints with regard to verification and validation.

In some situations, the customer provides a set of requirements to the project, or the requirements exist as an output of a previous project's activities. In these situations, the customer requirements could conflict with the relevant stakeholders' needs, expectations, constraints, and interfaces and will need to be transformed into the recognized set of customer requirements after appropriate resolution of conflicts.

Relevant stakeholders representing all phases of the product's lifecycle should include business as well as technical functions. In this way, concepts for all product-related lifecycle processes are considered concurrently with the concepts for the products. Customer requirements result from informed decisions on the business as well as technical effects of their requirements.

Typical Work Products

1.    Customer requirements

2.    Customer constraints on the conduct of verification

3.    Customer constraints on the conduct of validation

Subpractices

1.    Translate the stakeholder needs, expectations, constraints, and interfaces into documented customer requirements.

2.    Define constraints for verification and validation.