AS 4043-1992

1 - AS 4043:1992 SOFTWARE CONFIGURATION MANAGEMENT
4 - PREFACE
5 - CONTENTS
7 - 1. Introduction
7 - 1.1 Scope.
7 - Table 1
7 - Characteristics of Appendixes*
8 - 1.2 References.
8 - 1.3 Mnemonics.
8 - 1.4 Terms.
8 - baseline
9 - promotion
9 - release
9 - promotion
9 - version
9 - revision
9 - 2. SCM Disciplines in Software Management
9 - 2.1 The Context of SCM
9 - 2.1.1 SCM is a Service Function
9 - 2.1.2 SCM is a Part of the Engineering Process
10 - 2.1.3 SCM Manages all Software Entities
12 - 2.2 The Process of SCM
12 - 2.2.1 Management Environment of SCM
12 - 2.2.2 Dynamics of SCM
13 - 2.2.3 Role of Source Code in SCM
13 - 2.2.4 Different Levels of Control
13 - 2.3 The Implementation of SCM
13 - 2.3.1 Using Software Libraries
14 - 2.3.2 Controlling Changes to Libraries
15 - 2.3.3 Using Configuration Control Boards
15 - 2.4 The Tools of SCM
15 - 2.4.1 Basic Tool Set
15 - 2.4.2 Advanced Tool Set
16 - 2.4.3 On-Line Tool Set
16 - 2.4.4 Integrated Tool Set
16 - 2.5 The Planning of SCM
17 - 3. Software Configuration Management Plaits
17 - 3.1 Introduction
17 - 3.1.1 Purpose
17 - 3.1.2 Scope
18 - 3.1.3 Definitions
18 - 3.1.4 References
19 - 3.2 Management
19 - 3.2.1 Organization
20 - 3.2.2 SCM Responsibilities
20 - 3.2.3 Interface Control
21 - 3.2.4 SCM Plan Implementation.
22 - 3.2.5 Applicable Policies, Directives, and Procedures
23 - 3.3 SCM Activities
23 - 3.3.1 Configuration Identification
24 - 3.3.1.2 Identify Project Baselines
25 - 3.3.1.3 Delineate Project Titling, Labeling, Numbering
25 - 3.3.2 Configuration Control
26 - 3.3.2.1 Levels of Authority
26 - 3.3.2.2 Processing Changes
28 - 3.3.2.3 The Configuration Control Board
29 - 3.3.2.4 Interface With Other CCB
29 - 3.3.2.5 Support Software
30 - 3.3.3 Configuration Status Accounting
31 - 3.3.4 Audits and Reviews
32 - 3.3.5 Release Process
32 - 3.3.5.1 Version Description Document
33 - 3.4 Tools, Techniques and Methodologies
34 - 3.5 Supplier Control
34 - 3.5.1 Subcontractor Software
35 - 3.5.2 Vendor Software
36 - 3.6 Records Collection and Retention
37 - Appendixes
37 - Appendix A - Software Configuration Management Plan for Critical Software for Embedded Systems
38 - Synopsis
39 - CONTENTS
41 - 1. Introduction
41 - 1.1 Purpose
41 - 1.2 Scope
41 - 1.3 Definitions and Mnemonics
41 - 1.3.1 Definitions
41 - 1.3.2 Mnemonics
42 - 1.4 References
42 - 2. Management
42 - 2.1 Organization
43 - 2.2 SCM Responsibilities
43 - 2.2.1 Configuration Identification
43 - 2.2.2 Configuration Control
43 - 2.2.2.1 Systems/Software Change Request (SCR)
43 - 2.2.2.2 Software Change Authorization (SCA)
43 - 2.2.3 Status Accounting
43 - 2.2.4 Audits
43 - 2.2.4.1 SQA Audits
43 - 2.2.5 Configuration Control Board (CCB)
43 - 2.2.1 Configuration Identification
43 - 2.2.1.1 Baselines
43 - 2.2.1.2 Releases
43 - 2.2.1.3 Documentation
44 - 2.3 Interface Control
44 - 2.4 SCMP Implementation
44 - 2.4.1 Configuration Control Board
44 - 2.4.2 Configuration Baselines
44 - 2.4.2.1 Functional Baseline
44 - 2.4.2.2 Allocated Baseline
44 - 2.4.2.3 Developmental Baseline
44 - 2.4.2.4 Product Baseline
44 - 2.4.3 Schedules and Procedures for SCM Reviews and Audits
44 - 2.4.4 Configuration Management of Software Development Tools
44 - 2.5 Applicable Policies, Directives, and Procedures
44 - 3. SCM Activities
44 - 3.1 Configuration Identification
44 - 3.1.1 Documentation
45 - 3.1.2 Software Parts
45 - 3.1.3 Configuration Identification of the Functional Baseline
45 - 3.1.4 Configuration Identification of the Allocated Baseline
45 - 3.1.5 Configuration Identification of the Developmental Baselines
45 - 3.1.6 Configuration Identification of the Product Baseline
45 - 3.2 Configuration Control
45 - 3.2.1 Function of the Configuration Control Board
45 - 3.2.2 The System/Software Change Request
45 - 3.2.3 Software Change Authorization
46 - 3.2.4 Change Control Automated SCM Tools
46 - 3.3 Configuration Status Accounting
46 - 3.4 Audits and Reviews
46 - 3.4.1 Functional Configuration Audit
46 - 3.4.2 Physical Configuration Audit
46 - 3.4.3 Reviews
47 - 4. Tools, Techniques, and Methodologies
47 - 4.1 Configuration Control Tools
47 - 5. Supplier Control
47 - 5.1 Vendor-Provided Software
47 - 5.2 Subcontracted Software
47 - 5.3 Vendor and Subcontractor Software
47 - 6. Records Collection and Retention
53 - Appendix B - Software Configuration Management Plan for Experimental Development Small System
54 - Synopsis
55 - CONTENTS
56 - 1. Introduction
56 - 1.1 Purpose of the Plan
56 - 1.2 Scope
56 - 1.3 Definitions and Mnemonics
56 - 1.3.1 Standard Definitions
56 - 1.3.2 Other Definitions
56 - 1.3.3 Mnemonics
57 - 1.4 References
57 - 2. Management
57 - 2.1 Organizations
57 - 2.2 SCM Responsibilities
57 - 2.2.1 Identification
58 - 2.2.2 Control
58 - 2.2.3 Status Accounting
58 - 2.2.4 Audits and Reviews
58 - 2.3 Interface Control
58 - 2.4 SCMP Implementation
58 - 2.5 Applicable Policies, Directives, and Procedures
59 - 3. SCM Activities
59 - 3.1 Configuration Identification
59 - 3.1.1 EDSS Project Baselines
59 - 3.1.2 EDSS Project Labeling
59 - 3.2 Configuration Control
59 - 3.2.1 Configuration Control Board
59 - 3.2.2 Processing SCR
59 - 3.2.3 CCB Interfaces
59 - 3.3 Configuration Status Accounting
59 - 3.4 Audits and Reviews
60 - 4. Tools, Techniques, and Methodologies
60 - 5. Supplier Control
60 - 6. Records Collection and Retention
64 - Appendix C - Software Configuration Management Plan for a Software Maintenance Organization
65 - Synopsis
66 - CONTENTS
67 - 1. Introduction
67 - 1.1 Purpose of the Plan
67 - 1.2 Scope
67 - 1.3 Definitions and Mnemonics
67 - 1.3.1 Definitions
67 - 1.3.2 Mnemonics
67 - 1.4 References
68 - 2. Management
68 - 2.1 Organization
68 - 2.1.1 Operations Group
68 - 2.1.2 Systems Software Programmers
68 - 2.1.3 Test and Evaluation Group
68 - 2.1.4 User Consultants
68 - 2.1.5 SPLIT Software Quality Assurance Group
68 - 2.1.6 Multiple Configuration Control Boards
69 - 2.2 SCM Responsibilities.
69 - 2.2.1 Identification
69 - 2.2.2 Configuration Control
69 - 2.2.3 Configuration Status Accounting
69 - 2.2.4 Audits and Reviews
69 - 2.3 Interface Control
70 - 2.4 SCMP Implementation
70 - 2.5 Applicable Policies, Directives, and Procedures
70 - 2.5.1 Policies
70 - 2.5.2 Directives
70 - 2.5.3 Procedures
70 - 3. SCM Activities
70 - 3.1 Configuration Identification
71 - 3.1.1 Baseline Identification
71 - 3.1.2 Product Baseline Cataloging
71 - 3.2 Inspection and Receiving
71 - 3.3 Configuration Control
71 - 3.3.1 Levels of Authority for Approvals
71 - 3.3.2 Change Proposal Processing
71 - 3.3.2.1 SCR Processing
72 - 3.3.2.2 SCA Processing
72 - 3.3.2.3 Changes to EWS
72 - 3.3.2.4 Changes to Supplier Software
72 - 3.3.2.5 Licensed Software
72 - 3.3.2.6 Purchased Commercial Software
72 - 3.3.3 CCB Roles
72 - 3.3.4 Control of Interfaces
73 - 3.4 Configuration Status Accounting
73 - 3.5 Audits and Reviews
73 - 4. Tools, Techniques, and Methodologies
73 - 4.1 Use of the CCM System
73 - 4.2 Inspections
73 - 4.3 Library Management
73 - 4.3.1 Development Library
73 - 4.3.2 Integration Library
73 - 4.3.3 Production Library
73 - 4.3.4 Software Repository
74 - 5. Supplier Control
74 - 6. Records Collection and Retention
77 - Appendix D - Software Configuration Management Plan for a Product Line System
78 - Synopsis
79 - CONTENTS
80 - 1. Introduction
80 - 1.1 Purpose
80 - 1.2 Scope
80 - 1.3 Definitions and Mnemonics
80 - 1.3.1 Definitions
81 - 1.3.2 Mnemonics
81 - 1.4 References
81 - 2. Management
81 - 2.1 Organization
83 - 2.2 SCM Responsibilities
83 - 2.3 Interface Control
84 - 2.4 SCMP Implementation
84 - 2.4.1 PLAS Configurati on Baselines
84 - 2.4.2 The Configuration Control Board
84 - 2.4.3 The Support Environment
84 - 2.4.4 SCM Resource Requirements
85 - 2.5 Applicable Policies, Directives, and Procedures
85 - 2.5.1 Existing Policies and Procedures
85 - 2.5.2 New Policies and Procedures To Be Written
85 - 3. SCM Activities
85 - 3.1 Configuration Identification
85 - 3.1.1 Naming Conventions
85 - 3.1.2 Implementation
86 - 3.1.3 Ownership Notification Procedures
86 - 3.2 Configuration Control
86 - 3.2.1 Change Processing
86 - 3.2.2 Production Baseline Changes
87 - 3.2.3 PLAS Module Release
87 - 3.3 Configuration Status Accounting
88 - 3.4 Audits and Reviews
88 - 3.4.1 Audits
88 - 4. Tools, Techniques, and Methodologies
89 - 5. Supplier Control
89 - 6. Records Collection and Retention
89 - 6.1 Backup Data Base
89 - 6.2 Archive Data Base
90 - Appendix E - References Bibliography

