dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-003-establish-controlled-starting-state:env-003c-initialise-participating-nodes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-003-establish-controlled-starting-state:env-003c-initialise-participating-nodes [2026/08/18 12:34] – removed - external edit (Unknown date) 127.0.0.1dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-003-establish-controlled-starting-state:env-003c-initialise-participating-nodes [2026/08/18 12:34] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== ENV-003c — Initialise Participating Nodes ======
  
 +[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-003-establish-controlled-starting-state:start|Go to ENV-003 — Establish Controlled Starting State]]
 +
 +===== Statement =====
 +
 +Before each [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]], the [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL initialise each participating [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] to the state specified by the controlled descriptive information governing the applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]].
 +
 +===== Derived From =====
 +
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-003-establish-controlled-starting-state:start|ENV-003 — Establish Controlled Starting State]]
 +  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-005|[DTE5] DIDO-TE Requirements Register]], source requirement identifier and obligation to be assigned
 +  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-006|[DTE6] Structured Information Processing Reference Architecture (SIP-RA)]]
 +  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-007|[DTE7] Federated Data Interpretation Systems Reference Architecture (FDIS-RA)]]
 +
 +===== Rationale =====
 +
 +Initialising each participating [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] establishes its required operational state before [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|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 [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]].
 +
 +===== Applies To =====
 +
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_resource|Test Resource]]
 +
 +===== 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 [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|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 Node
 +  * Inspection of the specified initial state for each participating Node
 +  * Observation of Node initialisation
 +  * Comparison of each resulting Node state with its specified initial state
 +  * Inspection of the applied software, parameters, dependencies, interfaces, identity, communication settings, and supporting resources
 +  * Inspection for prohibited residual Node state
 +  * Inspection of Node identity, initialisation status, and resulting-state records
 +  * Inspection of Traceability records connecting each Node to its specified state, resulting state, and Test Execution
 +  * A negative assessment using an absent, uninitialised, partially initialised, incorrectly initialised, residual, or untraceable Node
 +  * Confirmation that the negative assessment produces a nonconformance result
 +
 +===== Referenced By =====
 +
 +{{backlinks>.}}
 +
 +===== 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:
 +
 +<code dokuwiki>
 +{{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}}
 +</code>
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>