Validating a process model

The validation process is not limited to a phase at the end of system development, but generally occurs at the end of a set of life cycle tasks or activities, and always at the end of each milestone of a development project.It may be performed on an iterative basis on every produced engineering element during development and may begin with the validation of the expressed stakeholder requirements.

With a note added in ISO 9005: validation is the set of activities that ensure and provide confidence that a system is able to accomplish its intended use, goals, and objectives (i.e., meet stakeholder requirements) in the intended operational environment (ISO 2005).When the validation process is applied to the system when completely integrated, it is often called final validation.It is important to remember that while system validation is separate from verification, the activities are complementary and intended to be performed in conjunction.Validation is based on tangible evidence; i.e., it is based on information whose veracity can be demonstrated by factual results obtained from techniques or methods such as inspection, measurement, test, analysis, calculation, etc.

Thus, to validate a system (product, service, or enterprise) consists of demonstrating that it satisfies its system requirements and eventually the stakeholder’s requirements depending on contractual practices.

Generally, the system-of-interest (So I) has been decomposed during design in a set of layers of systems.