Requirements for initiating, planning, controlling, and executing the Software Quality Assurance processes of a software development or maintenance project are established in this standard. This standard is harmonized with the software life cycle process of ISO/IEC/IEEE 12207:2008 and the information content requirements of ISO/IEC/IEEE 15289:2011.
- Sponsor Committee
- C/S2ESC - Software & Systems Engineering Standards Committee
Learn More - Status
- Active Standard
- PAR Approval
- 2011-09-10
- Superseding
- 730-2002
- Board Approval
- 2014-03-27
- History
-
- Published:
- 2014-06-13
Working Group Details
- Society
- IEEE Computer Society
Learn More - Sponsor Committee
- C/S2ESC - Software & Systems Engineering Standards Committee
Learn More - Working Group
-
730_WG - Std for Software Quality Assurance Plans Working Group
Learn More - IEEE Program Manager
- Patricia Roder
Contact - Working Group Chair
- Lynn Carter
P730
Standard for Software Quality Assurance Processes
This standard establishes requirements for initiating, planning, controlling, and executing the software quality assurance processes of a software endeavor. This standard is consistent with and elaborates on the software life cycle processes specified in ISO/IEC/IEEE 12207-2017 and the information content requirements of ISO/IEC/IEEE 15289:2019.
No Active Standards
730-1984
IEEE Standard Software Quality Assurance Plans
The purpose of this standard is to provide uniform, minimum acceptable requirements for preparation and content of Software Quality Assurance Plans (SQAP). In considering adoption of this standard, regulatory bodies should be aware that specific application of this standard may already be covered by one or more IEEE or ANSI standards documents relating to quality assurance, definitions, or other matters. It is not the purpose of IEEE Std 730 to supersede, revise or amend existing standards directed to specific industries or applications. This standard applies to the development and maintenance of critical software; for example, where failure could impact safety or cause large financial or social losses. For non-critical software, or for software already developed, a subset of the requirements of this standard may be applied. The existence of this standard should not be construed to prohibit additional content in a Software Quality Assurance Plan. An assessment should be made for the specific software product item to assure adequacy of coverage. Where this standard is invoked for a project engaged in producing several software items, the applicability of the standard should be specified for each of the software product items encompassed by the project.
730-1989
IEEE Standard for Software Quality Assurance Plans
Superseded Uniform minimum acceptable requirements for the preparation and content of Software Quality Assurance Plans (SQAPs) are provided. The standard also provides a standard against which such plans can be compared and assessed. It applies to the development and maintenance of critical software. For noncritical software, or for software already developed, a subset of the requirements of this standard may be applied.
730-1998
Standard for Software Quality Assurance Plans
Uniform, minimum acceptable requirements for preparation and content of Software QualityAssurance Plans (SQAPs) are provided. This standard applies to the development and maintenance of critical software. For non-critical software, or for software already developed, a subset of the requirements of this standard may be applied.
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.
No Inactive-Withdrawn Standards
No Inactive-Reserved Standards