NOD-002f — Establish the Node Initial State

Go to NOD-002 — Provision a Node

Statement

The DIDO-TE SHALL establish each provisioned Node in the initial state specified by its Node Definition.

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 successfully instantiated Node does not necessarily occupy the controlled lifecycle state required before configuration, validation, or Test Execution.

Establishing the initial state applies the prescribed startup conditions, resets transient effects, confirms required preconditions, and places the Node at a defined lifecycle boundary. The initial state provides a reproducible point from which subsequent activities proceed.

An undefined, residual, ambiguous, or incorrectly established state permits prior activity, stale data, incomplete startup, or environmental effects to influence Test Execution and Test Results.

Establishing the initial state does not constitute complete Node configuration, validation, or the beginning of Test Execution.

Applies To

Node DefinitionNode LifecycleNode StateProvisioningTest EnvironmentTest DefinitionEvidence

Verification

Verification confirms that:

The Node Definition identifies the required initial state.The initial state has a unique name or identifier.The initial state belongs to the defined Node lifecycle.The Node Definition identifies the preconditions for entering the initial state.The Node Definition identifies the operations required to establish the initial state.The Node Definition identifies the expected conditions, values, resources, interfaces, and observations associated with the initial state.The Node Definition identifies the completion criteria for establishing the initial state.The DIDO-TE verifies that the Node instance satisfies each applicable initial-state precondition.The DIDO-TE performs the required initialisation, reset, restoration, startup, or preparation operations.The DIDO-TE applies the operations in the required sequence.The DIDO-TE places each interface in its specified initial condition.The DIDO-TE places each applicable Dependency and Test Resource relationship in its specified initial condition.The DIDO-TE establishes the specified initial values for state variables, data stores, queues, caches, clocks, counters, credentials, and control information.The DIDO-TE removes or identifies residual data, state, processes, connections, messages, and effects from previous activities.The DIDO-TE distinguishes retained state required by the Node Definition from unintended residual state.The DIDO-TE confirms the Node’s actual state using the observations defined for the Node.The DIDO-TE confirms that each mandatory initial-state criterion is satisfied.The DIDO-TE detects an undefined, incomplete, inconsistent, unreachable, or incorrectly established initial state.The DIDO-TE detects a failed, interrupted, or out-of-sequence initialisation operation.The DIDO-TE detects unintended residual state material to subsequent Node behaviour.The DIDO-TE prevents configuration or Test Execution from proceeding when the Node has not reached its required initial state.Establishing the initial state does not begin Test Execution or produce a successful Test Outcome.The DIDO-TE records the required initial state, actual initial state, operations performed, observations collected, completion determination, findings, and exceptions.The DIDO-TE maintains Traceability among the Node Definition, Node instance, lifecycle definition, initial-state criteria, initialisation operations, observations, Test Definition, provisioning activity, and resulting Evidence.An undefined, incomplete, inconsistent, incorrectly established, or untraceable mandatory initial state constitutes nonconformance with this requirement.Verification includes:

Inspection of the Node lifecycle and initial-state definitionInspection of initial-state preconditions, operations, expected conditions, and completion criteriaExecution of the required initialisation procedureObservation of the Node before, during, and after initialisationComparison of the actual state with the defined initial-state criteriaInspection of interface, Dependency, resource, data, process, connection, and control statesConfirmation that unintended residual state has been removed or identifiedA negative assessment involving a failed or interrupted initialisation operationA negative assessment involving an unsatisfied preconditionA negative assessment involving unintended residual stateConfirmation that Test Execution cannot begin before the Node reaches its required initial stateRepeated establishment of the initial state to assess reproducibilityInspection of initial-state records, observations, findings, exceptions, Evidence, and Traceability

Referenced By

Related Architecture Sections

Add links to the architecture sections governing Node lifecycle, Node state, initialisation, reset, restoration, Test Execution preconditions, observation, Evidence, and Traceability.

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:03-node-requirements:nod-002-provision-a-node:nod-002f-establish-the-node-initial-state#Statement&noheader&nofooter&noeditbtn}}

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