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-003b-resolve-node-configuration-values [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-003b-resolve-node-configuration-values [2026/08/17 14:20] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== NOD-003b — Resolve Node Configuration Values ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Statement ===== | ||
| + | |||
| + | The [[dido: | ||
| + | |||
| + | ===== Derived From ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Rationale ===== | ||
| + | |||
| + | A selected Node Configuration may contain literal Configuration Values, references, defaults, expressions, | ||
| + | |||
| + | [[dido: | ||
| + | |||
| + | Unresolved, ambiguous, incorrectly converted, conflicting, | ||
| + | |||
| + | Configuration Values remain distinct from [[dido: | ||
| + | |||
| + | ===== Applies To ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Verification ===== | ||
| + | |||
| + | Verification confirms that: | ||
| + | |||
| + | * Each required Configuration Parameter has a unique identity. | ||
| + | * Each Configuration Parameter identifies its permitted Configuration Source, data type, format, units, constraints, | ||
| + | * Each resolved Configuration Value identifies its Configuration Source and applicable authority. | ||
| + | * Configuration Resolution follows the defined precedence among explicit values, inherited values, referenced values, and defaults. | ||
| + | * Each reference resolves to an identified and accessible Configuration Source. | ||
| + | * Each substitution or transformation preserves the required type, format, units, and meaning. | ||
| + | * The DIDO-TE distinguishes resolved Configuration Values from unresolved expressions, | ||
| + | * The DIDO-TE distinguishes Configuration Values from Test Inputs. | ||
| + | * The DIDO-TE detects a missing, malformed, out-of-range, | ||
| + | * The DIDO-TE detects an unresolved reference, variable, expression, or substitution. | ||
| + | * The DIDO-TE prevents [[dido: | ||
| + | * The DIDO-TE records each resolved Configuration Value or a protected reference to it when the Configuration Value constitutes a [[dido: | ||
| + | * The DIDO-TE records each Configuration Source, default, substitution, | ||
| + | * The DIDO-TE maintains Traceability among each Configuration Parameter, Configuration Source, unresolved representation, | ||
| + | * A missing, invalid, unresolved, unauthorized, | ||
| + | |||
| + | Verification includes: | ||
| + | |||
| + | * Inspection of required Configuration Parameters and permitted Configuration Sources | ||
| + | * Inspection of Configuration Source identities, authorities, | ||
| + | * Resolution of literal, referenced, inherited, defaulted, and derived Configuration Values | ||
| + | * Comparison of resolved Configuration Values with their types, formats, units, ranges, and constraints | ||
| + | * A negative assessment involving a missing mandatory Configuration Value | ||
| + | * A negative assessment involving an unresolved reference or substitution | ||
| + | * A negative assessment involving conflicting or unauthorized Configuration Sources | ||
| + | * Confirmation that an invalid mandatory Configuration Value prevents Configuration Application | ||
| + | * Inspection of resolution records, 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> | ||
| + | </ | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||