ENV-003 — Establish Controlled Starting State

Go to C.2 Test Environment Requirements

Statement

Before each Test Execution, the DIDO-TE SHALL establish a controlled starting state for the applicable Test Environment.

The controlled starting state SHALL:

Apply the required BaselineApply the required Configuration valuesInitialise each participating NodeInitialise each Test ObjectProvision each required Test ResourceLoad each required Test InputEstablish each required communication relationshipApply each applicable ConstraintRemove or isolate residual state from prior Test ExecutionsValidate the resulting starting state against the controlled descriptive information governing the Test EnvironmentRecord the validated starting state as EvidenceThe DIDO-TE SHALL NOT begin the Test Execution when the starting state fails validation.

Derived Requirements

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

A controlled starting state establishes the conditions under which a Test Execution begins.

Applying the required Baseline, Configuration values, Test Inputs, Test Resources, and Constraints limits differences among repeated Test Executions to the variables governed by the applicable Test Definition.

Removing or isolating residual state prevents a prior Test Execution from influencing a later Test Result.

Validating and recording the controlled starting state supports Reproducibility, Comparability, and Traceability.

Applies To

Verification

Verification confirms that:

The DIDO-TE establishes a controlled starting state before each Test Execution.The starting state contains the required Baseline and Configuration values.The starting state contains the required Nodes, Test Objects, Test Resources, and Test Inputs.The starting state contains the required communication relationships.The starting state satisfies each applicable Constraint.The DIDO-TE removes or isolates residual state from prior Test Executions.The DIDO-TE validates the resulting starting state against the controlled descriptive information governing the Test Environment.The DIDO-TE records the validated starting state as Evidence.The DIDO-TE maintains Traceability among the starting-state Evidence, applicable Baseline, Configuration, Test Definition, Test Environment, and Test Execution.The DIDO-TE prevents Test Execution when the starting state fails validation.The DIDO-TE records each starting-state validation failure as Evidence.A missing, incomplete, invalid, residual, or untraceable starting state constitutes nonconformance with this requirement.Verification includes:

Inspection of the controlled descriptive information governing the Test EnvironmentInspection of the applicable Baseline and Configuration recordsInspection of Node and Test Object initialisation recordsInspection of Test Resource provisioning recordsInspection of Test Input loading recordsInspection of the established communication relationshipsInspection of applicable Constraint enforcement recordsInspection of starting-state validation EvidenceInspection of Traceability recordsRepetition of a Test Execution from the same controlled starting stateA negative assessment using a starting state that differs from the required stateA residual-state assessment following a prior Test ExecutionConfirmation that the DIDO-TE prevents Test Execution when starting-state validation failsInspection of Evidence recording the validation failure

Referenced By

Related Architecture Sections

Add links to the architecture sections governing Test Environment initialisation, state control, residual-state isolation, validation, Evidence, 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:start#Statement&noheader&nofooter&noeditbtn}}

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