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

Differences

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

Link to this comparison view

Both sides previous 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:start [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:start [2026/08/17 14:20] (current) – ↷ Page moved from dido:03-dido-te:99-annexes:annex-c-requirements:03-node-requirements:nod-004-control-the-node-lifecycle:start to dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-004-control-the-node- nick_dido
Line 1: Line 1:
 +====== NOD-004 — Control the Node Lifecycle ======
  
 +[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:start|Go to Node Requirements]]
 +
 +===== Statement =====
 +
 +The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL control the lifecycle of each [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] participating in a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]].
 +
 +===== Derived From =====
 +
 +  * [[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 =====
 +
 +Node lifecycle control governs the states through which a Node passes and the operations that move the Node between those states.
 +
 +A Node may require initialization, startup, readiness confirmation, activation, suspension, resumption, shutdown, restart, recovery, or termination during the preparation and operation of a Test Environment. The applicable lifecycle states and permitted transitions depend on the Node Definition, Node Implementation, Node Configuration, Test Definition, and Test Environment.
 +
 +Each lifecycle operation identifies the target Node, current state, requested state, applicable preconditions, authorized procedure, responsible authority, operation time, resulting state, findings, exceptions, and required recovery action.
 +
 +Controlled lifecycle transitions prevent a Node from participating in Test Execution while it occupies an unknown, invalid, unauthorized, failed, or otherwise unsuitable state.
 +
 +Lifecycle records support synchronization among Nodes, diagnosis of failures, reconstruction of Test Execution, evaluation of Test Results, and production of Evidence.
 +
 +===== 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: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_execution|Test Execution]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Result]]
 +  * [[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 each Node subject to lifecycle control.
 +  * The applicable Node Definition or Node Implementation identifies the lifecycle states and transitions supported by the Node.
 +  * The DIDO-TE identifies the current lifecycle state of each Node.
 +  * The DIDO-TE identifies the lifecycle state required for each Node before the Node participates in Test Execution.
 +  * The DIDO-TE uses identified and authorized lifecycle procedures.
 +  * Each lifecycle operation identifies its initiating authority and target Node.
 +  * Each lifecycle operation identifies its source state, requested transition, and intended resulting state.
 +  * Each lifecycle operation verifies its applicable preconditions before initiating the transition.
 +  * The DIDO-TE permits only defined and authorized lifecycle transitions.
 +  * The DIDO-TE performs lifecycle operations in the required sequence.
 +  * The DIDO-TE coordinates dependent lifecycle operations among applicable Nodes and Test Resources.
 +  * The DIDO-TE verifies the completion and outcome of each material lifecycle operation.
 +  * The DIDO-TE confirms the actual Node state after each lifecycle transition.
 +  * The DIDO-TE detects an unsuccessful, incomplete, interrupted, duplicate, conflicting, unauthorized, or out-of-sequence lifecycle operation.
 +  * The DIDO-TE detects a difference between the requested and actual Node state.
 +  * The DIDO-TE prevents a Node in an unknown, invalid, unauthorized, failed, or otherwise unsuitable state from participating in Test Execution.
 +  * The DIDO-TE detects an unexpected Node state change during Test Execution.
 +  * The DIDO-TE identifies the effect of an unexpected Node state change on the applicable Test Execution and Test Results.
 +  * A failed lifecycle operation leaves the Node in a known state or identifies the resulting state and required recovery action.
 +  * A Node restart or recovery operation preserves or re-establishes the required Node Configuration and Node Bindings.
 +  * A material change to the Node Definition, Node Implementation, Node Configuration, lifecycle procedure, or Test Environment triggers applicable revalidation.
 +  * The DIDO-TE records the target Node, initiating authority, lifecycle procedure, source state, requested state, operations, timing, actual resulting state, findings, exceptions, and recovery actions.
 +  * The DIDO-TE maintains Traceability among the Node Definition, Node Implementation, Node Configuration, lifecycle procedure, lifecycle operations, Node states, Test Environment, Test Execution, Test Results, findings, exceptions, and resulting Evidence.
 +  * An incorrect, incomplete, unsuccessful, unauthorized, ambiguous, or untraceable lifecycle operation constitutes nonconformance with this requirement.
 +
 +Verification includes:
 +
 +  * Inspection of the lifecycle states and transitions defined for each applicable Node
 +  * Inspection of authorized lifecycle procedures and responsible authorities
 +  * Observation of Node initialization and startup
 +  * Observation of Node readiness determination
 +  * Observation of an authorized transition between supported Node states
 +  * Observation of Node shutdown
 +  * Observation of Node restart or recovery
 +  * Confirmation that a Node in an unsuitable state cannot participate in Test Execution
 +  * A negative assessment involving an undefined or unauthorized lifecycle transition
 +  * A negative assessment involving an interrupted lifecycle operation
 +  * A negative assessment involving a difference between the requested and actual Node state
 +  * Confirmation that an unexpected state change during Test Execution produces a detectable condition
 +  * Confirmation that a failed transition leaves the Node in a known state or produces a recovery action
 +  * Inspection of lifecycle records, findings, exceptions, Evidence, and Traceability
 +
 +===== Contents =====
 +
 +{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:03-node-requirements:nod-004-control-the-node-lifecycle#1|js navbar nocookie maxjs#1 id#dido_te_nod_004_requirements_nav}}
 +
 +===== Referenced By =====
 +
 +{{backlinks>.}}
 +
 +===== Related Architecture Sections =====
 +
 +  * Add links to the architecture sections governing Node lifecycle states, lifecycle transitions, Node Configuration, Node Bindings, Test Environment control, Test Execution, 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:start#Statement&noheader&nofooter&noeditbtn}}
 +</code>
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>