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-004-control-the-node-lifecycle:nod-004a-establish-the-initial-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-004-control-the-node-lifecycle:nod-004a-establish-the-initial-node-state [2026/08/17 14:20] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== NOD-004a — Establish the Initial Node State ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Statement ===== | ||
| + | |||
| + | The [[dido: | ||
| + | |||
| + | ===== Derived From ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Rationale ===== | ||
| + | |||
| + | The initial Node state provides the controlled starting point for subsequent lifecycle operations. It identifies the actual condition of the Node before the DIDO-TE starts, activates, suspends, resumes, stops, restarts, recovers, or terminates it. | ||
| + | |||
| + | The applicable [[dido: | ||
| + | |||
| + | An unknown, ambiguous, unauthorized, | ||
| + | |||
| + | Establishing and recording the initial state supports lifecycle control, reproducibility, | ||
| + | |||
| + | ===== Applies To ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Verification ===== | ||
| + | |||
| + | Verification confirms that: | ||
| + | |||
| + | * The DIDO-TE uniquely identifies the Node before establishing its initial state. | ||
| + | * The Node Definition or Node Implementation identifies the permitted initial states. | ||
| + | * The DIDO-TE uses identified and authorized criteria and procedures to determine the initial Node state. | ||
| + | * The DIDO-TE observes the actual Node state rather than relying solely on an intended or previously recorded state. | ||
| + | * The DIDO-TE identifies active processes, services, connections, | ||
| + | * The DIDO-TE identifies residual Node activity or state from an earlier operation. | ||
| + | * The DIDO-TE confirms that the initial Node state satisfies the applicable Node Definition, Node Implementation, | ||
| + | * The DIDO-TE detects an unknown, ambiguous, conflicting, | ||
| + | * The DIDO-TE prevents a lifecycle transition when the initial Node state does not satisfy the transition preconditions. | ||
| + | * The DIDO-TE identifies the corrective or recovery action required when the initial Node state is unsuitable. | ||
| + | * The DIDO-TE records the Node identity, observed state, applicable criteria, procedure, authority, time, findings, exceptions, and resulting status. | ||
| + | * Repeated determination of an unchanged initial Node state under equivalent conditions produces an equivalent result. | ||
| + | * The DIDO-TE maintains Traceability among the Node Definition, Node Implementation, | ||
| + | * An unknown, ambiguous, unauthorized, | ||
| + | |||
| + | Verification includes: | ||
| + | |||
| + | * Inspection of the Node identity | ||
| + | * Inspection of permitted initial states and transition preconditions | ||
| + | * Inspection of the authorized state-determination criteria and procedure | ||
| + | * Observation of the actual Node state | ||
| + | * Inspection of active processes, services, connections, | ||
| + | * A negative assessment involving an unknown initial state | ||
| + | * A negative assessment involving residual activity from an earlier operation | ||
| + | * Confirmation that an unsuitable initial state prevents a lifecycle transition | ||
| + | * Inspection of 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, | ||
| + | |||
| + | ===== Delivery Phase ===== | ||
| + | |||
| + | < | ||
| + | |||
| + | ===== Requirement Status ===== | ||
| + | |||
| + | Draft | ||
| + | |||
| + | ===== Statement Reference ===== | ||
| + | |||
| + | Use the following syntax to reference this requirement’s Statement section from another DokuWiki page: | ||
| + | |||
| + | <code dokuwiki> | ||
| + | {{section> | ||
| + | </ | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||