Describes the application of configuration management (CM) disciplines to management of software engineering projects. This Standard is technically identical with and reproduced from IEEEStd1042:1987.

This guide describes the application of configuration management (CM) disciplines to the management of software engineering projects. Software configuration management (SCM) consists of two major aspects: planning and implementation. For those planning SCM activities, this guide provides insight into the various factors that must be considered.Users implementing SCM disciplines will find suggestions and detailed examples of plans in this guide. This guide also presents an interpretation of how ANSI/IEEE Std 828-1983 [2]1can be used for planning the management of different kinds of computer program development and maintenance activities.The guide is presented in two parts. The first part, the main body of the guide, presents issues to consider when planning software configuration management for a project or organization. The second part of the guide presents, for those preparing SCM Plans, a series of sample Plans illustrating different concepts discussed in the body of the guide.The text of the guide introduces the essential concepts of SCM, particularly those of special significance (for example, libraries and tools) to software engineering. It then presents the planning for SCM in terms of documenting a Plan following the outline of ANSI/IEEE Std 828-1983 [2] so that a user who is unfamiliar with the disciplines of software configuration management can gain some insight into the issues. For those preparing SCM Plans, the second part of the guide provides sample plans for consideration.The sample SCM Plans include a variety of software configuration management applications for different types of projects and organizations. Appendix A illustrates a software configuration management plan (SCMP) for a project developing a complex, critical computer system. It describes a Plan for managing a typical software development cycle where the development is contracted to an organization that does not have responsibility for its maintenance or use. Appendix B illustrates a SCMP for a small software development project. It describes a Plan for supporting a prototype development activity where the goal of the project is to demonstrate the feasibility of a concept. Appendix C illustrates a SCMP used by an organization where the emphasis is on maintaining programs developed by other activities or organizations. Appendix D illustrates a SCMP for an organization developing and maintaining computer programs embedded in a hardware product line. It describes a Plan for managing both software development and maintenance of a commercial product line. Some of the different characteristics illustrated are shown in Table 1.

First published as AS 4043-1992.