Allocate contractual requirements to supplier deliverables.


Contractual requirements are allocated, as appropriate, to supplier deliverables. The requirements for each supplier deliverable are documented. In some cases, technical requirements are allocated to third-party products that are used by the supplier (e.g., COTS products).

Example Work Products

  1. Requirement allocation sheets


1. Allocate requirements to supplier deliverables.

In the case of an evolutionary acquisition lifecycle, the requirements for the initial capability can also be allocated to suppliers’ initial iterations or increments based on stakeholder priorities, technology issues, supplier capabilities, and acquirer project objectives.

2. Allocate design constraints to supplier deliverables.

3. Document relationships among allocated requirements and design constraints.

Relationships include dependencies (i.e., a change in one requirement can affect other requirements).

4. Allocate 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. Develop an approach to address requirements that by their nature are shared among multiple stakeholders (e.g., the acquirer, multiple suppliers, customers, end users).

Some requirements (in particular, for some quality attribute requirements) should be shared among multiple stakeholders and maintained through the life of the product (e.g., security requirements often cannot be allocated to a single supplier). An approach that addresses such requirements should be devised and appropriately incorporated in customer and supplier agreements.

Refer to the Solicitation and Supplier Agreement Development (SSAD) (CMMI-ACQ) process area for more information about establishing supplier agreements.