Develop an understanding with the requirements providers on the meaning of the requirements.


As the work matures and requirements are derived, all activities or disciplines will receive requirements. To avoid requirements creep, criteria are established to designate appropriate channels or official sources from which to receive requirements. Those who receive requirements conduct analyses of them with the provider to ensure that a compatible, shared understanding is reached on the meaning of requirements. The result of these analyses and dialogs is a set of approved requirements.

Example Work Products

  1. Lists of criteria for distinguishing appropriate requirements providers
  2. Criteria for evaluation and acceptance of requirements
  3. Results of analyses against criteria
  4. A set of approved requirements


1. Establish criteria for distinguishing appropriate requirements providers.

2. Establish objective criteria for the evaluation and acceptance of requirements.


SSD Addition
Refer to the Service System Development process area for more information about analyzing and validating requirements.

Lack of evaluation and acceptance criteria often results in inadequate verification, costly rework, or customer rejection.


Examples of evaluation and acceptance criteria include the following:
  • Clearly and properly stated
  • Complete
  • Consistent with one another
  • Uniquely identified
  • Consistent with service system architecture and quality attribute priorities
  • Appropriate to implement
  • Verifiable (i.e., testable)
  • Traceable
  • Achievable
  • Tied to business value
  • Identified as a priority for the customer

3. Analyze requirements to ensure that established criteria are met.

4. Reach an understanding of requirements with requirements providers so that participants can commit to them.