IEEE HomeSearch IEEE ShopWeb Account Contact IEEE IEEE
MembershipPublicationsServicesStandardsConferencesCareers/Jobs
IEEE-SA IEEE-SA Member Area Search our standards database for Abstract, Sponsor, Status, Contact,Ordering and Historical information. IEEE-SA Standards Association
Products & ServicesIEEE-SA MembershipStandards DevelopmentNews & InformationnavFillerHOMEHOME Icon

ANSI/IEEE 1042-1987 IEEE Guide to Software Configuration Management -Description

Content +

  • 1. Introduction
    • 1.1 Scope.
  • References.
    • 1.3 Mnemonics.
    • 1.4 Terms.
  • 2. SCM Disciplines in Software Management
    • 2.1 The Context of SCM.
      • 2.1.1 SCM is a Service Function.
      • 2.1.2 SCM is a Part of the Engineering Process.
      • 2.1.3 SCM Manages all Software Entities.
    • 2.2 The Process of SCM
      • 2.2.1 Management Environment of SCM.
      • 2.2.2 Dynamics of SCM.
      • 2.2.3 Role of Source Code in SCM.
      • 2.2.4 Different Levels of Control.
    • 2.3 The Implementation of SCM
      • 2.3.1 Using Software Libraries.
      • 2.3.2 Controlling Changes to Libraries.
      • 2.3.3 Using Configuration Control Boards.
    • 2.4 The Tools of SCM.
      • 2.4.1 Basic Tool Set.
      • 2.4.2 Advanced Tool Set.
      • 2.4.3 On-Line Tool Set.
      • 2.4.4 Integrated Tool Set.
    • 2.5 The Planning of SCM.
  • 3. Software Configuration Management Plans
    • 3.1 Introduction.
      • 3.1.1 Purpose.
      • 3.1.2 Scope.
      • 3.1.3 Definitions.
      • 3.1.4 References.
    • 3.2 Management.
      • 3.2.1 Organization.
      • 3.2.2 SCM Responsibilities.
      • 3.2.3 Interface Control.
      • 3.2.4 SCM Plan Implementation.
      • 3.2.5 Applicable Policies, Directives, and Procedures.
    • 3.3 SCM Activities.
      • 3.3.1 Configuration Identification.
      • 3.3.2 Configuration Control.
      • 3.3.3 Configuration Status Accounting.
      • 3.3.4 Audits and Reviews.
      • 3.3.5 Release Process.
    • 3.4 Tools, Techniques and Methodologies.
    • 3.5 Supplier Control.
      • 3.5.1 Subcontractor Software.
      • 3.5.2 Vendor Software.
    • 3.6 Records Collection and Retention.
  • Annex A Appendix A Software Configuration Management Plan for Critical Software for Embedded System
    • A.1 Synopsis
  • 1. Introduction
    • 1.1 Purpose.
    • 1.2 Scope.
    • 1.3 Definitions and Mnemonics
      • 1.3.1 Definitions.
      • 1.3.2 Mnemonics.
  • References.
  • 2. Management
    • 2.1 Organization.
    • 2.2 SCM Responsibilities.
      • 2.2.1 Configuration Identification.
      • 2.2.2 Configuration Control.
      • 2.2.3 Status Accounting.
      • 2.2.4 Audits.
      • 2.2.5 Configuration Control Board (CCB).
    • 2.3 Interface Control.
    • 2.4 SCMP Implementation.
      • 2.4.1 Configuration Control Board.
      • 2.4.2 Configuration Baselines.
      • 2.4.3 Schedules and Procedures for SCM Reviews and Audits.
      • 2.4.4 Configuration Management of Software Development Tools.
    • 2.5 Applicable Policies, Directives, and Procedures.
  • 3. SCM Activities
    • 3.1 Configuration Identification
      • 3.1.1 Documentation.
      • 3.1.2 Software Parts.
      • 3.1.3 Configuration Identification of the Functional Baseline.
      • 3.1.4 Configuration Identification of the Allocated Baseline.
      • 3.1.5 Configuration Identification of the Developmental Baselines.
      • 3.1.6 Configuration Identification of the Product Baseline.
    • 3.2 Configuration Control.
      • 3.2.1 Function of the Configuration Control Board.
      • 3.2.2 The System/Software Change Request.
      • 3.2.3 Software Change Authorization.
      • 3.2.4 Change Control Automated SCM Tools.
    • 3.3 Configuration Status Accounting.
    • 3.4 Audits and Reviews.
      • 3.4.1 Functional Configuration Audit.
      • 3.4.2 Physical Configuration Audit.
      • 3.4.3 Reviews.
  • 4. Tools, Techniques, and Methodologies
    • 4.1 Configuration Control Tools.
  • 5. Supplier Control
    • 5.1 Vendor-Provided Software.
    • 5.2 Subcontracted Software.
    • 5.3 Vendor and Subcontractor Software.
  • 6. Records Collection and Retention
  • Annex B Appendix B Software Configuration Management Plan for Experimental Development Small System
    • A.1 Synopsis
  • 1. Introduction
    • 1.1 Purpose of the Plan.
    • 1.2 Scope.
    • 1.3 Definitions and Mnemonics
      • 1.3.1 Standard Definitions.
      • 1.3.2 Other Definitions
      • 1.3.3 Mnemonics.
  • References
  • 2. Management
    • 2.1 Organizations.
    • 2.2 SCM Responsibilities.
      • 2.2.1 Identification.
      • 2.2.2 Control.
      • 2.2.3 Status Accounting.
      • 2.2.4 Audits and Reviews.
    • 2.3 Interface Control.
    • 2.4 SCMP Implementation.
    • 2.5 Applicable Policies, Directives, and Procedures.
  • 3. SCM Activities
    • 3.1 Configuration Identification
      • 3.1.1 EDSS Project Baselines.
      • 3.1.2 EDSS Project Labeling.
    • 3.2 Configuration Control
      • 3.2.1 Configuration Control Board.
      • 3.2.2 Processing SCR.
      • 3.2.3 CCB Interfaces.
    • 3.3 Configuration Status Accounting.
    • 3.4 Audits and Reviews.
  • 4. Tools, Techniques, and Methodologies
  • 5. Supplier Control
  • 6. Records Collection and Retention
    • 1.1 Processing steps are
    • 1.2 SCM Coordinator.
  • Annex C Appendix C Software Configuration Management Plan for a Software Maintenance Organization
    • A.1 Synopsis
  • 1. Introduction
    • 1.1 Purpose of the Plan.
    • 1.2 Scope.
    • 1.3 Definitions and Mnemonics
      • 1.3.1 Definitions.
      • 1.3.2 Mnemonics.
  • References
  • 2. Management
    • 2.1 Organization.
      • 2.1.1 Operations Group.
      • 2.1.2 Systems Software Programmers.
      • 2.1.3 Test and Evaluation Group.
      • 2.1.4 User Consultants.
      • 2.1.5 SPLIT Software Quality Assurance Group.
      • 2.1.6 Multiple Configuration Control Boards.
    • 2.2 SCM Responsibilities.
      • 2.2.1 Identification.
      • 2.2.2 Configuration Control.
      • 2.2.3 Configuration Status Accounting.
      • 2.2.4 Audits and Reviews.
    • 2.3 Interface Control.
    • 2.4 SCMP Implementation.
    • 2.5 Applicable Policies, Directives, and Procedures
      • 2.5.1 Policies
      • 2.5.2 Directives
      • 2.5.3 Procedures
  • 3. SCM Activities
    • 3.1 Configuration Identification.
      • 3.1.1 Baseline Identification.
      • 3.1.2 Product Baseline Cataloging.
    • 3.2 Inspection and Receiving.
    • 3.3 Configuration Control
      • 3.3.1 Levels of Authority for Approvals.
      • 3.3.2 Change Proposal Processing
      • 3.3.3 CCB Roles.
      • 3.3.4 Control of Interfaces.
    • 3.4 Configuration Status Accounting.
    • 3.5 Audits and Reviews.
  • 4. Tools, Techniques, and Methodologies
    • 4.1 Use of the CCM System.
    • 4.2 Inspections.
    • 4.3 Library Management.
      • 4.3.1 Development Library.
      • 4.3.2 Integration Library.
      • 4.3.3 Production Library.
      • 4.3.4 Software Repository.
  • 5. Supplier Control
  • 6. Records Collection and Retention
    • A.1 Attachment A System/Software Change Request (SPLIT Form C-1049)
    • A.2 Attachment B Software Change Authorization
  • Annex D Appendix D Software Configuration Management Plan for a Product Line System
    • A.1 Synopsis
  • 1. Introduction
    • 1.1 Purpose.
    • 1.2 Scope.
    • 1.3 Definitions and Mnemonics
      • 1.3.1 Definitions.
      • 1.3.2 Mnemonics.
  • References
  • 2. Management
    • 2.1 Organization.
    • 2.2 SCM Responsibilities
    • 2.3 Interface Control.
    • 2.4 SCMP Implementation
      • 2.4.1 PLAS Configuration Baselines.
      • 2.4.2 The Configuration Control Board.
      • 2.4.3 The Support Environment.
      • 2.4.4 SCM Resource Requirements.
    • 2.5 Applicable Policies, Directives, and Procedures
      • 2.5.1 Existing Policies and Procedures.
      • 2.5.2 New Policies and Procedures To Be Written.
  • 3. SCM Activities
    • 3.1 Configuration Identification.
      • 3.1.1 Naming Conventions.
      • 3.1.2 Implementation.
      • 3.1.3 Ownership Notification Procedures.
    • 3.2 Configuration Control.
      • 3.2.1 Change Processing.
      • 3.2.2 Production Baseline Changes.
      • 3.2.3 PLAS Module Release.
    • 3.3 Configuration Status Accounting.
    • 3.4 Audits and Reviews
      • 3.4.1 Audits.
  • 4. Tools, Techniques, and Methodologies
  • 5. Supplier Control
  • 6. Records Collection and Retention
    • 6.1 Backup Data Base.
    • 6.2 Archive Data Base.
  • Annex E Appendix E References Bibliograph
    • A.1 References Bibliography
  • E1 . General Bibliography
  • E2 . Military Standards for SCM
  • E3 Department of Defense Standards
  • E4 . Military Specification
  • E5 . Department of Defense Directives
  • E6 . Department of Defense Instructions
  • E7 . US Government Publications
  • E8 . Electronic Industries Association Publications
  • E9 . American Defense Preparedness Association Publications

links: [Standard Status] - [Purchase] - [PDF*] - [Software Engineering Collection - Description]

available for Standards Online Software Engineering Collection subscribers only
spacer

Copyright ©2004 IEEE-SA
Contact IEEE-SA
(m.v.rodriguez@ieee.org)
URL: http://standards.ieee.org/reading/ieee/std_public/description/se/1042-1987_desc.html

 spacer