Tuesday, April 1, 2008

Establishing the Verification Environment

VER SP 1.2 is “Establish and maintain the environment to support verification.” Companion practices are OPD SP 1.6 “Establish and maintain work environment standards.” And IPM SP 1.3 “Establish and maintain the project’s work environment based on the organization’s work environment standards.”

So what this all means is that you have to define at the organization level what the standards are for verification environments, in IPM define the project’s verification environment(s) in the project plan, and in VER define what the various verification environments are. When you consider VER, there are at least two and possibly more verification environments depending on the system you are developing. At a minimum you have a peer review environment and a product testing environment. Both of these environments have requirements, resources, equipment, and tools which you will have to define yourself. In the case of peer reviews and inspections the environment is many times just the conference room with a whiteboard, LAN connection, computer, and a projector, plus other requirements. The testing environment may be a specific room and equipment set aside as a testing lab, etc. So, to implement VER SP 1.2 you have to define the requirements for each verification environment that you have defined for the project, along with the resources, equipment, and tools, and then the acquisition of these items to actually construct and maintain the environment(s), which also include upgrades over time.

And keep in mind the CMMI definition of the phrase “establish and maintain”, which means formulate, document, and use. Therefore you need to design the environment, document the environment, and use the environment for verification.


QA_Tester said...

In our organization we conduct reviews as part of verification process.We have internal testing like unit testing,functional testing etc before the product goes to the UAT phase.Are these also Verification activities? In that case does only prototype validation & UAT comes under the real validation processess?can u pls clarify them?

Henry Schneider said...

Yes, all of your testing examples are considered verification activities. Look in the CMMI Glossary for the definitions of verification and validation. Basically any activities that you perform from the customer's or user's perspective or with the customer involvement is a validation activity. I am not clear what you mean by prototype validation, but I suspect you may not be using the word validation in the same sense as the CMMI. However, UAT is a validation activity. And so is requirements validation.

QA_Tester said...

Thanks Schneider