Revision as of 03:14, 19 January 2012

Validation is a set of actions used to check compliance of any element (a system element, a system, a document, a service, a task, a System Requirement, etc.) to its purpose. These actions are planned and carried out throughout the life cycle of the system. Validation is a generic term that needs to be instantiated within the context it occurs.

Validation understood as a process is a transverse activity to every life cycle stage of the system. In particular during the development cycle of the system, the Validation Process is performed in parallel of System Definition and System Realization processes, and applies onto any activity and product resulting from this activity. The Validation Process generally occurs at the end of a set of life cycle tasks or activities, and at least at the end of every milestone of a development project.

The Validation Process is not limited to a phase at the end of development of the system. It might be performed on an iterative basis on every produced engineering element during development and might begin with validation of expressed Stakeholder Requirements. The Validation Process applied onto the system when completely integrated is often called Final Validation.

Definition and Purpose

Definition of Validation: Confirmation, through the provision of objective evidence, that the requirements for a specific intended use or application have been fulfilled.

With a note added in ISO 9000:2005: Validation is the set of activities ensuring and gaining confidence that a system is able to accomplish its intended use, goals and objectives (i.e., meet stakeholder requirements) in the intended operational environment.

The purpose of Validation, as a generic action, is to establish compliance of any activity output, compared to inputs of this activity. Validation is used to prove that the transformation of inputs produced the expected, the "right" result.

Validation is based on tangible evidences; this means based on information whose veracity can be demonstrated, based on factual results obtained by techniques or methods such as inspection, measurement, test, analysis, calculation, etc.

So, validate a system (Product, Service, or Enterprise) consists in demonstrating that it satisfies its System Requirements and eventually to Stakeholders Requirements depending of contractual practices. From a purpose and a global point of view, validate a system consists in acquiring confidence in its ability to achieve its intended mission or use under specific operational conditions.

Principles

Concept of Validation Action

Validation Action – A Validation Action is defined then performed.

Definition of a Validation Action applied to an engineering element includes:

Identification of the element on which the Validation Action will be performed,
Identification of the reference to define the expected result of the Validation Action.

Performance of the Validation Action includes:

Obtaining a result from performance of the Validation Action onto the submitted element,
Comparing obtained result with expected result,
Deducing a degree of compliance of the element,
Deciding about acceptability of this compliance, because sometimes the result of the comparison may require a judgment of value regarding relevance in the context of use to accept or not the obtained result.

Note: If there is uncertainty about compliance, the cause could come from ambiguity in requirements.

References

Citations

Primary References

Primary references.

Additional References

Additional References.

Comments from 0.5 wiki

@@ Line 1: / Line 1: @@
-Placeholder Page for 0.75
+Validation is a set of actions used to check compliance of any element (a system element, a system, a document, a service, a task, a System Requirement, etc.) to its purpose. These actions are planned and carried out throughout the life cycle of the system. Validation is a generic term that needs to be instantiated within the context it occurs.
+Validation understood as a process is a transverse activity to every life cycle stage of the system. In particular during the development cycle of the system, the Validation Process is performed in parallel of System Definition and System Realization processes, and applies onto any activity and product resulting from this activity. The Validation Process generally occurs at the end of a set of life cycle tasks or activities, and at least at the end of every milestone of a development project.
+The Validation Process is not limited to a phase at the end of development of the system. It might be performed on an iterative basis on every produced engineering element during development and might begin with validation of expressed Stakeholder Requirements.
+The Validation Process applied onto the system when completely integrated is often called Final Validation.
+==Definition and Purpose==
+'''Definition of Validation:''' Confirmation, through the provision of objective evidence, that the requirements for a specific intended use or application have been fulfilled.
+With a note added in ISO 9000:2005: Validation is the set of activities ensuring and gaining confidence that a system is able to accomplish its intended use, goals and objectives (i.e., meet stakeholder requirements) in the intended operational environment.
+The purpose of Validation, as a generic action, is to establish compliance of any activity output, compared to inputs of this activity. Validation is used to prove that the transformation of inputs produced the expected, the "right" result.
+Validation is based on tangible evidences; this means based on information whose veracity can be demonstrated, based on factual results obtained by techniques or methods such as inspection, measurement, test, analysis, calculation, etc.
+So, validate a system (Product, Service, or Enterprise) consists in demonstrating that it satisfies its System Requirements and eventually to Stakeholders Requirements depending of contractual practices. From a purpose and a global point of view, validate a system consists in acquiring confidence in its ability to achieve its intended mission or use under specific operational conditions.
+==Principles==
+===Concept of Validation Action===
+'''Validation Action''' – A Validation Action is defined then performed.
+Definition of a Validation Action applied to an engineering element includes:
+* Identification of the element on which the Validation Action will be performed,
+* Identification of the reference to define the expected result of the Validation Action.
+Performance of the Validation Action includes:
+* Obtaining a result from performance of the Validation Action onto the submitted element,
+* Comparing obtained result with expected result,
+* Deducing a degree of compliance of the element,
+* Deciding about acceptability of this compliance, because sometimes the result of the comparison may require a judgment of value regarding relevance in the context of use to accept or not the obtained result.
+Note: If there is uncertainty about compliance, the cause could come from ambiguity in requirements.
 ==References==

Difference between revisions of "System Validation"