NOD-004b — Start the Node

Go to NOD-004 — Control the Node Lifecycle

Statement

The DIDO-TE SHALL start each Node through an identified and authorized lifecycle procedure.

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

Starting a Node moves it from an established initial state into an operating state from which the DIDO-TE determines readiness for participation in a Test Environment.

A controlled start operation applies the sequence, parameters, dependencies, authorities, time constraints, and environmental conditions specified by the Node Definition, Node Implementation, Node Configuration, and applicable Test Definition.

Starting a Node does not by itself establish Node readiness. The start operation establishes the operating condition that NOD-004c evaluates before the Node participates in Test Execution.

An uncontrolled, incomplete, unauthorized, duplicate, or out-of-sequence start may produce an unknown Node state, activate unintended services or connections, disrupt dependent Nodes, or compromise Test Environment isolation.

Applies To

Verification

Verification confirms that:

The DIDO-TE uniquely identifies the Node before starting it.The DIDO-TE confirms that the Node occupies a permitted initial state.The DIDO-TE uses an identified and authorized start procedure.The start operation identifies the initiating authority, target Node, start parameters, applicable preconditions, and intended resulting state.The DIDO-TE verifies each mandatory start precondition before initiating the start operation.The DIDO-TE verifies the availability of each Dependency, Node Binding, service, and Test Resource required during startup.The DIDO-TE starts dependent Nodes and services in the required sequence.The DIDO-TE applies the Node Configuration and startup parameters associated with the authorized start operation.The DIDO-TE prevents duplicate, conflicting, unauthorized, or out-of-sequence start operations.The DIDO-TE observes the Node during the start operation.The DIDO-TE detects an unsuccessful, incomplete, interrupted, stalled, or timed-out start operation.The DIDO-TE detects an unexpected process, service, connection, Node Binding, error, or state transition during startup.The DIDO-TE confirms the actual Node state after the start operation.The DIDO-TE distinguishes completion of the start operation from confirmation of Node readiness.An unsuccessful start leaves the Node in a known state or identifies the resulting state and required recovery action.The DIDO-TE prevents a Node with an unsuccessful, incomplete, unauthorized, or ambiguous start result from participating in Test Execution.The DIDO-TE records the Node identity, initiating authority, start procedure, parameters, source state, operations, timing, actual resulting state, findings, exceptions, and recovery actions.Repeated authorized starts from equivalent initial conditions produce equivalent resulting states within specified tolerances.The DIDO-TE maintains Traceability among the Node Definition, Node Implementation, Node Configuration, Node Bindings, Dependencies, start procedure, start activity, resulting state, findings, exceptions, and resulting Evidence.An incorrect, incomplete, unsuccessful, unauthorized, ambiguous, or untraceable start operation constitutes nonconformance with this requirement.Verification includes:

Inspection of the Node identity and initial stateInspection of the authorized start procedure and responsible authorityInspection of start preconditions, parameters, Dependencies, Node Bindings, services, and Test ResourcesObservation of the start sequenceObservation of the Node during startupConfirmation of the actual resulting Node stateA negative assessment involving an unauthorized startA negative assessment involving an unavailable mandatory DependencyA negative assessment involving an interrupted or timed-out startConfirmation that an unsuccessful start prevents Test ExecutionConfirmation that startup completion does not automatically establish Node readinessInspection of start records, findings, exceptions, recovery actions, Evidence, and Traceability

Referenced By

Related Architecture Sections

Add links to the architecture sections governing Node startup, Node lifecycle states, Node Configuration, Node Bindings, Dependencies, readiness, recovery, Evidence, and Traceability.

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-004-control-the-node-lifecycle:nod-004b-start-the-node#Statement&noheader&nofooter&noeditbtn}}

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