Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:v:validation [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:v:validation [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Validation ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | Validation is the evaluation of an identified subject against defined [[public: | ||
| + | |||
| + | Validation determines whether available information supports a [[public: | ||
| + | |||
| + | Validation can evaluate: | ||
| + | |||
| + | * Suitability for an intended use | ||
| + | * Satisfaction of stakeholder needs | ||
| + | * Satisfaction of operational objectives | ||
| + | * Satisfaction of specified capabilities | ||
| + | * Behavior under defined conditions | ||
| + | * Interoperability | ||
| + | * Performance | ||
| + | * Reliability | ||
| + | * Security | ||
| + | * Compliance | ||
| + | * Another defined validation purpose | ||
| + | |||
| + | Validation can use: | ||
| + | |||
| + | * Inspection | ||
| + | * Analysis | ||
| + | * Demonstration | ||
| + | * Testing | ||
| + | * Modeling | ||
| + | * Simulation | ||
| + | * Measurement | ||
| + | * Observation | ||
| + | * Expert evaluation | ||
| + | * A combination of evaluation methods | ||
| + | |||
| + | Validation can consider: | ||
| + | |||
| + | * Applicable Validation Criteria | ||
| + | * Applicable [[public: | ||
| + | * Applicable [[public: | ||
| + | * Applicable [[public: | ||
| + | * Applicable [[public: | ||
| + | * Applicable [[public: | ||
| + | * Applicable [[public: | ||
| + | * Applicable [[public: | ||
| + | * Applicable [[public: | ||
| + | * Applicable [[public: | ||
| + | * Applicable exceptions and limitations | ||
| + | |||
| + | Validation should preserve [[public: | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Adapted from: | ||
| + | |||
| + | * ISO/ | ||
| + | * ISO/IEC 17029:2019, Conformity assessment — General principles and requirements for validation and verification bodies | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * DIDO Reference Implementation Conceptual Model | ||
| + | * DIDO-TE draft Requirements Register | ||
| + | |||
| + | ISO and systems-engineering usage associate Validation with evaluating suitability or satisfaction for an intended use or stated purpose. | ||
| + | |||
| + | This definition applies that purpose-oriented evaluation to DIDO-TE while separating the Validation activity from the resulting Validation Decision. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | Validation differs from a [[public: | ||
| + | |||
| + | * Validation is the evaluation activity | ||
| + | * A Validation Decision records the resulting determination | ||
| + | |||
| + | Validation differs from testing: | ||
| + | |||
| + | * Testing performs defined test activities and produces Test Results | ||
| + | * Validation evaluates whether the available information supports satisfaction of the Validation Criteria for the stated purpose | ||
| + | |||
| + | Testing can provide Evidence for Validation. Validation can also use inspection, analysis, demonstration, | ||
| + | |||
| + | Validation differs from verification: | ||
| + | |||
| + | * Verification evaluates whether a subject satisfies specified requirements | ||
| + | * Validation evaluates whether a subject satisfies Validation Criteria for a stated purpose or intended use | ||
| + | |||
| + | The same Test Results and Evidence can support both verification and Validation when the applicable criteria require them. | ||
| + | |||
| + | Validation does not establish universal validity. A positive Validation Decision applies only to: | ||
| + | |||
| + | * The identified subject | ||
| + | * The stated validation purpose | ||
| + | * The applicable Validation Criteria | ||
| + | * The applicable Baseline | ||
| + | * The evaluated conditions | ||
| + | * The available Evidence | ||
| + | * The applicable effective period | ||
| + | * The recorded limitations and exceptions | ||
| + | |||
| + | A subject validated for one purpose, configuration, | ||
| + | |||
| + | Validation can produce a positive, negative, conditional, | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | DIDO-TE performs Validation of a selected Node Set for use in a defined distributed transaction scenario. | ||
| + | |||
| + | The Validation: | ||
| + | |||
| + | * Identifies the Node Set and its Versions | ||
| + | * Identifies the stated validation purpose | ||
| + | * Selects the applicable Validation Criteria | ||
| + | * Selects the approved Test Definitions | ||
| + | * Reviews the applicable Test Runs | ||
| + | * Evaluates the resulting Test Results and Verdicts | ||
| + | * Reviews the supporting Evidence | ||
| + | * Accounts for applicable limitations and exceptions | ||
| + | * Preserves Provenance and Traceability | ||
| + | |||
| + | An authorized Evaluator uses the Validation output to make and record the applicable Validation Decision. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||