Jump to content

Software quality assurance

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Bongwarrior (talk | contribs) at 10:03, 2 February 2017 (Reverted edits by Yana.gusti (talk) to last version by Klbrain). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Software quality assurance (SQA) consists of a means of monitoring the software engineering processes and methods used to ensure quality.[citation needed] The methods by which this is accomplished are many and varied, and may include ensuring conformance to one or more standards, such as ISO 9000 or a model such as CMMI.[1]

SQA encompasses the entire software development process, which includes processes such as requirements definition, software design, coding, source code control, code reviews, software configuration management, testing, release management, and product integration. SQA is organized into goals, commitments, abilities, activities, measurements, and verifications.[2]

Software quality assurance, according to ISO/IEC 15504 v.2.5 (SPICE), is a supporting process that has to provide the independent assurance in which all the work products, activities and processes comply with the predefined plans and ISO 15504.[citation needed]

See also

References

  • 730-2014 - IEEE Standard for Software Quality Assurance Processes. 2014. doi:10.1109/IEEESTD.2014.6835311. ISBN 978-0-7381-9168-3.
  • 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). Wiley and Sons: 895–909. doi:10.1002/smr.549. Retrieved 17 August 2014.