Superseded
Standard
Historical
IEEE 828:2005
IEEE Standard for Software Configuration Management Plans
Summary
Revision Standard - Superseded.
The minimum required contents of a Software Configuration Management (SCM) Plan
are established via this standard. This standard applies to the entire life cycle of critical software (e.g., where failure would impact safety or cause large financial or social losses). It also applies to noncritical software and to software already developed. The application of this standard is not restricted to any form, class, or type of software.
This standard establishes the minimum required contents of a Software Configuration Management (SCM) Plan (also referred to as "the Plan"). This standard applies to the entire life cycle of critical software; e.g., where failure would impact safety or cause large financial or social losses. It also applies to noncritical software and to software already developed. The application of this standard is not restricted to any form, class, or type of software.
The SCM Plan documents what SCM activities are to be done, how they are to be done, who is responsible for doing specific activities, when they are to happen, and what resources are required. It can address SCM activities over any portion of a software product's life cycle. This standard is consistent with the IEEE Software Engineering Body of Knowledge (SWEBOK) project Stoneman release on the topic of configuration management and with IEEE/EIA Std 12207.0(TM).
The minimum required contents of a Software Configuration Management (SCM) Plan
are established via this standard. This standard applies to the entire life cycle of critical software (e.g., where failure would impact safety or cause large financial or social losses). It also applies to noncritical software and to software already developed. The application of this standard is not restricted to any form, class, or type of software.
This standard establishes the minimum required contents of a Software Configuration Management (SCM) Plan (also referred to as "the Plan"). This standard applies to the entire life cycle of critical software; e.g., where failure would impact safety or cause large financial or social losses. It also applies to noncritical software and to software already developed. The application of this standard is not restricted to any form, class, or type of software.
The SCM Plan documents what SCM activities are to be done, how they are to be done, who is responsible for doing specific activities, when they are to happen, and what resources are required. It can address SCM activities over any portion of a software product's life cycle. This standard is consistent with the IEEE Software Engineering Body of Knowledge (SWEBOK) project Stoneman release on the topic of configuration management and with IEEE/EIA Std 12207.0(TM).
Notes
Superseded
Technical characteristics
| Publisher | Institute of Electrical and Electronics Engineers (IEEE) |
| Publication Date | 08/12/2005 |
| Edition | |
| Page Count | 30 |
| EAN | --- |
| ISBN | --- |
| Weight (in grams) | --- |
| Brochures |
|
Amendments replaces
27/10/1998
Superseded
Historical
Previous versions
16/03/2012
Withdrawn
Most Recent
12/08/2005
Superseded
Historical
27/10/1998
Superseded
Historical
06/11/1990
Superseded
Historical
24/06/1983
Superseded
Historical