IEEE 828-2005 pdf download IEEE Standard for Software Configuration Management Plans
1. Overview
1.1 Scope
This standard establishes the minimum required contents of a Software Configuration ManagementSCM) Plan (also referred to as “the Plan). This standard applies to the entire life cycle of criticalsoftware; e.g, where falure would impact safety or cause large financial or social losses. It alsoapplies to noncritical software and to software already developed. The application of this standard isnot restricted to any form, class, or type of software.
1.2 Purpose
The SCM Plan documents what SCM activities are to be done, how they are to be done, who isresponsible for doing specific activities, when they are to happen, and what resources are required. ltcan address SCM activities over any portion of a software product’s life cycle. This standard isconsistent with the IEEE Software Engineering Body of Knowledge (SWEBOK) project Stonemanrelease on the topic of configuration management and with IEEE/EIA Std 12207.0TM (B4)2
The content of the Plan is identified in Clause 3 of this standard. The required information isindicated by the words “shalland “required.”Additional optional information is also identified asappropriate, The user of this standard, however, is expected to expand and supplement the minimumrequirements as necessary for the development environment, specific industry, organization, andproject. 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 performingSCM audits.
In considering adoption of this standard, regulatory bodies should be aware that specific applicationof this standard may already be covered by one or more lEEE standards documents relating toquality assurance, definitions, or other matters (see IEEE Std 730TM-2002 (B3]). It is not the purposeof this standard to supersede, revise, or amend existing standards directed to specific industries orapplications.
2. Definitions and acronyms
21 Definitions
For the purposes of this standard, the following terms and definitions apply. The AuthoritativeDictionary oflEEE Standards,(Bl], should be referenced for terms not defined in this clause.
2.1.1 control point (project control point): a project agreed on point in time or times whenspecified agreements or controls are applied to the software configuration items being developed.(eg, an approved baseline or release of a specified document/code or project milestone).
2.1.2 release: (A) a particular version of a configuration item that is made available for a specificpurpose (e.g., test release). (B) The formal notification and distribution of an approved version.The following additional terms are used in a manner consistent with their definition or usage inEEE/EIA 12207.0: baseline, component, configuration, configuration audit, configuration contro.configuration control board, configuration identification, configuration item, configurationmanagement, configuration status accounting, interface, interface control, software, software library,software life cycle. unit and version.
The term “the Planis used throughout this standard to refer to the Software ConfigurationManagement Plan.
2.2 Acronyms
The following acronyms appear within the text of this standard:
CCBCISCMSQA
configuration control boardconfiguration itemsoftware configuration managementsoftware quality assurance
3. The Software Configuration Management Plan
SCM planning information shall be partitioned into the six classes described in Table 1. Thereferenced subclauses of the standard provide the reader with detailed requirements for each class ofinformation
IEEE 828-2005 pdf download
PS:Thank you for your support!
