Write-up on QA and QC:

 QA is not QC . The term QA and QC are often used incorrectly. The difference is that QA is Process oriented and QC is product oriented. Testing therefore is product oriented and thus is in the QC domain. Testing for quality is not assuring quality, its controlling it so it a QC activity.

 QC is the most basic level of quality.  It started with activities whose purpose is to control the quality of products or services by finding problems and defects. At its simplest, QC is inspecting, testing or checking something (service or product) to make sure it's OK.  The intent is to identify anything that isn't OK, and either fix it or eliminate it, to make sure it conforms to the specifications, and has/does/functions as required. 

 Quality assurance make sure that you are doing the right things ,the right way . Quality control make sure the result of what you have done are what we have expected . QC is the responsibility of the worker but QA is the management responsibility

 The QA team's job is to see that standards, processes, and policies (or other guidelines) are in place and carried out; to recommend and implement improvements to them, and to ensure that the people that need to know about them know about them. QA "audits" or "reviews" are intended to determine the efficacy of these "governance."

 Assuring quality is about confidence. It's about the *processes* by which we go about doing what we do. Part of that is knowing that we're doing the right things at the right time, and part of it is that we are doing them the right way. This all should be done or known before we start working, not afterwards.

 QA dealt with manufacturing processes, while QC inspected the manufacturing output to verify that it was acceptable. In the manufacturing environment you analyze, design, and implement once and then crank out many essentially identical products. This is very different from the software environment where the analysis, design, and

 implementation happen on each product, and then you start over for the next iteration.

 Quality means meeting requirements and meeting customer needs, which means a defect-free product from both the producer’s and the customer’s viewpoint. Both quality control and quality assurance are used to make quality happen. Of the two, quality assurance is the more important.

 In a software environment, "Quality Assurance" does not assure quality. Rather, they assure that a process is being followed, which is very different. The process, if it's a good process, will increase the probability that there is a quality result. It will, presumably, make sure that requirements are communicated, tracked, planned for, scheduled, etc. The "Quality Assurance" role will likely also collect metrics that it can then use for process improvement. However, this QA group could do its job and still have the organization's product be low-quality. Therefore this function would be better termed "Process Management." It is aimed at preventing nonconformities/defects.

 Similarly, "Quality Control" does not control quality. Rather they measure quality, by verifying that what was implemented matches the requirements. Certainly there's a feedback loop, as any defects will be reported and presumably fixed, thus increasing quality. But this group doesn't really control anything. It would thus be better termed "Requirements Verification," although "Product Test" is more concise.

 Calling these functions Process Management and Product Test removes any ambiguity or confusion. And calling them by these names does not impact your ability to get ISO 9000 certification or achieve a CMM level. Those require certain things to be done or documented, and require certain functions to be executed by the organization, but absolutely do not require specific organizational names.