The contractor shall perform the following CSCI testing activities.
5.7.1 Software development management. The contractor shall support the Functional Configuration Audit(s) (FCA) and Physical Configuration Audit(s) (PCA). The FCA and PCA for a CSCI may be delayed until after system integration and testing.
5.7.2 Software engineering.
188.8.131.52 The contractor shall make necessary revisions to the Software Design Document(s) (SDDs) and code, conduct all necessary retesting, and update the software development files (SDFs) of all CSUs, CSCs, and CSCIs that undergo design or coding changes based on the results of formal qualification testing.
184.108.40.206 The contractor shall make necessary revisions to the Interface Design Document (IDD) based on the results of formal qualification testing and shall prepare the IDD for delivery.
220.127.116.11 Following successful completion of formal qualification testing and prior to Functional Configuration Audit (FCA) and Physical Configuration Audit (PCA), the contractor shall produce the updated source code for each CSCI. The contractor shall prepare the source code for each CSCI for delivery as specified in the Software Requirements Specification (SRS).
18.104.22.168 For each CSCI, the contractor shall prepare a Software Product Specification (SPS) for delivery.
5.7.3 Formal qualification testing.
22.214.171.124 The contractor shall perform the formal qualification testing (FQT) activities in accordance with the procedures documented in the Software Test Description (STD) for each CSCI.
126.96.36.199 The contractor shall record the results of formal qualification testing in the Software Test Report (STR) for each CSCI.
188.8.131.52 Upon completion of FQT, the contractor shall prepare an up-to-date Software Test Description (STD) for delivery to the contracting agency.
5.7.4 Software product evaluations. The contractor shall perform evaluations of the products identified below, using the evaluation criteria specified in the associated graph.
a. The Software Test Report (STR) for each CSCI
b. The updated source code and design documentation.
5.7.5 Configuration management.
184.108.40.206 The contractor shall identify the exact version of each CSCI to be delivered. The contractor shall document this information in a Version Description Document (VDD) for each CSCI.
220.127.116.11 Following successful completion of the Functional Configuration Audit (FCA) and Physical Configuration Audit (PCA) and when authenticated by the contracting agency, the Software Product Specification (SPS) for each CSCI will be incorporated into the Product Baseline. At this point, each CSCI's Developmental Configuration shall cease to exist.