Purpose:

Customer requirements are refined and elaborated into contractual requirements.

Objective:

Defining contractual requirements that are based on customer requirements and are included in the solicitation package and supplier agreement.

Description:

Customer requirements are analyzed in conjunction with the development of the operational concept to derive more detailed and precise sets of requirements, called contractual requirements, to be included in the solicitation package for potential suppliers and eventually in the supplier agreement. The level of detail of contractual requirements is based on the acquisition strategy and project characteristics.

Contractual requirements arise from constraints, consideration of issues implied but not explicitly stated in the customer requirements baseline, and factors introduced by design constraints and supplier capabilities.
Contractual requirements include both requirements documented in contracts between an acquirer and supplier and requirements addressed through formal agreements between the acquirer and other organizations (e.g., partners, subcontractors, government agencies, internal organizational units). Requirements are reexamined throughout the project lifecycle.

The requirements are allocated to supplier deliverables. The traceability across levels of requirements and supplier deliverables (and planned supplier delivery increments) is documented.

Inputs:

• Customer Requirements

Outputs:

<?>

Controls:

<?>

Task Instructions:

Establish Contractual Requirements

1. 1. Using the <?>, [the ?] with support from <?> is responsible for developing functional and quality attribute requirements necessary for the determination of alternative solutions and the development of the product by the supplier.
   2. Using the <?>, [the ?] with support from <?> is responsible for developing requirements for the interfaces between the acquired product and other products in the intended environment.
   3. Using the <?>, [the ?] with support from <?> is developing  design considerations and constraints necessary for supplier activities that include: determination of alternative solutions, development and evaluation of architectures, and the development of the product.
   4. Using the <?>, [the ?] with support from <?> is responsible for developing requirements for verification and validation of the product to
      be developed by the supplier.
   5. Using the <?>, [the ?] with support from <?> is establishing and maintain relationships among the requirements under
      consideration during change management and requirements allocation.
   6. Using the <?>, [the ?] with support from <?> is identifying nontechnical requirements.
   7. Using the <?>, [the ?] with support from <?> is establishing  and maintain a prioritization of contractual requirements.

Allocate Contractual Requirements 

1. 1. Using the <?>, [the ?] with support from <?> is responsible for allocating  requirements to supplier deliverables.
   2. Using the <?>, [the ?] with support from <?> is allocating design constraints to supplier deliverables.
   3. Using the <?>, [the ?] with support from <?> is documenting relationships among allocated requirements and design constraints. Relationships include dependencies (i.e., a change in one requirement can affect other
      requirements).
   4. Using the <?>, [the ?] with support from <?> is allocating requirements to suppliers. In situations where multiple suppliers are involved in developing the technical solution, different products or product components may be allocated to different suppliers.
   5. Using the <?>, [the ?] with support from <?> is developing  an approach to address requirements that by their nature are shared among multiple stakeholders (e.g., the acquirer, multiple suppliers, customers, end users).