Process ID

VAL.1

Process name

Validation

Process purpose

The purpose is to provide evidence that the end product, allowing direct end user interaction, satisfies the intended use expectations in its operational target environment.

Process outcomes

Note 1: Validation measures are specified that are suitable to provide evidence for satisfaction of the intended use expectations in the operational target environment;

1) Validation measures are selected considering criteria for regression verification;

2) The product is validated using the selected validation measures and the results of validation are recorded;

3) Consistency and unidirectional traceability are established between validation measures and stakeholder requirements; and consistency and bidirectional traceability is established between validation results and validation measures;

4) Results of the validation are summarized and communicated to all affected parties.

Base practices

VAL.1.BP1: Specify validation measures for product validation. Specify the validation measures for the end product based on the stakeholder requirements to provide evidence that it fulfills its intended use expectations in its operational target environment, and

 techniques for the validation measures;

 pass/fail criteria for validation measures;

 a definition of entry and exit criteria for the validation measures;

 necessary sequence of validation measures;

 the required validation infrastructure and environment setup.

Note 1: An example for validation-relevant stakeholder requirements are homologation or legal type approval requirements. Further examples of sources of intended use expectations are technical risks (see MAN.5, SYS.3.BP4, SWE.2.BP3, HWE.2.BP6).

Note 2: Where stakeholder requirements cannot be specified comprehensively or change frequently, repeated validation of (often rapidly developed) increments in product evolution may be employed to refine stakeholder requirements, and to mitigate risks in the correct identification of needs.

Note 3: Validation may also be conducted to confirm that the product also satisfies the often less formally expressed, but sometimes overriding, attitudes, experience, and subjective tests that comprise stakeholder or end user satisfaction.

VAL.1.BP2: Select validation measures. Document the selection of validation measures considering selection criteria including criteria for regression validation. The documented selection of validation measures shall have sufficient coverage according to the release scope.

Note 4: Examples for criteria for selection can be the release purpose of the delivered product (such as test bench, test track, validation on public roads, field use by end users), homologation/ type approval, confirmation of requirements, or the need for regression due to e.g. changes to stakeholder requirements and needs.

VAL.1.BP3: Perform validation and evaluate results. Perform the validation of the integrated system using the selected validation measures. Record the validation results including pass/fail status. Evaluate the validation results.

Note 5: Validation results can be used as a means for identifying stakeholder or system requirements

e.g. in the case of mock-ups or concept studies.

Note 6: See SUP.9 for handling of non-conformances and SUP.10 for raising change requests.

VAL.1.BP4: Ensure consistency and establish traceability. Ensure consistency and establish bidirectional traceability from validation measures to the stakeholder requirements from which they are derived. Establish bidirectional traceability between validation results and validation measures.

Note 7: Examples of sources of validation measures from which they can be derived are legal requirements, homologation requirements, results of technical risk analyses, or stakeholder and system requirements (see SYS.1 and SYS.2).

Note 8: If sources of validation measures source are e.g. legal or homologation requirements, then direct bidirectional traceability from those sources to the validation measures are not possible. In such a case, unidirectional traceability is sufficient.

Note 9: Bidirectional traceability supports consistency, and facilitates impact analyses of change requests, and demonstration of verification coverage.

VAL.1.BP5: Summarize and communicate results. Summarize the validation results and inform all affected parties.

Note 10: Providing all necessary information from the test case execution in a summary enables other parties to judge the consequences.

VAL.1 Validation

Outcome 1

Outcome 2

Outcome 3

Outcome 4

Outcome 5

Outcome 6

Output Information Items

08-59 Validation Measure

X

08-58 Validation Measure Selection Set

X

13-24 Validation Results

X

13-51 Consistency Evidence

X

X

13-52 Communication Evidence

X

Base Practices

BP1: Specify validation measures

X

BP2: Select validation measures

X

BP3: Perform validation and evaluate results

X

BP4: Ensure consistency and establish traceability.

X

X

BP5: Summarize and communicate results

X