IEEE 828-1990

IEEE 828-1990 is the standard for Software Configuration Management Plans, providing a practical framework for controlling software change, identifying configuration items, and documenting the processes used to manage them. In computing and processing environments, it helps project teams define how versions, baselines, approvals, and status accounting should be handled. This matters because a clear plan can reduce ambiguity during development, testing, maintenance, and delivery.

IEEE 828-1990 overview

This standard sets out the content and organization of a Software Configuration Management Plan for software projects and related technical work. IEEE 828-1990 is intended to support disciplined control of software artifacts, so teams can manage changes consistently and trace the status of items over time. It is especially relevant where configuration control, documentation, and release integrity need to be defined in advance rather than left to informal practice.

Typical use cases

IEEE 828-1990 is commonly used when preparing configuration management plans for software systems that require careful version control, change approval, and release tracking. It is relevant to development groups, maintenance teams, and organizations managing multiple software baselines or deliveries. The standard may also support projects where software is tied to larger computing systems, helping align planning for audits, acceptance testing, and controlled updates across the lifecycle.

Why this standard matters

Clear configuration management planning helps reduce errors caused by unmanaged changes, undocumented revisions, or inconsistent release practices. IEEE 828-1990 matters because it supports traceability and repeatable control, which are important when teams must demonstrate compliance, maintain product integrity, or coordinate work across multiple contributors. In practice, it can improve confidence in testing results, simplify reviews, and lower the risk of configuration drift in software-intensive environments.

• Software configuration management planning
• Change control and approval processes
• Version, baseline, and status tracking
• Documentation for controlled software delivery