ENV-003j — Validate Controlled Starting State

Go to ENV-003 — Establish Controlled Starting State

Statement

Before each Test Execution, the DIDO-TE SHALL validate the controlled starting state against the controlled descriptive information governing the applicable Test Environment.

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

Validation determines whether the established starting state corresponds to the required Baseline, Configuration, participating Nodes, Test Objects, Test Resources, Test Inputs, communication relationships, and applicable Constraints.

Validation also confirms the absence or effective isolation of residual state excluded from the required starting state.

A validated starting state provides an inspectable basis for admitting a Test Execution and interpreting its resulting Test Results.

Applies To

Verification

Verification confirms that:

The DIDO-TE validates the controlled starting state before each Test Execution.Validation uses the applicable controlled descriptive information.Validation confirms application of the required Baseline.Validation confirms application of the required Configuration values.Validation confirms the required initial state of each participating Node and Test Object.Validation confirms the availability and required state of each Test Resource and Test Input.Validation confirms establishment of each required communication relationship.Validation confirms satisfaction of each applicable Constraint.Validation confirms removal or effective isolation of prohibited residual state.Validation produces an explicit valid or invalid result.The DIDO-TE identifies each difference between the required and actual starting states.The DIDO-TE records each validation result and identified difference as Evidence.The DIDO-TE maintains Traceability among the validation result, identified differences, controlled descriptive information, Test Environment, and applicable Test Execution.An incomplete, incorrect, indeterminate, unsupported, or untraceable validation result constitutes nonconformance with this requirement.Verification includes:

Inspection of the controlled descriptive information used for validationObservation of controlled-starting-state validationInspection of Baseline and Configuration validation resultsInspection of Node, Test Object, Test Resource, and Test Input validation resultsInspection of communication-relationship and Constraint validation resultsInspection of residual-state validation resultsInspection of the explicit valid or invalid resultInspection of identified differences between the required and actual starting statesInspection of validation Evidence and Traceability recordsA negative assessment using an incomplete or incorrect starting stateConfirmation that the negative assessment produces an invalid result and identifies the applicable differences

Referenced By

Related Architecture Sections

Add links to the architecture sections governing starting-state validation, validation criteria, difference detection, Evidence, Traceability, 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-003j-validate-controlled-starting-state#Statement&noheader&nofooter&noeditbtn}}

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.