dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-008-observe-a-node:start

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-008-observe-a-node: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-008-observe-a-node:start [2026/08/22 14:21] (current) – ↷ Links adapted because of a move operation 216.73.217.111
Line 1: Line 1:
 +====== NOD-008 — Observe a Node ======
  
 +[[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 observe each [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] throughout its participation 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 observation provides information about the state, activity, interactions, resource use, and operating condition of a Node throughout its participation in a Test Environment.
 +
 +Observation begins when the DIDO-TE admits the Node into the Test Environment and continues through applicable configuration, validation, readiness, execution, isolation, recovery, stopping, and removal activities. Observation therefore extends beyond the boundaries of an individual [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]].
 +
 +Lifecycle observation supports determination of whether the Node remains in an expected state, operates within applicable constraints, uses authorized resources, participates through valid [[dido:99_annexes:annex-b-terms-and-definitions:n:node_binding|Node Bindings]], and produces activity consistent with its [[dido:99_annexes:annex-b-terms-and-definitions:n:node_definition|Node Definition]] and [[dido:99_annexes:annex-b-terms-and-definitions:n:node_configuration|Node Configuration]].
 +
 +Lifecycle observation also supports detection of changes or deviations that occur before, between, or after Test Executions. Such conditions may affect Node readiness, the validity of a subsequent Test Execution, the interpretation of Test Results, or the disposition of the Node.
 +
 +NOD-008 differs from [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-005-execute-a-node:nod-005d-observe-node-execution|NOD-005d — Observe Node Execution]]. NOD-005d governs observation of Node activity within a particular Test Execution. NOD-008 governs observation across the broader period during which the Node participates in the Test Environment.
 +
 +The child requirements decompose lifecycle observation into establishment of observation controls, observation of Node state, activity and resource use, detection of deviations, and recording of observations.
 +
 +===== 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: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_resource|Test Resource]]
 +  * [[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]]
 +
 +===== Derived Requirements =====
 +
 +NOD-008 is decomposed into the following leaf requirements:
 +
 +{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:03-node-requirements:nod-008-observe-a-node#1|js navbar nocookie maxjs#1 id#dido_te_nod_008_requirements_nav}}
 +
 +===== Verification =====
 +
 +Verification confirms that the child requirements collectively:
 +
 +  - Establish the scope and controls governing Node observation.
 +  - Observe the lifecycle state, readiness, availability, health, configuration, and operating condition of the Node.
 +  - Observe the activities, interactions, inputs, outputs, Node Bindings, and control actions associated with the Node.
 +  - Observe the resources used by the Node.
 +  - Detect differences between expected and observed Node state, activity, behavior, timing, interactions, or resource use.
 +  - Record each material Node observation with its source, time, sequence, context, and applicable Node identity.
 +  - Continue the required observation before, during, between, and after Test Executions while the Node participates in the Test Environment.
 +  - Associate each observation with the applicable Node Definition, Node Implementation, Node Configuration, Test Environment, and Test Execution.
 +  - Preserve the observations required to support Test Results, Evidence, and Traceability.
 +  - Prevent a material Node condition or deviation from remaining undetected because observation was missing, interrupted, incorrectly scoped, or associated with the wrong Node.
 +  - Identify nonconformance with an applicable child requirement as nonconformance with NOD-008.
 +
 +===== Referenced By =====
 +
 +The following pages reference this requirement:
 +
 +{{backlinks>.#dido:03-dido-te}}
 +
 +===== Delivery Phase =====
 +
 +<todo>Assign the applicable delivery phase.</todo>
 +
 +===== Implementation Status =====
 +
 +<todo>Implementation status derives from the implementation status of the child requirements.</todo>
 +
 +===== Requirement Status =====
 +
 +<todo>The proposed derived requirement and its decomposition require review and acceptance.</todo>
 +
 +----
 +
 +===== Issues =====
 +
 +<todo>Assign the source requirement identifier and obligation from the DIDO-TE Requirements Register.</todo>
 +
 +----
 +
 +===== Notes for Editors =====
 +
 +The explicit child-requirement links remain on this page until all child pages have been created and finalized. The indexmenu then provides the maintained list of child pages.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>