UNLIMITED FREE ACCESS TO THE WORLD'S BEST IDEAS

close
Already an Engineering360 user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your Engineering360 Experience

close
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

IEEE 828

Standard for Software Configuration Management Plans

inactive
Buy Now
Organization: IEEE
Publication Date: 14 February 2005
Status: inactive
Page Count: 27
scope:

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.

Purpose

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™ [B4]1,2.

The content of the Plan is identified in Clause 3 of this standard. The required information is indicated by the words "shall" and "required." Additional optional information is also identified as appropriate. The user of this standard, however, is expected to expand and supplement the minimum requirements as necessary for the development environment, specific industry, organization, and project. Adapting a plan in conformance with this standard is described in Clause 4.

The primary users of this standard are assumed to be those planning SCM activities or performing SCM audits.

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 standards documents relating to quality assurance, definitions, or other matters (see IEEE Std 730™-2002 [B3]). It is not the purpose of this standard to supersede, revise, or amend existing standards directed to specific industries or applications.

1IEEE publications are available from the Institute of Electrical and Electronics Engineers, 445 Hoes Lane, P.O. Box 1331, Piscataway, NJ 08855-1331, USA

2 The numbers in brackets correspond to those of the bibliography in Annex A.

Document History

February 6, 2012
Configuration Management in Systems and Software Engineering
This standard establishes the minimum requirements for Configuration Management (CM) in Systems and Software Engineering, without restriction to any form, class, or type. Purpose This standard...
IEEE 828
February 14, 2005
Standard for Software Configuration Management Plans
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...
June 25, 1998
Standard for Software Configuration Management Plans
This standard establishes the minimum required contents of a Software Configuration Management (SCM) Plan (the Plan). It is supplemented by IEEE Std 1042-1987, 1 which provides approaches to good...
January 1, 1990
Standard for Software Configuration Management Plans
IEEE Std 828-1990 establishes the minimum required contents of a Software Configuration Management (SCM) Plan (the Plan). It is supplemented by IEEE Std 1042- 1987 [4]1, which provides approaches to...
June 23, 1983
STANDARD FOR SOFTWARE CONFIGURATION MANAGEMENT PLANS; (IEEE COMPUTER SOCIETY DOCUMENT)
This standard provides minimum requirements for preparation and content of Software Configuration Management (SCM) Plans. SCM Plans document the methods to be used for identifying software product...

References

Advertisement