September 28 & 29, 2020 | Virtual
Please login or join to subscribe to this thread
Hate to sound dogmatic but:
QA is a control of processes (often against ISO 9000 or some standard(s). It involves audits.
QC is a control of products and involves test, reviews and (occasionally) simulations and mathmatical proving.
The two are sometimes confused :-)
Following is the difference between QA and QC.
a) In QC, only the end product is validated.
b) In QA, the end product delivered after every phase is validated and verified.
eg) w.r.t S/W development, testing the final binary is QC.
Performing Requirements review, design review, code review and then finally performing testing is QA. In QA the Quality at each and every phase is checked.
Yes, QC will be a subset of overall QA activities in place.
Interesting distinctions made between QA & QC especially the distinction between strategic and tactical. It will prove helpful to me. Always looking for new ways to describe things.
P Farrell-Vinay is correct IMO as a practitioner of QA for the last 10 tears.
This is also the definition supported by industry models like SEI CMMI-DEV, industry methods like OGC PRINCE2, and industry standards like IEC ISO9001.
Other definitions are still floating around, mostly because of the historical interchangeable use of QA and QC in the manufacturing industry. For example, if you look at a few plastic toys you'll see "QA Inspected" and "QC Inspected" labels; this shows a universal lack of understanding, and ignorance as to the benefit of having a different purpose and scope for each one.
Please login or join to reply