IEEE 828-1990

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, which provides approaches to good software configuration management planning. This standard applies to the entire life cycle of critical software; for example, where failure could 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 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. The content of the Plan is identified in Section 2 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. Tailoring of a plan in conformance with this standard is described in Section 3 . 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 [2] ). It is not the purpose of IEEE Std 828-1990 to supersede, revise, or amend existing standards directed to specific industries or applications.



Revision Standard - Superseded. IEEE Std 828-1990, IEEE Standard for Software Configuration Management Plans, establishes the minimum required contents of a Software Configuration Management Plan and defines the specific activities to be addressed and their requirements for any portion of a software product’s life cycle.