ENV-003h — Apply Applicable Constraints

Go to ENV-003 — Establish Controlled Starting State

Statement

Before each Test Execution, the DIDO-TE SHALL apply each applicable Constraint to the Test Environment element governed by the Constraint.

Derived From

, source requirement identifier and obligation to be assigned[DTE6] Structured Information Processing Reference Architecture (SIP-RA)[DTE7] Federated Data Interpretation Systems Reference Architecture (FDIS-RA)

Rationale

Applying each applicable Constraint establishes the conditions, limits, prohibitions, dependencies, and relationships governing the controlled starting state.

Constraints may govern participating Nodes, Test Objects, Test Resources, 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 Test Results.

Applies To

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 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 ConstraintsInspection of the Test Environment elements governed by the ConstraintsObservation of Constraint application and evaluationConfirmation that each governed Test Environment element satisfies its applicable ConstraintsTesting for missing, conflicting, unsatisfied, and prohibited conditionsInspection of Constraint identity, application-status, and evaluation recordsInspection of Traceability records connecting each Constraint to its governed element, evaluation result, and Test ExecutionA negative assessment using a missing, incorrectly applied, conflicting, unsatisfied, or untraceable ConstraintConfirmation that the negative assessment produces a nonconformance result

Referenced By

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.