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

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-004d-transition-the-node-state [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-004d-transition-the-node-state [2026/08/17 14:20] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== NOD-004d — Transition the Node State ======
  
 +[[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 control each transition of a [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] from one lifecycle state to another.
 +
 +===== 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-c-requirements:03-functional-requirements:03-02-node-requirements:nod-004-control-the-node-lifecycle:nod-004b-start-the-node|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:nod-004c-confirm-node-readiness|NOD-004c — Confirm Node Readiness]]
 +  * [[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 =====
 +
 +A lifecycle transition moves a Node from a known source state to an intended destination state. The applicable [[dido:99_annexes:annex-b-terms-and-definitions:n:node_definition|Node Definition]] or [[dido:99_annexes:annex-b-terms-and-definitions:n:node_implementation|Node Implementation]] identifies the supported states, permitted transitions, transition preconditions, authorized procedures, and expected outcomes.
 +
 +Lifecycle transitions include activation, suspension, resumption, entry into or departure from a maintenance state, and other changes required during preparation or [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]].
 +
 +A controlled transition preserves the integrity of the [[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 Bindings]], data, resources, and interactions affected by the state change. It also coordinates the transition with dependent Nodes and [[dido:99_annexes:annex-b-terms-and-definitions:t:test_resource|Test Resources]].
 +
 +An undefined, unauthorized, incomplete, conflicting, or out-of-sequence transition may leave the Node or Test Environment in an unknown condition and may invalidate the applicable Test Execution or [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]].
 +
 +===== 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: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 the Node subject to the lifecycle transition.
 +  * The DIDO-TE identifies the actual source state and intended destination state.
 +  * The Node Definition or Node Implementation identifies the requested transition as a permitted transition.
 +  * The DIDO-TE uses an identified and authorized transition procedure.
 +  * The transition identifies its initiating authority, preconditions, parameters, dependencies, time constraints, and expected outcome.
 +  * The DIDO-TE verifies each mandatory precondition before initiating the transition.
 +  * The DIDO-TE prevents a transition from an unknown, incorrect, unauthorized, or unsuitable source state.
 +  * The DIDO-TE prevents an undefined, unauthorized, conflicting, duplicate, or out-of-sequence transition.
 +  * The DIDO-TE coordinates the transition with affected Nodes, Dependencies, Node Bindings, and Test Resources.
 +  * The DIDO-TE preserves or re-establishes the required Node Configuration and Node Bindings during the transition.
 +  * The DIDO-TE observes the Node throughout the transition.
 +  * The DIDO-TE detects an unsuccessful, incomplete, interrupted, stalled, or timed-out transition.
 +  * The DIDO-TE confirms the actual Node state after the transition.
 +  * The DIDO-TE detects a difference between the intended and actual destination states.
 +  * The DIDO-TE determines the effect of a lifecycle transition occurring during Test Execution.
 +  * The DIDO-TE identifies Test Inputs, observations, Test Results, and other Nodes affected by the transition.
 +  * An unsuccessful transition leaves the Node in a known state or identifies the resulting state and required recovery action.
 +  * The DIDO-TE prevents a Node in an invalid, unknown, unauthorized, or unsuitable resulting state from continuing to participate in Test Execution.
 +  * The DIDO-TE records the Node identity, initiating authority, transition procedure, source state, intended destination state, parameters, operations, timing, actual resulting state, findings, exceptions, and recovery actions.
 +  * Repeated authorized transitions from equivalent source states under equivalent conditions produce equivalent destination states within specified tolerances.
 +  * The DIDO-TE maintains Traceability among the Node Definition, Node Implementation, Node Configuration, Node Bindings, transition procedure, source state, transition activity, resulting state, affected Test Execution, Test Results, findings, exceptions, and resulting Evidence.
 +  * An incorrect, incomplete, unsuccessful, unauthorized, ambiguous, or untraceable lifecycle transition constitutes nonconformance with this requirement.
 +
 +Verification includes:
 +
 +  * Inspection of the Node identity and source state
 +  * Inspection of permitted lifecycle states and transitions
 +  * Inspection of the authorized transition procedure and responsible authority
 +  * Inspection of transition preconditions, parameters, Dependencies, Node Bindings, and Test Resources
 +  * Observation of an authorized lifecycle transition
 +  * Confirmation of the actual resulting Node state
 +  * A negative assessment involving an undefined transition
 +  * A negative assessment involving an unauthorized or unsuitable source state
 +  * A negative assessment involving an interrupted or timed-out transition
 +  * Confirmation that an unsuitable resulting state prevents continued participation in Test Execution
 +  * Inspection of affected Test Executions, Test Results, findings, exceptions, recovery actions, Evidence, and Traceability
 +
 +===== Referenced By =====
 +
 +{{backlinks>.}}
 +
 +===== Related Architecture Sections =====
 +
 +  * Add links to the architecture sections governing Node lifecycle states, lifecycle transitions, Node Configuration, Node Bindings, Test Environment coordination, 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:nod-004d-transition-the-node-state#Statement&noheader&nofooter&noeditbtn}}
 +</code>
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>