====== ENV-003h — Apply Applicable Constraints ======
[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-003-establish-controlled-starting-state:start|Go to ENV-003 — Establish Controlled Starting State]]
===== Statement =====
Before each [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]], the [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL apply each applicable [[dido:99_annexes:annex-b-terms-and-definitions:c:constraint|Constraint]] to the [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] element governed by the Constraint.
===== Derived From =====
* [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-003-establish-controlled-starting-state:start|ENV-003 — Establish Controlled Starting State]]
* [[dido:03-dido-te:99-annexes:annex-b-references:dte-005|[DTE5] DIDO-TE Requirements Register]], source requirement identifier and obligation to be assigned
* [[dido:03-dido-te:99-annexes:annex-b-references:dte-006|[DTE6] Structured Information Processing Reference Architecture (SIP-RA)]]
* [[dido:03-dido-te:99-annexes:annex-b-references:dte-007|[DTE7] Federated Data Interpretation Systems Reference Architecture (FDIS-RA)]]
===== Rationale =====
Applying each applicable [[dido:99_annexes:annex-b-terms-and-definitions:c:constraint|Constraint]] establishes the conditions, limits, prohibitions, dependencies, and relationships governing the controlled starting state.
Constraints may govern participating [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], [[dido:99_annexes:annex-b-terms-and-definitions:t:test_object|Test Objects]], [[dido:99_annexes:annex-b-terms-and-definitions:t:test_resource|Test Resources]], [[dido:99_annexes:annex-b-terms-and-definitions:t:test_input|Test Inputs]], communication relationships, security controls, resource limits, timing, location, or other Test Environment characteristics.
Applying Constraints before Test Execution prevents a starting state that violates its governing conditions from producing invalid, misleading, or incomparable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]].
===== Applies To =====
* [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]
* [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]
* [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]
* [[dido:99_annexes:annex-b-terms-and-definitions:c:constraint|Constraint]]
* [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]]
* [[dido:99_annexes:annex-b-terms-and-definitions:t:test_object|Test Object]]
* [[dido:99_annexes:annex-b-terms-and-definitions:t:test_resource|Test Resource]]
* [[dido:99_annexes:annex-b-terms-and-definitions:t:test_input|Test Input]]
* [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]]
* [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
===== Verification =====
Verification confirms that:
* The controlled descriptive information identifies each Constraint applicable to the Test Environment.
* The controlled descriptive information identifies the Test Environment element governed by each Constraint.
* The DIDO-TE applies each applicable Constraint before Test Execution.
* Each governed Test Environment element satisfies its applicable Constraints.
* The DIDO-TE detects missing, conflicting, unsatisfied, and prohibited conditions.
* The DIDO-TE records the identity, application status, and evaluation result of each applicable Constraint.
* The DIDO-TE maintains [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among each Constraint, its governed Test Environment element, its evaluation result, and the applicable Test Execution.
* A missing, incorrectly applied, conflicting, unsatisfied, or untraceable Constraint constitutes nonconformance with this requirement.
Verification includes:
* Inspection of the controlled descriptive information identifying the applicable Constraints
* Inspection of the Test Environment elements governed by the Constraints
* Observation of Constraint application and evaluation
* Confirmation that each governed Test Environment element satisfies its applicable Constraints
* Testing for missing, conflicting, unsatisfied, and prohibited conditions
* Inspection of Constraint identity, application-status, and evaluation records
* Inspection of Traceability records connecting each Constraint to its governed element, evaluation result, and Test Execution
* A negative assessment using a missing, incorrectly applied, conflicting, unsatisfied, or untraceable Constraint
* Confirmation that the negative assessment produces a nonconformance result
===== Referenced By =====
{{backlinks>.}}
===== Related Architecture Sections =====
* Add links to the architecture sections governing Constraint specification, Constraint application, Constraint evaluation, Test Environment validation, and Test Execution admission.
===== Delivery Phase =====
Assign the applicable delivery phase.
===== Requirement Status =====
Draft
===== Statement Reference =====
Use the following syntax to reference this requirement’s Statement section from another DokuWiki page:
{{section>dido:03-dido-te:99-annexes:annex-c-requirements:02-test-environment-requirements:env-003-establish-controlled-starting-state:env-003h-apply-applicable-constraints#Statement&noheader&nofooter&noeditbtn}}
----
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.