Configuration Validation [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Configuration Validation ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]

===== Discussion =====

Configuration Validation determines whether an intended, resolved, or applied [[dido:99_annexes:annex-b-terms-and-definitions:n:node_configuration|Node Configuration]] satisfies the applicable configuration criteria.

The applicable criteria address completeness, data types, formats, units, permitted ranges, relationships, constraints, source authority, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_precedence|Configuration Precedence]], security controls, [[dido:99_annexes:annex-b-terms-and-definitions:n:node_binding|Node Bindings]], and compatibility with the applicable Node Definition, Node Implementation, environment, and operating state.

Configuration Validation distinguishes among the intended configuration, the values produced by [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_resolution|Configuration Resolution]], and the configuration established through [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_application|Configuration Application]]. Comparison among these states identifies omissions, substitutions, conflicts, drift, application failures, and unauthorised changes.

Configuration Validation remains distinct from Test Execution. Configuration Validation evaluates configuration against configuration criteria. [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]] executes a Test Definition to evaluate a Test Object against specified test criteria.

===== Definition =====

//process that determines whether a Node Configuration satisfies applicable configuration criteria//

===== Source =====

DIDO Solutions project definition.

===== Note =====

Configuration Validation identifies the configuration revision, configured Node instance, validation criteria, validation method, responsible actor or process, observed results, findings, exceptions, and validation outcome.

Validation occurs before application, during application, after application, or during continuing operation. Each validation activity identifies the configuration state evaluated.

A successful validation result establishes conformity with the specified configuration criteria. It does not independently establish the correctness, security, or suitability of the Node for every operational purpose.

Validation results recorded in a [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_record|Configuration Record]] support [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]].

===== Example =====

Configuration Validation confirms that a publishing Node uses the approved DDS domain, topic, partition, Quality of Service profile, Credential reference, and network interface specified for the Test Environment.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>