dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-004-control-the-node-lifecycle:nod-004b-start-the-node

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-02-node-requirements:nod-004-control-the-node-lifecycle:nod-004b-start-the-node [2026/08/17 14:20] – removed - external edit (Unknown date) 127.0.0.1dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-004-control-the-node-lifecycle:nod-004b-start-the-node [2026/08/17 14:20] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== NOD-004b — Start the Node ======
  
 +[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-004-control-the-node-lifecycle:start|Go to NOD-004 — Control the Node Lifecycle]]
 +
 +===== Statement =====
 +
 +The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL start each [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] through an identified and authorized lifecycle procedure.
 +
 +===== Derived From =====
 +
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-004-control-the-node-lifecycle:start|NOD-004 — Control the Node Lifecycle]]
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-004-control-the-node-lifecycle:nod-004a-establish-the-initial-node-state|NOD-004a — Establish the Initial Node 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 =====
 +
 +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 [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]].
 +
 +A controlled start operation applies the sequence, parameters, dependencies, authorities, time constraints, and environmental conditions specified by the [[dido:99_annexes:annex-b-terms-and-definitions:n:node_definition|Node Definition]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node_implementation|Node Implementation]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node_configuration|Node Configuration]], and applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|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 [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|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 =====
 +
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_definition|Node Definition]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_implementation|Node Implementation]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_configuration|Node Configuration]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_binding|Node Binding]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependency]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_resource|Test Resource]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
 +
 +===== 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 state
 +  * Inspection of the authorized start procedure and responsible authority
 +  * Inspection of start preconditions, parameters, Dependencies, Node Bindings, services, and Test Resources
 +  * Observation of the start sequence
 +  * Observation of the Node during startup
 +  * Confirmation of the actual resulting Node state
 +  * A negative assessment involving an unauthorized start
 +  * A negative assessment involving an unavailable mandatory Dependency
 +  * A negative assessment involving an interrupted or timed-out start
 +  * Confirmation that an unsuccessful start prevents Test Execution
 +  * Confirmation that startup completion does not automatically establish Node readiness
 +  * Inspection of start records, findings, exceptions, recovery actions, Evidence, and Traceability
 +
 +===== Referenced By =====
 +
 +{{backlinks>.}}
 +
 +===== 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 =====
 +
 +<todo>Assign the applicable delivery phase.</todo>
 +
 +===== 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:03-node-requirements:nod-004-control-the-node-lifecycle:nod-004b-start-the-node#Statement&noheader&nofooter&noeditbtn}}
 +</code>
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>