NOD-008 — Observe a Node

Go to Node Requirements

The DIDO-TE SHALL observe each Node throughout its participation in a Test Environment.

• [DTE5] DIDO-TE Requirements Register, 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)

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 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 Node Bindings, and produces activity consistent with its Node Definition and 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 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.

• DIDO-TE
• Node
• Node Definition
• Node Implementation
• Node Configuration
• Node Binding
• Test Definition
• Test Environment
• Test Execution
• Test Resource
• Test Result
• Evidence
• Traceability

NOD-008 is decomposed into the following leaf requirements:

Verification confirms that the child requirements collectively:

1. Establish the scope and controls governing Node observation.
2. Observe the lifecycle state, readiness, availability, health, configuration, and operating condition of the Node.
3. Observe the activities, interactions, inputs, outputs, Node Bindings, and control actions associated with the Node.
4. Observe the resources used by the Node.
5. Detect differences between expected and observed Node state, activity, behavior, timing, interactions, or resource use.
6. Record each material Node observation with its source, time, sequence, context, and applicable Node identity.
7. Continue the required observation before, during, between, and after Test Executions while the Node participates in the Test Environment.
8. Associate each observation with the applicable Node Definition, Node Implementation, Node Configuration, Test Environment, and Test Execution.
9. Preserve the observations required to support Test Results, Evidence, and Traceability.
10. Prevent a material Node condition or deviation from remaining undetected because observation was missing, interrupted, incorrectly scoped, or associated with the wrong Node.
11. Identify nonconformance with an applicable child requirement as nonconformance with NOD-008.

The following pages reference this requirement:

Assign the applicable delivery phase.

Implementation status derives from the implementation status of the child requirements.

The proposed derived requirement and its decomposition require review and acceptance.

Assign the source requirement identifier and obligation from the DIDO-TE Requirements Register.

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.