IEEE 833:1988 pdf download.IEEE Stand ard 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 (4P, 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. IL 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 ushalI and required.” Additional optional information is also identified as appropriate. The user of this standard, however, is expected to expand and supplement the minimum requirement,s 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 [21). It is not the purpose of IEEE St.d 828-1990 to supersede, revise, or amend existing standards directed to specific industries or applications.
1.2 References. This standard may be used in conjunction with the following IEEE Software Engineering Standards:
[1] IEEE Std 610.12-1990, IEEE Standard Glossary of Software Engineering Terminology.
[2] IEEE Std 730.1-1989, IEEE Standard for Software Quality Assurance Plans (ANSI).
[3] IEEE Std 1042-1987, IEEE Guide to Software Configuration Management (ANSI).
1.3 Definitions and Acronyms. The definitions below describe specific terms as used within the context of this standard.
control poLnt (project control point). A project agreed on point in time or times when specified agreements or controls are applied to the software configuration items being developed, e.g., an approved baseline or release of a specified documentfcode.
release. The formal notification and distribution of an approved version.
Additional terms that are relevant are defined in IEEE SW 610. 12-1990 [1], and are as follows: baseline, component, configuration, configuration audit, configuration control, configuration control board, configuration identification, configuration item, configuration management, configuration status accounting, interface, interface control, software, software library, software life cycle, unit, version.IEEE 833 pdf download.