Software quality control is the set of procedures used by organizations[1] to ensure that a software product will meet its quality goals at the best value to the customer,[2] and to continually improve the organization’s ability to produce software products in the future.[1]

Software quality control refers to specified functional requirements as well as non-functional requirements such as supportability, performance and usability.[2] It also refers to the ability for software to perform well in unforeseeable scenarios and to keep a relatively low defect rate.

These specified procedures and outlined requirements lead to the idea of Verification and Validation and software testing.

It is distinct from software quality assurance which encompasses processes and standards for ongoing maintenance of high quality of products, e.g. software deliverables, documentation and processes - avoiding defects. Whereas software quality control is a validation of artifacts compliance against established criteria - finding defects.


Software quality control is a function that checks whether a software component, or supporting artifact meets requirements, or is "fit for use". Software Quality Control is commonly referred to as Testing.

Quality Control Activities

Software Control Methods

Verification and validation

Verification and validation assure that a software system meets a user's needs.

Verification: "Are we building the product right?" The software should conform to its specification.

Validation: "Are we building the right product?" The software should do what the user really requires.

Two principal objectives are:

Verification and Validation of Methods

This list is incomplete; you can help by adding missing items. (February 2011)


See also


  1. ^ a b c Clapp, Judith A, Software Quality Control, Error Analysis, and Testing, 1995 William Andrew In.
  2. ^ a b