Refine Your Search

Search Results

Viewing 1 to 18 of 18
Standard

Automated Data Management Guideline

2014-10-01
CURRENT
DMG2
This document provides guidance in the developing, managing, controlling and transmitting of data in the current electronic environment.
Standard

Configuration Change Control for Digital Computer Programs

2020-06-08
WIP
CMB4_4A

The very nature of configuration management is the control of the configuration. This was the initial premise under which the control discipline was established and, later, formalized in DoD-D-5010.19 (1969) into a statement which defined control as: "The systematic evaluation, coordination, approval or disapproval, and implementation of all approved changes in the configuration of a configuration item after formal establishment of its configuration identification."

What this definition does not impart is the scope and magnitude of the configuration change control task, or the rationale for configuration changes. The purpose of this bulletin is to describe the software change control process in the context of a structured programming environment.

Standard

Configuration Control

2020-06-08
WIP
CMB6_4A

The objective of this course is to provide an in-depth understanding of the concepts and principles involved in the configuration control process. It is intended for an individual who has completed a basic introductory course in CM and who requires the deeper knowledge of a CM practitioner rather than a superficial overview.

The overall objective of configuration management is to guarantee the buyer that a given product is what it was intended to be, functionally and physically as defined by contractual drawings and specifications, and to identify the configuration to the lowest level of assembly required to assure repeatable performance, quality, maintainability and reliability in all units of the same product.

Standard

Configuration Control

2014-10-01
CURRENT
CMB6_4
This Interface Control Plan establishes a program for interface control among the major segments/equipments of a DoD program. This could be an airborne weapon system, Medium Launch Vehicle System, Space Launch Complex System, etc. The program is based on formal agreements between participating organizations, and includes (1) documentation to establish, define and control interface requirements and to detail interface design definition between system segments, (2) interface management under the purview of the Interface Management Boards (IMB) and (3) interface control, through Interface Control Working Groups (ICWGs). The plan establishes the IMB and ICWG policy and procedures. Furthermore, it sets forth the Government Agencies Program Offices, associate contractors and participating Government Agency responsibilities in support of the Interface Control Program and the conduct of interface management/control through the IMBs, and ICWGs.
Standard

Configuration Management Definitions for Digital Computer Programs

2014-10-01
CURRENT
CMB4_1A
This Bulletin is intended for use as a guide and defines the terms and definitions to be used during the development, documentation, verification, and delivery cycles of new and modified computer software. It lists and defines the most common terms currently used in the world of computer software configuration management. There has been no attempt to compete with some of the more formal documents in use within the software programming community.
Standard

Configuration Management Requirements for Subcontractors/Vendors

2014-10-01
CURRENT
CMB5A
The role of CM, within any one company's organization, on the development and production of a product has been established by internal company needs or imposed by customer dictum. (As used hereinafter, in order to reduce any confusion, computer programs, components, software, hardware, firmware, etc., are included in the designation "PRODUCT".) The primary focus of this Bulletin is directed toward the Buyer and Supplier personnel who will be managing hardware products in the production phase and software products in the full-scale development phase. The trend in DoD is toward expanded use of standardized components and subassemblies, using competitive reprocurement. The DoD needs to know the full span of CM requirements which should be included in the production contract and the management tasks that will have to be accomplished.
Standard

Configuration Management Standard

2019-02-07
CURRENT
EIA649C
This standard defines five CM functions and their underlying principles. The functions are detailed in Section 5. The principles, highlighted in text boxes, are designed to individually identify the essence of the related CM function and can be used to collectively create a checklist of “best practice” criteria to evaluate a CM program. The CM principles defined in this standard apply equally to internally focused enterprise information, processes, and supporting systems (i.e., Enterprise CM - policy driven, supporting the internal goals needed to achieve an efficient, effective and lean enterprise), as well as to the working relationships supported by the enterprise (i.e., Acquirer/Supplier CM - contracted relationship to support external trusted interaction with suppliers).
Standard

Configuration and Data Management References

2020-06-09
WIP
CMB6_1D
The purpose of this Bulletin is to provide a listing of available government and industry references for CM and DM. This listing is a guide in selecting appropriate reading material and text for college curricula, as well as material for anyone interested in researching these subjects.
Standard

Configuration and Data Management Training Course

2020-06-08
WIP
CMB6_9A

The functional and/or physical characteristics or hardware/software as set forth in technical documentation and achieved in a product.

What is Configuration Management?

A discipline applying technical and administrative direction and surveillance to (a) identify and document the functional and physical characteristics of a configuration item, (b) control changes to those characteristics, and (c) record and report change processing and implementation status.

Standard

Glossary of Terms, Acronyms, and Definitions

2014-10-01
CURRENT
CMB7_4A
This Bulletin provides a comprehensive list of Terms and Definitions used in or related to TechAmerica prepared standards/documents. The information in these listings was extracted from standards and documents prepared by the Systems Engineering (G47), Configuration Management (G33), Life Cycle Logistics Supportability and Enterprise Information Management Interoperability Committees along with other pertinent international, industry and government standards. It is intended that this bulletin be used as a resource to help with harmonization of terms and definitions across standards. One should be cognizant of the release date of this Bulletin and understand that updates to the included standards and handbooks after this Bulletin was released may affect its accuracy.
Standard

Implementation Guide for Configuration Management

2005-10-01
HISTORICAL
GEIAHB649
This handbook provides guidance about the use of CM and about CM's interface with other management systems and procedures. The paragraph numbers in this handbook map directly to the paragraph numbers in ANSI/EIA-649. It is applicable to the support of projects throughout all phases of a product's life cycle. Generic CM examples are included which may be tailored, taking into account the complexity and nature of the work and the product. It is applicable to the support of projects throughout all phases of a products life cycle. Generic CM examples are included and may be tailored to suit the complexity and nature of the work and the product. This handbook establishes a common framework for generic product life cycle CM. It addresses tailored implementation based on differences that may exist in organization policies and procedures, in the phase of the product life cycle, in the acquisition method, in the project size and complexity, and in the system requirements and development.
Standard

Reviews and Configuration Audits

2020-06-08
WIP
CMB6_6A

The objective of this course is to provide an in-depth understanding of the concepts and principles involved in the Review and Configuration Audit process. It is intended for an individual who has completed a basic introductory course in CM and who requires the deeper knowledge of a CM practitioner rather than a superficial overview.

Technical review and product audit practices described in this text are based on Government requirements. This emphasis is made because the Department of Defense DOD) represents a major customer of goods and services and because the referenced specifications and standards reflect good business practices refined over many years of usage. For commercial companies producing items for other companies or the public, many of these reviews and audits may not be formally implemented. They are, however, an integral and essential part of the systems engineering process.

X