dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-003-configure-a-node:nod-003c-apply-the-node-configuration

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-003-configure-a-node:nod-003c-apply-the-node-configuration [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-003-configure-a-node:nod-003c-apply-the-node-configuration [2026/08/17 14:20] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== NOD-003c — Apply the Node Configuration ======
  
 +[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-003-configure-a-node:start|Go to NOD-003 — Configure a Node]]
 +
 +===== Statement =====
 +
 +The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL apply the selected and resolved [[dido:99_annexes:annex-b-terms-and-definitions:n:node_configuration|Node Configuration]] to the intended [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] instance.
 +
 +===== Derived From =====
 +
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-003-configure-a-node:start|NOD-003 — Configure a Node]]
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-003-configure-a-node:nod-003a-select-the-node-configuration|NOD-003a — Select the Node Configuration]]
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-003-configure-a-node:nod-003b-resolve-node-configuration-values|NOD-003b — Resolve Node Configuration Values]]
 +  * [[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 =====
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_application|Configuration Application]] changes the actual Node instance so its operational settings correspond to the selected and resolved Node Configuration.
 +
 +The activity may create or modify configuration files, runtime parameters, environment settings, [[dido:99_annexes:annex-b-terms-and-definitions:c:credential|Credentials]], [[dido:99_annexes:annex-b-terms-and-definitions:p:policy|Policies]], data-store entries, service properties, or other controlled configuration mechanisms.
 +
 +Controlled Configuration Application preserves the target identity, operation sequence, actual [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_value|Configuration Values]] applied, resulting state, and any difference between the intended and actual Node Configuration.
 +
 +Configuration Application directed to the wrong Node, performed in the wrong sequence, or completed only partially may invalidate the Node and subsequent [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]].
 +
 +===== 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:c:configuration_value|Configuration Value]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_procedure|Configuration Procedure]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_application|Configuration Application]]
 +  * [[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:e:evidence|Evidence]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
 +
 +===== Verification =====
 +
 +Verification confirms that:
 +
 +  * The DIDO-TE identifies the intended Node instance before applying the Node Configuration.
 +  * The DIDO-TE identifies the selected Node Configuration and its resolved Configuration Values.
 +  * The DIDO-TE verifies that each mandatory Configuration Value has been resolved before Configuration Application.
 +  * The DIDO-TE verifies that the selected Node Configuration applies to the intended Node Definition, Node Implementation, and Node instance.
 +  * The DIDO-TE uses an identified and authorized Configuration Procedure.
 +  * The DIDO-TE performs configuration operations in the required sequence.
 +  * The DIDO-TE applies each Configuration Value through its specified configuration mechanism.
 +  * The DIDO-TE verifies the completion and outcome of each material configuration operation.
 +  * The DIDO-TE preserves Configuration Values designated for retention.
 +  * The DIDO-TE prevents unintended Configuration Values from a previous Node Configuration from remaining active.
 +  * The DIDO-TE detects Configuration Application to the wrong Node or configuration location.
 +  * The DIDO-TE detects an unsuccessful, incomplete, interrupted, duplicate, or out-of-sequence Configuration Application.
 +  * The DIDO-TE detects a difference between the intended and actual Node Configuration.
 +  * The DIDO-TE prevents an incompletely or incorrectly configured Node from proceeding to Test Execution.
 +  * The DIDO-TE records the target Node, applied Node Configuration, actual Configuration Values, Configuration Procedure, responsible authority, timing, operations, findings, exceptions, and resulting status.
 +  * A failed Configuration Application leaves the Node in a known state or identifies the resulting state and required recovery action.
 +  * Repeated application of the same controlled Node Configuration produces an equivalent Node Configuration within specified tolerances.
 +  * A material change to the applied Node Configuration produces a distinguishable configuration revision.
 +  * The DIDO-TE maintains Traceability among the selected Node Configuration, resolved Configuration Values, Configuration Procedure, Node instance, applied Node Configuration, findings, exceptions, and resulting Evidence.
 +  * An incorrect, incomplete, unsuccessful, unauthorized,