Software quality assurance

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Software quality assurance (SQA) is a means of monitoring the software engineering processes and methods used to ensure proper quality. This is accomplished by many and varied approaches. It may include ensuring conformance to one or more standards, such as ISO 9000 or a model such as CMMI.[1]

It includes standards and procedures that administrators may use to review and audit software products and activities to verify that the software meets standards. According to ISO/IEC 15504 v.2.5 (SPICE), it is a supporting process that provides the independent assurance that all work products, activities and processes comply with the predefined plans and ISO 15504.[citation needed]

SQA encompasses the entire software development process, including requirements definition, software design, coding, code reviews, source code control, software configuration management, testing, release management and product integration. It is organized into goals, commitments, abilities, activities, measurements and verification.[2]


SQA involves a three-prong approach:

  • Organization-wide policies, procedures and standards
  • Project-specific policies, procedures and standards
  • Compliance to appropriate procedures

Standards that inform software quality assurance plans:

  • ISO 9000-3 (original), now ISO 90003ANSI/IEEE

External entities can be contracted to verify that projects are standard-compliant.


Quality assurance activities take place at each phase of development.

Analysts use application technology to achieve high-quality specifications and designs.

Technicians find problems with related software quality through meetings.

Tests are created by developers and/or dedicated testers for each significant use case.

Standards violations are identified and addressed throughout development.

Product/program managers ensure that feature/architecture/component changes are made only after appropriate review.

The team monitors statistics about defect discovery, severity and fix rates.

See also[edit]


External links[edit]

  • 730-2014 - IEEE Standard for Software Quality Assurance Processes. 2014. doi:10.1109/IEEESTD.2014.6835311. ISBN 978-0-7381-9168-3.
  • April, Alain (2018). Software Quality Assurance. Wiley-IEEE. ISBN 978-1-11850-182-5.
  • Chemuturi, Murali (2010). Software Quality Assurance: Best Practices, Tools and Techniques for Software Developers. J.Ross Publishing. ISBN 978-1-60427-032-7.
  • Kelemen, Z. D.; Kusters, R.; Trienekens, J. (2012). "Identifying criteria for multimodel software process improvement solutions - based on a review of current problems and initiatives". Journal of Software: Evolution and Process. 24 (8): 895–909. doi:10.1002/smr.549.
  • Auburn University Libraries. Auburn University Libraries / Illiad @ Auburn Libraries,
  • "Software Quality Assurance(SQA): Plan, Audit & Review." Meet Guru99 - Free Training Tutorials & Video for IT Courses,
  • Collofello, James S., and Jeffrey J. Buck. "Software Quality Assurance for Maintenance." IEEE Software, vol. 4, no. 5, Sept. 1987, p. 46. EBSCOhost, doi:10.1109/MS.1987.231418
  • Parnas, David L., and Mark Lawford. "Inspection's Role in Software Quality Assurance." IEEE Software, vol. 20, no. 4, July 2003, p. 16. EBSCOhost, doi:10.1109/MS.2003.1207449.
  • Laporte, Claude Y., and Alain April. Software Quality Assurance. IEEE Press, 2018.