Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I know that verification is QC (focused on products) but what about validation? I would say its QC too, as it does aim on the product workings, yet no source mentiones that. I am trying to understand, in QA/QC, where these activities belong to.

share|improve this question
up vote 5 down vote accepted

If we agree in principle that

  • validation is regarded as "building the right software," and
  • verification is "building the software right," and
  • QC is quality control helps identify defects in the product via testing, and
  • QA is quality assurance intended to help prevent defects in the product through process management

then, one position is that both validation and verification are aspects of quality control, although someone could also argue that validating we are building the right product is an aspect of quality assurance because we are driving 'quality' upstream.

In my view modern software testing requires being involved in both validation and verification and the role also entails aspects of QC and QA.

While it may be important to understand these differences conceptually I question the value in slicing and dicing these roles and/or tasks in practice unless the company revolves around a rigid set of rules carried out by process droids, or someone wants/needs to pigeon hole labels in artificial silos.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.