The contractor shall perform software configuration management in compliance with the following requirements.
4.5.1 Configuration identification. The contractor shall document and implement plans for performing configuration identification. Configuration identification shall be conducted in accordance with the identification scheme specified in the contract. Configuration identification performed by the contractor shall accomplish the following:
a. Identify the documentation that establishes the Functional Allocated and Product Baselines and the Developmental Configuration.
b. Identify the documentation and the computer software media containing code, documentation, or both that are placed under configuration control.
c. Identify each CSCI and its corresponding Computer Software Components (CSCs) and Computer Software Units (CSUs).
d. Identify the version, release, change status, and any other identification details of each deliverable item.
e. Identify the version of each CSCI, CSC, and CSU to which the corresponding software documentation applies.
f. Identify the specific version of software contained on a deliverable medium, including all changes incorporated since its previous release.
4.5.2 Configuration control. The contractor shall document and implement plans for performing configuration control. Configuration control performed by the contractor shall accomplish the following:
a. Establish a Developmental Configuration for each CSCI.
b. Maintain current copies of the deliverable documentation and code.
c. Provide the contracting agency access to documentation and code under configuration control.
d. Control the preparation and dissemination of changes to the master copies of deliverable software and documentation that have been placed under configuration control so that they reflect only approved changes.
4.5.3 Configuration status accounting. The contractor shall document and implement plans for performing configuration status accounting. The contractor shall generate management records and status reports on all products comprising the Developmental Configuration and the Allocated and Product Baselines. The status reports shall:
a. Provide traceability of changes to controlled products.
b. Serve as a basis for communicating the status of configuration identification and associated software.
c. Serve as a vehicle for ensuring that delivered documents describe and represent the associated software.
4.5.4 Storage, handling, and delivery of project media. The contractor shall document and implement methods and procedures for the storage, handling, and delivery of software and documentation. The contractor shall maintain master copies of the delivered software and documentation.
4.5.5 Engineering Change Proposals. The contractor shall prepare Engineering Change Proposals (ECPs) in accordance with DOD-STD-480 or MIL-STD-481 as specified in the contract. The contractor shall prepare Specification Change Notices (SCNs) in accordance with MIL-STD-490.