4. GENERAL REQUIREMENTS
The contractor shall establish a CM program covering the appropriate life-cycle phases of the applicable Configuration Items (CIs) and Computer Software Configuration Items (CSCIs). In this document, CI is a broad term that includes CSCI whenever appropriate. The requirements of this document shall be implemented and tailored as stated in the contract Statement of Work (SOW) and consist of the following elements:
a. Configuration Identification
b. Configuration Control
c. Configuration Status Accounting
d. Configuration Verification; Configuration Verification/Validation for Software/Firmware
The contractor shall assure that all appropriate subcontractors comply with the requirements of this CM program.
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
| File | MIME type | Size (KB) | Language | Download | |
|---|---|---|---|---|---|
| ED03- Standard for Contractor Configuration Management for MSFC Programs Projects.pdf | application/pdf | 1.08 MB | English | DOWNLOAD! |
Provides definitions
Cover images
Introduction
1. SCOPE/PURPOSE
1.1 Scope/Purpose.
The purpose of this document is to establish requirements for implementing Configuration Management (CM) on MSFC contracts to design, develop, fabricate, integrate, operate, or provide logistical support to hardware, software, and firmware items. This document also establishes requirements for MSFC contracts providing technology or requirements that are precursors of program design.
1.2 Applicability.
This document is applicable to all MSFC contractors performing design, development, fabrication, integration, operations, or logistical products and services for MSFC programs or projects. These standards apply to flight, flight demos, protoflight, and ground support equipment and may be tailored by the individual programs/projects.