Log in


Demix Update September 2016
View this email in your browser
Dear Reader

Articles - VAL/VER

*Validation / Verification
Article: (VAL/VER)  In terms of CMMI what is the difference between Validation and Verification? by Rajendra Khare 

www.cmmiconsultantblog.com - In general we refer to the Verification as a Review activity and Validation as Test activity. But if we talk about CMMI then these terms have slightly different meaning.

From CMMI-Dev V1.3 Model:

The Verification and Validation process areas are similar, but they address different issues. Validation demonstrates that the product, as provided (or as it will be provided), will fulfill its intended use, whereas verification addresses whether the work product properly reflects the specified requirements. In other words, verification ensures that “you built it right”; whereas, validation ensures that “you built the right thing.”
Article: (VAL/VER)  Inception of Software Validation and Verification Practices within CMMI Level 2  by Ricardo J. Machado, Rick Kazman & Paula Monteiro.

Validation and verification are mandatory activities that software companies must perform when developing software products with a high degree of quality. Currently, more companies become aware that adopting CMMI (the software process maturity model developed by the Software Engineering Institute) can be a way to develop quality software. However, some companies are resistant to adopt CMMI maturity level 2 because they do not considerer this maturity level a benefit since its implementation is expensive and does not cover the validation and verification efforts. The simultaneous adoption of CMMI maturity level 2 with validation and verification process areas (from maturity level 3) lacks some methodological recommendations, since some dependencies exist between those two CMMI maturity levels. This PhD thesis will propose one approach to conciliate validation and verification practices with of CMMI maturity level 2 and by adopting ISO/IEC 29119 standard to fulfill a product lifecycle perspective.
Article: (VAL/VER) Verification (VER) (CMMI-DEV) by Wibas

The purpose of Verification (VER) (CMMI-DEV) is to ensure that selected work products meet their specified requirements.

Introductory Notes
The Verification (VER) (CMMI-DEV) process area involves the following: verification preparation, verification performance, and identification of corrective action. 

 Verification includes verification of the product and intermediate work products against all selected requirements, including customer, product, and product component requirements. For product lines, core assets and their associated product line variation mechanisms should also be verified. Throughout the process areas, where the terms “product” and “product component” are used, their intended meanings also encompass services, service systems, and their components. 

(Read more)

Article: (VAL/VER) Validation (VAL) An Engineering Process Area at Maturity Level 3 by software-quality-assurance 
www.software-quality-assurance.org - 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. 

 Introductory Notes  
Validation activities can be applied to all aspects of the product in any of its intended environments, such as operation, training, manufacturing, maintenance, and support services. The methods employed to accomplish validation can be applied to work products as well as to the product and product components. (Throughout the process areas, where we use the terms product and product component, their intended meanings also encompass services and their components.) The work products (e.g., requirements, designs, and prototypes) should be selected on the basis of which are the best predictors of how well the product and product component will satisfy user needs and thus validation is performed early and incrementally throughout the product lifecycle. 

 The validation environment should represent the intended environment for the product and product components as well as represent the intended environment suitable for validation activities with work products. 
Article: (VAL/VER)  What’s the difference between Verification and Validation, and how do I figure out which project practices support which process area? by Pat O’Toole and Jeff Dalton

www.askthecmmiappraiser.blogspot.co.za - [Dear Readers, for the past several months, our good friend Pat O’Toole, CMMI expert and seasoned consultant, has been collaborating with us on a monthly series of CMMI-related posts, "Just the FAQs." Our goal with these posts is to provide answers to the most frequently asked questions about the CMMI, SCAMPI, engineering strategy and software process improvement. This month Pat clarifies some of the misconceptions about Verification and Validation.  Take it away, Pat! ~ the CMMI Appraiser]

[PAT: Note – there are a number of verification/validation misconceptions I am going to address in this article.  In other words, I’m not going to constrain myself to answering the question – but why shouldn’t THAT surprise you!] 

The CMMI addresses this question very explicitly, and yet the question keeps coming up.  In the “Introductory Notes” of BOTH Verification and Validation, the model states: “verification ensures that ‘you built it right;’ whereas validation ensures that ‘you built the right thing.”  All you have to do is follow that advice and you can’t go wrong differentiating between the two.
Downloads: (VAL/VER)  
(Login to view*)                                          
VAL Self assessment - (Login to view)
VER Self assessment - (Login to view)
Self assessment - (Login to view)


Appraisal services

This email address is being protected from spambots. You need JavaScript enabled to view it.


(Login to view all)
Related Articles 
Other Articles  

Comments powered by CComment