Differences

This shows you the differences between two versions of the page.

--- dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-003-configure-a-node:start [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:start [2026/08/20 14:55] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
+====== NOD-003 — Configure a Node ======
+[[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:start|Go to Node Requirements]]
+===== Statement =====
+The [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL configure each [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] in accordance with its [[dido:99_annexes:annex-b-terms-and-definitions:n:node_definition|Node Definition]] and applicable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]].
+===== Derived From =====
+  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-001-define-a-node:start|NOD-001 — Define a Node]]
+  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-002-provision-a-node:start|NOD-002 — Provision a Node]]
+  * [[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:n:node_configuration|Node Configuration]] establishes the [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_value|Configuration Values]], settings, [[dido:99_annexes:annex-b-terms-and-definitions:n:node_binding|Node Bindings]], [[dido:99_annexes:annex-b-terms-and-definitions:c:credential|Credentials]], [[dido:99_annexes:annex-b-terms-and-definitions:p:policy|Policies]], [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_parameter|Configuration Parameters]], and relationships required for a provisioned Node to participate in a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]].
+Controlled configuration distinguishes the [[dido:99_annexes:annex-b-terms-and-definitions:n:node_implementation|Node Implementation]] from the Node Configuration applied to a particular Node instance. This separation permits the DIDO-TE to reuse the same Node Implementation under different controlled test conditions.
+Configuration preserves the identity, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_source|Configuration Source]], Configuration Value, authority, applicability, and [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] of each material configuration item. It also distinguishes the intended Node Configuration from the configuration applied to the Node.
+An incomplete, inconsistent, unauthorized, or unrecorded Node Configuration may change Node behavior and invalidate subsequent [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]] and [[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_parameter|Configuration Parameter]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_value|Configuration Value]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_source|Configuration Source]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_binding|Node Binding]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:s:sensitive_configuration_value|Sensitive Configuration Value]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_record|Configuration Record]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]
+  * [[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]]
+===== Contents =====
+{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:03-node-requirements:nod-003-configure-a-node#1|js navbar nocookie maxjs#1 id#dido_te_nod_003_nav}}
+===== Verification =====
+Verification of NOD-003 occurs through verification of its decomposed child requirements.
+Collectively, verification confirms that:
+  * The applicable Node Configuration is selected.
+  * Required Configuration Values are determined through [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_resolution|Configuration Resolution]] using identified and authorized Configuration Sources.
+  * Configuration Values remain distinguishable from Node Implementation content and [[dido:99_annexes:annex-b-terms-and-definitions:t:test_input|Test Inputs]].
+  * The DIDO-TE assigns the resolved Node Configuration to the intended Node instance through [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_application|Configuration Application]].
+  * Required interfaces, endpoints, resources, services, and [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]] are established through Node Bindings.
+  * Sensitive Configuration Values receive protection through applicable [[dido:99_annexes:annex-b-terms-and-definitions:s:security_control|Security Controls]].
+  * The DIDO-TE records the intended, resolved, and applied Node Configurations in a Configuration Record.
+  * The DIDO-TE detects missing, invalid, incompatible, conflicting, altered, or unauthorized Configuration Values.
+  * The DIDO-TE performs [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_validation|Configuration Validation]] before using the configured Node in Test Execution.
+  * The DIDO-TE prevents an unconfigured, incorrectly configured, or unvalidated Node from participating in Test Execution.
+  * The DIDO-TE maintains Traceability among the Node Definition, Node Implementation, Node instance, Node Configuration, Test Definition, Test Environment, configuration activities, Configuration Record, validation results, and resulting Evidence.
+===== Referenced By =====
+{{backlinks>.}}
+===== Related Architecture Sections =====
+  * Add links to the architecture sections governing Node Configuration, Configuration Sources, Configuration Parameters, Node Bindings, Sensitive Configuration Values, Configuration Validation, Evidence, and Traceability.
+===== 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>dido:03-dido-te:99-annexes:annex-c-requirements:03-node-requirements:nod-003-configure-a-node:start#Statement&noheader&nofooter&noeditbtn}}
+</code>
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>