Skip to main content

Quality Assurance vs. Quality Control

            Quality Assurance

            Quality Control

Definition:   
QA is a set of activities for ensuring quality in the processes by which products are developed.
QC is a set of activities for ensuring quality in products. The activities focus on identifying defects in the actual products produced.
Focus on:   
QA aims to prevent defects with a focus on the process used to make the product. It is a proactive quality process.
QC aims to identify (and correct) defects in the finished product. Quality control, therefore, is a reactive process.
Goal:  
The goal of QA is to improve development and test processes so that defects do not arise when the product is being developed.
The goal of QC is to identify defects after a product is developed and before it's released.
How:  
Establish a good quality management system and the assessment of its adequacy. Periodic conformance audits of the operations of the system.
Finding & eliminating sources of quality problems through tools & equipment so that customer's requirements are continually met.
What:  Prevention of quality problems through planned and systematic activities including documentation.
The activities or techniques used to achieve and maintain the product quality, process and service.
Responsibility:  
Everyone on the team involved in developing the product is responsible for quality assurance.
Quality control is usually the responsibility of a specific team that tests the product for defects.
Example:  
Verification is an example of QA
Validation/Software Testing is an example of QC
Statistical Techniques:  
Statistical Tools & Techniques can be applied in both QA & QC. When they are applied to processes (process inputs & operational parameters), they are called Statistical Process Control (SPC); & it becomes the part of QA.
When statistical tools & techniques are applied to finished products (process outputs), they are called as Statistical Quality Control (SQC) & comes under QC.
As a tool:  
QA is a managerial tool

In the ISO 9000 standard, clause 3.2.10 defines Quality Control as:
“A part of quality management focused on fulfilling quality requirements”

Clause 3.2.11 defines Quality Assurance as:
“A part of quality management focused on providing confidence that quality requirements will be fulfilled”
QC is a corrective tool








Comments

Popular posts from this blog

Effective Scrum Meeting

Overview: The Daily Scrum Meeting is held every day through the sprint. At the meeting, the Scrum team gathers to review and synchronize about the project status. In theory, each team member should provide his/her status based on three (03) Q: What did you do yesterday? What do you intend to do today? Is there any issues that blocks your work? # The participants should come prepared: Stop participants that don't come prepared and waste the meeting time. The team members should come prepared to share their updates. You should describe how to answer these questions effectively to increase the synchronization among the team members. The team members should know what is your expectations from them while answering these questions. # Validate that each individual describe the full picture: Validate that each individual can answer the 3 questions (Do not continue until you get the answers or the reasons for why he can't provide them). Validate that each tea...

GitHub- how it works

GitHub: GitHub is a platform for hosting and collaborating on projects. We don’t have to worry about losing data on our hard drive or managing a project across multiple computers — sync from anywhere. GitHub Essentials:   Repositories ,   Branches , Commits ,   Issues   and   Pull Requests . A   repository   is the basic unit of GitHub, most commonly a single project.  Repositories can contain folders and files, including images – anything our project needs. Repository = single project = single folder which contains subfolders and files. Sometimes GitHub users shorten this to “repo.” Branching   is the way to work on different parts of a repository at one time. When we are working on a project, we are going to have a bunch of different features or ideas in progress at any given time – some of which are ready to go, and others which are not. Branching exists to help we manage this workflow. When we create ...

Verification and Validation (V&V)- a software testing approach

Verification: It focuses on PROCESS related activities to ensure that the Products and deliverables meet a specific requirement before the final testing. Can be done through: A. Technical review B. Business review C. Management review Simply: Are we building the product in the right way?  that is, does the software conform to its specification verification  is the process of checking that the software meets the specification. Verification is an example of QA Validation: It focuses on PRODUCT related activities, that attempt to determine if the system or project deliverables meet the customer or client's expectations. Will be done by: Testing. Simply: Did we build the right product?  that is, is the software doing what the user really requires. Validation  is the process of checking whether the specification captures the customer's needs. According to the Capability Maturity Model(CMMI-SW v1.1) we can also define validation as The process ...