Standards, Policies, and Procedures for configuration management, especially software configuration management
Brad Appleton's Software Configuration Management Links - This site provides a collection of CM resources in the following categories:
projects, groups, and conferences; resources; guides and tutorials; research papers and experience reports; software tool vendors; and tools.
CM Resource Guide - CM and Related Organizations - A web site that lists organizations involved in configuration management and other resources for configuration management, including standards and tools.
CMII Standard for CM and IPE - CMII Standard for Configuration Management — Basis for CMII Training and Five Levels of Certification
This document contains everything you could want to know about CMII without taking the actual courses.
"This Department of Energy (DOE) Technical Standard is available for use by DOE contractors and subcontractors and DOE operators responsible for DOE nuclear activities. It was written to apply to DOE hazard category 1, 2, and 3 nuclear facilities, but elements of this standard can be successfully applied to other types of facilities, activities, and operations, both nuclear and non-nuclear."
This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. Software includes the software portion of firmware. This revision integrates ISO/IEC 12207:1995 with its two amendments and was coordinated with the parallel revision of ISO/IEC 15288:2002 (System life cycle processes) to align structure, terms, and corresponding organizational and project processes. This standard may be used stand alone or jointly with ISO/IEC 15288, and supplies a process reference model that supports process capability assessment in accordance with ISO/IEC 15504-2 (Process assessment). An annex provides support for IEEE users and describes relationships of this International Standard to IEEE standards
Abstract: The minimum required contents of a Software Configuration Management (SCM) Plan are established via this standard. This standard applies to the entire life cycle of critical software
(e.g., where failure would 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.
"This Standard is published by the National Aeronautics and Space Administration (NASA) to provide uniform engineering and technical requirements for processes, procedures, practices, and
methods that have been endorsed as standard for NASA programs and projects, including requirements for selection, application, and design criteria of an item.
This Standard is approved for use by NASA Headquarters and NASA Centers, including Component Facilities.
This Standard establishes a common framework for consistent and acceptable Configuration Management (CM) practices across NASA."
Oklahoma State -- Configuration Management Resources - This site contains a series of PowerPoint presentations on CM available in both PC and Mac formats. Included are sample plans and procedures and information on software tools. (Note this link is to an archive of the site. The original site is no longer available.)
Software Configuration Management - Measurements - This report defines the basic priciples of SCM and identifies their value in improving software quality. SCM adoption issues are discussed, and guidance is provided for the development of a long-term SCM solution. This report emphasizes the need for organizations to plan for the SCM implementation, to develop a detailed SCM plan, and to define the SCM process before implementing an automated SCM system. Information about SCM products in the market place is also included. Finally, future directions of the SCM domain are identified. {MS-WORD Zip format} (Note this link is to an archive of the site. The original site is no longer available.)
Software Configuration Management Technology Report - This report defines the basic priciples of SCM and identifies their value in improving software quality. SCM adoption issues are discussed, and guidance is provided for the development of a long-term SCM solution. This report emphasizes the need for organizations to plan for the SCM implementation, to develop a detailed SCM plan, and to define the SCM process before implementing an automated SCM system. Information about SCM products in the market place is also included. Finally, future directions of the SCM domain are identified. {MS-WORD Zip format} (Note this link is to an archive of the site. The original site is no longer available.)