Differences
This shows you the differences between two versions of the page.
| 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:nod-008b-observe-node-state [2026/08/17 14:20] – removed - external edit (Unknown date) 127.0.0.1 | dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-008-observe-a-node:nod-008b-observe-node-state [2026/08/17 14:20] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== NOD-008b — Observe Node State ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Statement ===== | ||
| + | |||
| + | The [[dido: | ||
| + | |||
| + | ===== Derived From ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Rationale ===== | ||
| + | |||
| + | Observation of Node state establishes the actual lifecycle state, readiness, availability, | ||
| + | |||
| + | The governing Test Definition identifies the Node states and state-related conditions subject to observation. It also identifies the expected values, permitted transitions, | ||
| + | |||
| + | The DIDO-TE preserves the distinction between a commanded state, an expected state, a state reported by the Node, and an observed state. A state reported by the Node does not establish the actual state when other observations contradict that report. | ||
| + | |||
| + | State observation continues across the transitions identified by the governing Test Definition. This allows the DIDO-TE to determine whether a requested transition occurred, whether the Node reached the expected resulting state, and whether the Node maintained that state for the required period. | ||
| + | |||
| + | An unknown, stale, inconsistent, | ||
| + | |||
| + | ===== Applies To ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Verification ===== | ||
| + | |||
| + | Verification confirms that: | ||
| + | |||
| + | - The governing Test Definition identifies each Node state subject to observation. | ||
| + | - The governing Test Definition identifies the expected values, permitted transitions, | ||
| + | - The DIDO-TE observes each Node state identified by the governing Test Definition. | ||
| + | - The DIDO-TE distinguishes commanded, expected, reported, and observed Node states. | ||
| + | - The DIDO-TE identifies the source of each state observation. | ||
| + | - The DIDO-TE associates each state observation with the identity of the Node. | ||
| + | - The DIDO-TE associates each state observation with a controlled time and sequence. | ||
| + | - The DIDO-TE observes each state transition identified by the governing Test Definition. | ||
| + | - The DIDO-TE identifies the event or control action that initiates an observed state transition. | ||
| + | - The DIDO-TE verifies that a requested state transition reaches the expected resulting state. | ||
| + | - The DIDO-TE detects a transition to an unexpected or prohibited state. | ||
| + | - The DIDO-TE detects a Node that fails to leave its source state. | ||
| + | - The DIDO-TE detects a Node that fails to reach the expected resulting state within the specified time. | ||
| + | - The DIDO-TE detects an unrequested, | ||
| + | - The DIDO-TE detects a difference between the state reported by the Node and the observed state. | ||
| + | - The DIDO-TE detects a missing, unknown, stale, ambiguous, conflicting, | ||
| + | - The DIDO-TE prevents a Node with an unsuitable or unknown state from participating in an activity that requires another state. | ||
| + | - The DIDO-TE determines the effect of an unexpected or unknown Node state on affected Test Executions, Test Results, and Evidence. | ||
| + | - The DIDO-TE maintains Traceability among the Node identity, Node Definition, Node Implementation, | ||
| + | - A missing, stale, ambiguous, conflicting, | ||
| + | |||
| + | ===== Referenced By ===== | ||
| + | |||
| + | The following pages reference this requirement: | ||
| + | |||
| + | {{backlinks> | ||
| + | |||
| + | ===== Delivery Phase ===== | ||
| + | |||
| + | < | ||
| + | |||
| + | ===== Implementation Status ===== | ||
| + | |||
| + | < | ||
| + | |||
| + | ===== Requirement Status ===== | ||
| + | |||
| + | < | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ===== Issues ===== | ||
| + | |||
| + | < | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ===== Notes for Editors ===== | ||
| + | |||
| + | <code dokuwiki> | ||
| + | {{section> | ||
| + | </ | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||