IEEE 983-1986

IEEE 983-1986 is the IEEE Guide for Software Quality Assurance Planning, a computing standard that helps define how quality assurance should be organized and documented for software work. It addresses planning activities, responsibilities, and control points that support consistent development and verification. In practice, this guide matters because software projects often need a clear, repeatable approach to quality assurance, especially when requirements, reviews, and testing must be aligned across a team or organization.

IEEE 983-1986 overview

This standard focuses on the planning side of software quality assurance rather than on code techniques themselves. IEEE 983-1986 is intended to help organizations structure a software quality assurance plan so that the expected activities, methods, and review obligations are stated clearly. Within the broader computing and processing field, it provides a technical reference for managing quality-related tasks in a disciplined way. Its guidance is especially useful when a project needs documented assurance practices that can be traced and reviewed.

Typical use cases

IEEE 983-1986 is typically relevant during software project setup, when teams are defining the quality assurance plan for development, integration, and acceptance work. It may be used for systems where formal reviews, verification steps, and controlled documentation are important, such as business software, control applications, or other engineered software environments. The guide can also support procurement or contract-driven projects where buyers expect a clear quality assurance framework before implementation begins.

Why this standard matters

This guide matters because software quality problems are often introduced when responsibilities, checks, and review criteria are left vague. IEEE 983-1986 helps reduce that risk by encouraging a planned approach to quality assurance that can support consistency, auditability, and better coordination between development and verification functions. For organizations that need a defensible planning basis, the standard can improve control over software quality activities and make expectations clearer throughout the project lifecycle.

• Software quality assurance planning
• Review and verification structure
• Roles and responsibilities
• Documentation and control points