Software Quality Knowledge Area

This knowledge area deals with software quality considerations that transcend the lifecycle processes. Since software quality is a ubiquitous concern in software engineering, it is also considered in many of the other knowledge areas. The knowledge area description covers four sub-areas.

The first sub-area describes the software quality concepts such as measuring the value of quality, the ISO 9126 quality description, dependability, and other special types of system and quality needs.

The second sub-area covers the purpose and planning of software quality assurance (SQA) and verification and validation (V&V). It includes common planning activities, and both the SQA and V&V plans.

The third sub-area describes the activities and techniques for SQA and V&V. It includes static and dynamic techniques as well as other SQA and V&V testing.

The fourth sub-area describes measurement applied to SQA and V&V. It includes the fundamentals of measurement, measures, measurement analysis techniques, defect characterization, and additional uses of SQA and V&V data.

The above summary was adapted from the Introduction to the IEEE Computer Society's SWEBOK Guide. For more information on the Software Requirements Knowledge Area, read Chapter 11 of the SWEBOK Guide.

Standards

Standard:

Title:

Abstract:

IEEE Std 730™-2002

IEEE Standard for Software Quality Assurance Plans

The standard specifies the format and content of software quality assurance plans. It meets the IEEE/EIA 12207.1 requirements for such plans.

 IEEE Std 829™-1998

IEEE Standard for Software Test Documentation

A set of basic software test documents is described. This standard specifies the form and content of individual test documents. It does not specify the required set of test documents.

IEEE Std 982.1™-1988

IEEE Standard Dictionary of Measures to Produce Reliable Software

This standard provides a set of measures indicative of software reliability that can be applied to the software product as well as to the development and support processes. It was motivated by the need of software developers and users who are confronted with a plethora of models, techniques, and measures. There is a need for measures that can be applied early in the development process that may be indicators of the reliability of the delivered product. This standard provides a common, consistent definition of a set of measures that may meet those needs.

IEEE Std 1008™-1987 (R1993)

 

IEEE Standard for Software Unit Testing

This standard's primary objective is to specify a standard approach to software unit testing that can be used as a basis for sound software engineering practice. A second objective is to describe the software engineering concepts and testing assumptions on which this standard approach is based. ... A third objective is to provide guidance and resource information to assist with the implementation and usage of the standard unit testing approach.

IEEE Std 1012™-1998

IEEE Standard for Software Verification and Validation

Software verification and validation (V&V) processes, which determine whether development products of a given activity conform to the requirements of that activity, and whether the software satisfies its intended use and user needs, are described. This determination may include analysis, evaluation, review, inspection, assessment, and testing of software products and processes. V&V processes assess the software in the context of the system, including the operational environment, hardware, interfacing software, operators, and users.

IEEE Std 1012a™-1998

 

Supplement to IEEE Standard for Software Verification and Validation: Content Map to IEEE/EIA 12207.1-1997

The relationship between the two sets of requirements on plans for verification and validation of software, found in IEEE Std 1012-1998 and IEEE/EIA 12207.1-1997, is explained so that users may produce documents that comply with both standards.

IEEE Std 1028™-1997

IEEE Standard for Software Reviews

This standard defines five types of software reviews, together with procedures required for the execution of each review type. This standard is concerned only with the reviews; it does not define procedures for determining the necessity of a review, nor does it specify the disposition of the results of the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and audits.

IEEE Std 1044™-1993

 

IEEE Standard Classification for Software Anomalies

A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.

IEEE Std 1061™-1998

 

IEEE Standard for a Software Quality Metrics Methodology

A methodology for establishing quality requirements and identifying, implementing, analyzing, and validating the process and product software quality metrics is defined. The methodology spans the entire software life cycle.

IEEE Std 1063™-2001

 

IEEE Standard for Software User Documentation

Minimum requirements for the structure, information content, and format of user documentation, including both printed and electronic documents used in the work environment by users of systems containing software, are provided in this standard.

IEEE Std 1228™-1994

 

IEEE Standard for Software Safety Plans

The minimum acceptable requirements for the content of a software safety plan are established. This standard applies to the software safety plan used for the development, procurement, maintenance, and retirement of safety-critical software. This standard requires that the plan be prepared within the context of the system safety program. Only the safety aspects of the software are included. This standard does not contain special provisions required for software used in distributed systems or in parallel processors.

IEEE Std 1465™-1998

 

IEEE Standard—Adoption of International Standard ISO/IEC 12119: 1994(E)—Information Technology—Software packages—Quality requirements and testing

Quality requirements for software packages and instructions on how to test a software package against these requirements are established. The requirements apply to software packages as they are offered and delivered, not to the production process (including activities and intermediate products, such as specifications).

IEEE Std 14143.1™-2000

 

IEEE Adoption of ISO/IEC 14143-1:1998 Information Technology—Software Measurement—Functional Size Measurement—Part 1: Definition of Concepts

This part [volume] of ISO/IEC 14143 defines the fundamental concepts of Functional Size Measurement (FSM) and describes the general principles for applying an FSM Method. This part of ISO/IEC 14143 does NOT provide detailed rules on how to:

  • Measure Functional Size of software using a particular method;

  • Use the results obtained from a particular method;

  • Select a particular method.

This part of ISO/IEC 14143 is applicable when determining if a method for sizing software is an FSM Method. It does not prevent the development of various methods, but rather provides a basis for assessing whether a particular method conforms to FSM. Implementation notes that relate to the IEEE interpretation of ISO/IEC 14143-1:1998 are provided.

About IEEE standard numbers.