Verification (VER) & Validation(VAL) : Goals and Practices

Validation (VAL)
An Engineering process area at Maturity Level 3
Purpose
The purpose of Validation (VAL) is to demonstrate that a product or product component fulfills its intended use when placed in its intended environment.
Specific Practices by Goal
SG 1 Prepare for Validation
SP 1.1 Select Products for Validation
SP 1.2 Establish the Validation Environment
SP 1.3 Establish Validation Procedures and Criteria
SG 2 Validate Product or Product Components
SP 2.1 Perform Validation
SP 2.2 Analyze Validation Results

Verification (VER)
An Engineering process area at Maturity Level 3
Purpose
The purpose of Verification (VER) is to ensure that selected work products meet their specified requirements.
Specific Practices by Goal
SG 1 Prepare for Verification
SP 1.1 Select Work Products for Verification
SP 1.2 Establish the Verification Environment
SP 1.3 Establish Verification Procedures and Criteria
SG 2 Perform Peer Reviews
SP 2.1 Prepare for Peer Reviews
SP 2.2 Conduct Peer Reviews
SP 2.3 Analyze Peer Review Data
SG 3 Verify Selected Work Products
SP 3.1 Perform Verification
SP 3.2 Analyze Verification Results

Examples of Verification & Validation activities

What is the difference between Validation & Verification

Verification is a Quality Control process that is used to evaluate
whether or not a product, service, or system complies with
regulations, specifications, or conditions imposed at the start of a
development phase. Verification can be in development, scale-up, or
production. This is often an internal process.

Validation is Quality assurance process of establishing evidence
that provides a high degree of assurance that a product, service, or
system accomplishes its intended requirements. This often involves
acceptance of fitness for purpose with end users and other product
stakeholders.

Verification: “are we building the product right”
Validation: “are we building the right product”

eQuality Jokes

Versions/Variants/Releases

Versions/Variants/Releases : These terms are often confused. hence it is important to know the differnce between what each of these stands for.

Version-An instance of a system which is functionally distinct in some way from other system instances.
Variant-An instance of a system which is functionally identical but non-functionally distinct from other instances of a system.
Release-An instance of a system which is distributed to users outside of the development team.

Various Configuration Management Tools

Below are few examples of Configuration Management Tools :

• VSS – Visual Source Safe for documents.
• VSTS - Visual Studio Team System
• VAJ - Visual Age for Java for source files.
• RCE – Revision Control Engine.
• Software Manager – Information from virtual sky.
• QVCS – Quma Version Control System.
• Source Code Manager.
• SCLM – Software Configuration Library Manager.
• CVS – Concurrent Version System.

What is a Configuration Mangement(CM) Plan

• Defines the types of documents to be managed and a document naming scheme.
• Defines who takes responsibility for the CM procedures and creation of baselines.
• Defines policies for change control and version management.
• Defines the CM records which must be maintained.
• Describes the tools which should be used to assist the CM process and any limitations on their use.
• Defines the process of tool use.
• Defines the CM database used to record configuration information.
• May include information such as the CM of external software, process auditing, etc