Validation Criteria

Go up to Terms and Definitions

Discussion

Validation Criteria are the conditions used to determine whether an evaluated subject satisfies a stated validation purpose.

Validation Criteria can apply to:

A NodeA Node SetA distributed systemA Test EnvironmentA Deployment TargetAn ArtifactA BaselineA configurationA capabilityA processA requirementAnother subject of ValidationValidation Criteria can establish:

Required capabilitiesRequired behaviorsRequired statesRequired state transitionsRequired outputsRequired performance thresholdsRequired timing constraintsRequired security propertiesRequired reliability propertiesRequired interoperability propertiesPermitted tolerancesPermitted exceptionsRequired Test ResultsPermitted VerdictsRequired EvidenceAggregation and arbitration rulesConditions for a positive, negative, conditional, or inconclusive Validation DecisionValidation Criteria can identify:

The evaluated subjectThe validation purposeThe applicable scopeThe applicable BaselineThe applicable Test DefinitionsThe applicable Acceptance CriteriaThe required Test ResultsThe permitted VerdictsThe required EvidenceThe permitted tolerancesThe permitted exceptionsThe decision rulesThe authorized decision-makerThe applicable PoliciesThe applicable Governance PoliciesTheir effective timeTheir ProvenanceTheir Traceability

Definition

conditions used to determine whether an evaluated subject satisfies a stated validation purpose

Source

Adapted from:

ISO/IEC/IEEE 15288:2023, Systems and software engineering — System life cycle processesDIDO Reference Implementation Conceptual ModelDIDO-TE draft Requirements Register

Note

Validation Criteria differ from Acceptance Criteria:

Validation Criteria establish the conditions used to determine whether a subject satisfies a stated validation purposeAcceptance Criteria establish the conditions used to determine whether an evaluated subject or outcome is acceptableThe same condition can serve as both a Validation Criterion and an Acceptance Criterion when the validation and acceptance purposes align.

Validation Criteria differ from Expected Results:

An Expected Result specifies an anticipated outcome associated with a Sequenced Test Object or Sequence StepValidation Criteria determine how the relevant outcomes contribute to the Validation DecisionValidation Criteria differ from requirements:

A requirement states an obligation that an identified subject must satisfyValidation Criteria establish how an authorized Actor evaluates whether the subject satisfies the stated validation purposeValidation Criteria must be sufficiently clear, measurable, and bounded to support repeatable application.

Statements such as the following do not establish adequate Validation Criteria without additional measurable conditions:

Performs correctlyOperates efficientlyProvides adequate securityProduces acceptable resultsSupports appropriate interoperabilityValidation Criteria do not need to require perfection. They can permit:

Defined tolerancesKnown limitationsApproved exceptionsConditional satisfactionSpecified numbers or types of failuresThe applicable Governance Policy must identify how those conditions affect the Validation Decision.

Validation Criteria must identify the applicable validation purpose. Criteria suitable for one intended use do not necessarily support another intended use.

Example

Validation Criteria determine whether a selected Node Set supports a defined distributed transaction scenario.

The Validation Criteria require:

Every required Node to join the Node SetEvery required transaction to reach the expected committed stateEvery committed state to reference its predecessorNo prohibited duplicate stateEvery required response to occur within five secondsEvery required Test Result to receive a PASS VerdictEvery Test Run to preserve the required EvidenceNo unresolved ERROR or INCONCLUSIVE VerdictAn authorized Actor applies these Validation Criteria when making the Validation Decision.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.