Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

Software quality assurance

From Wikipedia, the free encyclopedia
Means of monitoring the software engineering process
This article includes a list ofgeneral references, butit lacks sufficient correspondinginline citations. Please help toimprove this article byintroducing more precise citations.(April 2019) (Learn how and when to remove this message)
IEEE software life cycle

Software quality assurance (SQA) is a means and practice of monitoring allsoftware engineeringprocesses, methods, and work products to ensure compliance against defined standards.[1] It may include ensuring conformance to standards or models, such asISO/IEC 9126 (now superseded by ISO 25010),SPICE orCMMI.[2]

It includes standards and procedures that managers, administrators or developers may use to review and audit software products and activities to verify that the software meets quality criteria which link to standards.

SQA encompasses the entiresoftware development process, includingrequirements engineering,software design,coding,code reviews,source code control,software configuration management,testing,release management andsoftware integration. It is organized into goals, commitments, abilities, activities, measurements,verification and validation.[3]

Purpose

[edit]
This sectionis inlist format but may read better asprose. You can help byconverting this section, if appropriate.Editing help is available.(November 2019)

SQA involves a three-pronged approach:

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

Guidelines for the application of ISO 9001:2015 to computer software are described in ISO/IEC/IEEE 90003:2018.[4] External entities can be contracted as part of process assessments to verify that projects are standard-compliant. More specifically in case of software,ISO/IEC 9126 (now superseded by ISO 25010) should be considered and applied for software quality.

Activities

[edit]

Quality assurance activities take place at each phase of development. Analysts use application technology and techniques to achieve high-quality specifications and designs, such asmodel-driven design. Engineers and technicians find bugs and problems with related software quality through testing activities. Standards and process deviations are identified and addressed throughout development byproject managers or quality managers, who also ensure that changes to functionality, performance, features, architecture and component (in general: changes to product or servicescope) are made only after appropriate review, e.g. as part ofchange control boards.[5]

See also

[edit]

References

[edit]
  1. ^"What is Software Quality Assurance (SQA): A Guide for Beginners".Software Testing Help. Retrieved2022-06-02.
  2. ^Kelemen, Zádor Dániel; Kusters, Rob; Trienekens, Jos (December 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.S2CID 14382496.
  3. ^Nielsen, DavidCMM and Project Quality Management
  4. ^"ISO/IEC/IEEE 90003:2018".ISO. Retrieved2020-07-14.
  5. ^Wieczorek, Martin; Vos, Diederik; Bons, Heinz (2014-05-08).Systems and Software Quality: The next step for industrialisation. Springer Science & Business Media.ISBN 978-3-642-39971-8.
Wikimedia Commons has media related toSoftware quality assurance.


External links

[edit]
Qualities
Internal
External
Standards and lists
Processes
Fields
Concepts
Orientations
Models
Developmental
Other
Languages
Related fields
Current
802 series
802
802.1
802.3
(Ethernet)
802.11
(Wi-Fi)
802.15
Proposed
Superseded
Retrieved from "https://en.wikipedia.org/w/index.php?title=Software_quality_assurance&oldid=1228411697"
Categories:
Hidden categories:

[8]ページ先頭

©2009-2025 Movatter.jp