AS 4042-1992

1 - AS 4042:1992 SOFTWARE CONFIGURATION MANAGEMENT PLANS
4 - PREFACE
5 - CONTENTS
6 - 1. Introduction to the Standard
6 - 1.1 Scope
6 - 1.2 References
7 - 1.3 Definitions and Acronyms
7 - 2. The Software Configuration Management Plan
7 - 2.1 Introduction
8 - 2.2 SCM Management
8 - 2.2.1 Organization
8 - 2.2.2 SCM Responsibilities
8 - 2.3 Applicable Policies, Directives, and Procedures
8 - 2.3 SCM Activities
9 - 2.3.1 Configuration Identification
9 - 2.3.1.1 Identifying Configuration Items
10 - 2.3.1.2 Naming Configuration Items
10 - 2.3.1.3 Acquiring Configuration Items
10 - 2.3.2 Configuration Control
10 - 2.3.2.1 Requesting Changes
10 - 2.3.2.2 Evaluating Changes
11 - 2.3.2.3 Approving or Disapproving Changes
11 - 2.3.4 Implementing Changes
11 - 2.3.3 Configuration Status Accounting
11 - 2.3.4 Configuration Audits and Reviews
11 - 2.3.5 Interface Control
12 - 2.3.6 Subcontractor/Vendor Control
12 - 2.4 SCM Schedules
12 - 2.5 SCM Resources
12 - 2.6 SCM Plan Maintenance
13 - 3. Tailoring of the Plan
13 - 3.1 Upward Tailoring
13 - 3.2 Downward Tailoring
13 - 3.3 Format
13 - 4. Conformance to the Standard
13 - 4.1 Minimum Information
14 - 4.2 Presentation Format
14 - 4.3 Consistency Criteria
14 - 4.4 Conformance Declaration

Establishes the minimum required contents of a software configuration management (SCM) plan. This Standard is technically identical with, and reproduced from, IEEEStd828: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 [4]1, 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.

First published as AS 4042-1992.