ENV-003d — Initialise Test Objects

Go to ENV-003 — Establish Controlled Starting State

Statement

Before each Test Execution, the DIDO-TE SHALL initialise each applicable Test Object to the state specified by the controlled descriptive information governing the 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

Initialising each applicable Test Object establishes the required state of the object subjected to examination during a Test Execution.

Test Object initialisation applies the required software, data, state, parameters, dependencies, interfaces, identity, and supporting resources specified by the controlled descriptive information.

A known initial state prevents an uninitialised, partially initialised, incorrectly initialised, or residual Test Object state from influencing the observed behaviour or resulting Test Results.

Applies To

Verification

Verification confirms that:

The controlled descriptive information identifies each Test Object applicable to the Test Execution.The controlled descriptive information specifies the required initial state of each applicable Test Object.The DIDO-TE initialises each applicable Test Object before Test Execution.Each Test Object reaches its specified initial state.Each Test Object contains the required software, data, parameters, dependencies, interfaces, identity, and supporting resources.The initialised state excludes residual Test Object state prohibited by the controlled descriptive information.The DIDO-TE records the identity, initialisation status, and resulting state of each Test Object.The DIDO-TE maintains Traceability among each Test Object, its specified initial state, its resulting state, and the applicable Test Execution.An absent, uninitialised, partially initialised, incorrectly initialised, residual, or untraceable Test Object state constitutes nonconformance with this requirement.Verification includes:

Inspection of the controlled descriptive information identifying each applicable Test ObjectInspection of the specified initial state for each Test ObjectObservation of Test Object initialisationComparison of each resulting Test Object state with its specified initial stateInspection of the applied software, data, parameters, dependencies, interfaces, identity, and supporting resourcesInspection for prohibited residual Test Object stateInspection of Test Object identity, initialisation status, and resulting-state recordsInspection of Traceability records connecting each Test Object to its specified state, resulting state, and Test ExecutionA negative assessment using an absent, uninitialised, partially initialised, incorrectly initialised, residual, or untraceable Test ObjectConfirmation that the negative assessment produces a nonconformance result

Referenced By

Related Architecture Sections

Add links to the architecture sections governing Test Object lifecycle, Test Object initialisation, Test Object state, Configuration, residual-state control, 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-003d-initialise-test-objects#Statement&noheader&nofooter&noeditbtn}}

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