ENV-003c — Initialise Participating Nodes

Go to ENV-003 — Establish Controlled Starting State

Statement

Before each Test Execution, the DIDO-TE SHALL initialise each participating Node to the state specified by 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

Initialising each participating Node establishes its required operational state before Test Execution.

Node initialisation applies the required software, state, parameters, dependencies, interfaces, identity, communication settings, and supporting resources identified by the controlled descriptive information.

Establishing a known initial state prevents an uninitialised, partially initialised, incorrectly initialised, or residual Node state from influencing Node behaviour or the resulting Test Results.

Applies To

Verification

Verification confirms that:

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

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

Referenced By

Related Architecture Sections

Add links to the architecture sections governing Node lifecycle, Node initialisation, Node 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-003c-initialise-participating-nodes#Statement&noheader&nofooter&noeditbtn}}

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