====== Constraint ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]

===== Discussion =====

A Constraint establishes a boundary within which an entity exists, operates, or participates in a system. It restricts one or more characteristics, values, relationships, configurations, behaviors, or operating conditions.

A requirement states an obligation. A Constraint restricts the acceptable ways in which an entity satisfies an obligation. A requirement may establish, apply, or govern one or more Constraints.

Constraints associated with a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] include environmental, security, deployment, communication, resource, timing, and configuration restrictions.

===== Definition =====

*condition that restricts the permitted characteristics, values, relationships, configurations, behaviors, or operating circumstances of an entity*

===== Source =====

Dido Solutions, Inc. and Jackrabbit Consulting, Inc. Project definition.

===== Note =====

A Constraint does not necessarily constitute an independent requirement. A requirement establishes an obligation when it requires a system or responsible entity to impose, enforce, validate, or comply with the Constraint.

A Constraint should identify:

  * The entity subject to the restriction
  * The restricted characteristic, value, relationship, configuration, behavior, or operating circumstance
  * The permitted boundary or condition
  * The circumstances under which the restriction applies
  * The source or authority establishing the restriction

===== Example =====

A Test Environment description specifies that every participating Node uses an approved communication protocol. The protocol restriction constitutes a Constraint. The requirement directing DIDO-TE to record and enforce the restriction establishes the corresponding obligation.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>