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-003-configure-a-node:nod-003g-validate-the-configured-node [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-003-configure-a-node:nod-003g-validate-the-configured-node [2026/08/17 14:20] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== NOD-003g — Validate the Configured Node ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Statement ===== | ||
| + | |||
| + | The [[dido: | ||
| + | |||
| + | ===== Derived From ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Rationale ===== | ||
| + | |||
| + | Validation determines whether the configured Node corresponds to its [[dido: | ||
| + | |||
| + | Validation examines the actual Node state after Configuration Application. It confirms required Configuration Values, Node Bindings, interfaces, Dependencies, | ||
| + | |||
| + | Successful Configuration Application does not by itself demonstrate that the configured Node satisfies its applicable requirements. A configuration operation may complete while leaving an incorrect value, missing binding, unavailable Dependency, unintended residual setting, or incompatible runtime state. | ||
| + | |||
| + | Validation before Test Execution prevents an invalid Node from affecting Test Inputs, Test Results, other Nodes, Test Resources, or the integrity and isolation of the Test Environment. | ||
| + | |||
| + | A material change to the Node Configuration, | ||
| + | |||
| + | ===== Applies To ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Verification ===== | ||
| + | |||
| + | Verification confirms that: | ||
| + | |||
| + | * The DIDO-TE identifies the configured Node before validation. | ||
| + | * The DIDO-TE identifies the Node Definition, Node Implementation, | ||
| + | * The DIDO-TE uses identified and authorized validation criteria and procedures. | ||
| + | * The validation criteria identify the required Node state, Configuration Values, Node Bindings, interfaces, Dependencies, | ||
| + | * The DIDO-TE validates the actual Node Configuration rather than only the selected or intended Node Configuration. | ||
| + | * The DIDO-TE confirms that each mandatory Configuration Value is present, resolved, correctly applied, and within its applicable constraints. | ||
| + | * The DIDO-TE confirms that each mandatory Node Binding is correctly established and available. | ||
| + | * The DIDO-TE confirms that required interfaces, Endpoints, services, Dependencies, | ||
| + | * The DIDO-TE confirms that unintended Configuration Values, Node Bindings, services, resources, credentials, | ||
| + | * The DIDO-TE confirms that the configured Node satisfies applicable security, access-control, | ||
| + | * The DIDO-TE confirms that the Node occupies a known and permitted lifecycle state. | ||
| + | * The DIDO-TE confirms that the Node Configuration record corresponds to the actual configured Node. | ||
| + | * The DIDO-TE records each validation criterion, procedure, observation, | ||
| + | * The DIDO-TE assigns a distinguishable validation result to the configured Node. | ||
| + | * The DIDO-TE prevents a Node with an unsuccessful, | ||
| + | * An approved exception identifies its authority, rationale, scope, duration, expected effect, and conditions for continued operation. | ||
| + | * A material change to the Node Definition, Node Implementation, | ||
| + | * Repeated validation of an unchanged configured Node under equivalent conditions produces an equivalent result within specified tolerances. | ||
| + | * The DIDO-TE maintains Traceability among the validation criteria, validation procedure, Node Definition, Node Implementation, | ||
| + | * An invalid, incompletely validated, unsuccessfully validated, unauthorized, | ||
| + | |||
| + | Verification includes: | ||
| + | |||
| + | * Inspection of the configured Node identity and actual state | ||
| + | * Inspection of the applicable Node Definition, Node Implementation, | ||
| + | * Inspection of the authorized validation criteria and procedure | ||
| + | * Comparison of the intended Node Configuration with the actual Node Configuration | ||
| + | * Confirmation of required Configuration Values and Node Bindings | ||
| + | * Confirmation of required interfaces, Endpoints, services, Dependencies, | ||
| + | * Confirmation of applicable security, access-control, | ||
| + | * A negative assessment involving an incorrect Configuration Value | ||
| + | * A negative assessment involving a missing or incompatible Node Binding | ||
| + | * A negative assessment involving an unintended residual setting or service | ||
| + | * Confirmation that an unsuccessfully validated Node cannot participate in Test Execution | ||
| + | * Confirmation that a material change invalidates the applicable validation result and triggers revalidation | ||
| + | * Repeated validation of an unchanged configured Node under equivalent conditions | ||
| + | * Inspection of validation results, findings, exceptions, Evidence, and Traceability | ||
| + | |||
| + | ===== Referenced By ===== | ||
| + | |||
| + | {{backlinks> | ||
| + | |||
| + | ===== Related Architecture Sections ===== | ||
| + | |||
| + | * Add links to the architecture sections governing Node Configuration, | ||
| + | |||
| + | ===== Delivery Phase ===== | ||
| + | |||
| + | Assign the applicable 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> | ||