CLAUSE CODE: QC82    This clause was archived as of 01/22/2009
  CLAUSE TITLE: SOFTWARE CONFIGURATION MANAGEMENT SYSTEM (LESS THAN ISO 10007)


QC82-S SOFTWARE CONFIGURATION MANAGEMENT SYSTEM (LESS THAN ISO 10007):

 

Contractor shall be responsible for uniquely identifying, maintaining, and controlling copies of each version of every software unit, component, assembly, every computer file, and every software document produced by this contract. This includes deliverable, supporting, test, and simulation software, computer files containing more than one piece of software, and documents involving plans, procedures, requirements, interfaces, design documents, test plans, test cases run and test case results, Software Qualification Procedures, copies of Software Qualification Test (SQT) results provided by Quality Assurance, and SQT test reports.

Contractor shall be responsible for controlling and tracking nonconformance reports against software, processes, and software documents. This includes tracking the status of all nonconformances from discovery until verification that corrections have been properly made. Contractor shall be responsible for verifying that only authorized changes are made to the software, processes, and software documents.

With each shipment of software, Contractor shall submit “configuration documents,” which define the requirements, design, build/production, and verification for that contractual item. These documents shall be signed and dated by an official of the Contractor’s Quality Assurance department and shall include the aforementioned documentation and the following minimum information*:

·       Contractor’s Contract/Purchase Order number, including any changed orders.

·       Line item number.

·       Copy of all object code, source code, and associated non-COTS files necessary to produce the object code.

·       List of all documents and their revision level associated with this shipment, including procedures, requirements, interfaces, design documents, test plans and procedures, copies of test results provided by Quality Assurance, and test reports.

·       The procedure for converting source code into object code.

·       List of all open problem reports and all problem reports closed since the last shipment. The list shall identify the revision(s) of hardware, software, and documents caused by a change to close the problem report.

·       Copy of all problem reports on the list above with the associated Software Change Control Board activities.

·       JPL approved deviations and waivers (as applicable).

·       List of all object code, source code, and associated files necessary to produce the object code, including each piece of software's unique name, current version, date and time of this version’s creation, and size.

 

* The first eight items are usually combined into a document called the Release Description Document (RDD)"