The developer shall participate in system qualification testing in
accordance with the following requirements.
Note 1: System
qualification testing is performed to demonstrate to the acquirer that system
requirements have been met. It covers the system requirements in the
system/subsystem specifications (SSSs) and in associated interface
requirements specifications (IRSs). This testing contrasts with
developer-internal system testing, performed as the final stage of CSCI/HWCI
integration and testing.
Note 2: If a system is developed in multiple
builds, qualification testing of the completed system will not occur until the
final build. System qualification testing in each build should be interpreted
to mean planning and performing tests of the current build of the system to
ensure that the system requirements to be implemented in that build have been
met.
5.11.1 Independence in system qualification testing. The person(s)
responsible for fulfilling the requirements in this section shall not be the
persons who performed detailed design or implementation of software in the
system. This does not preclude persons who performed detailed design or
implementation of software in the system from contributing to the process, for
example, by contributing test cases that rely on knowledge of the system's
internal implementation.
5.11.2 Testing on the target computer system.
The developer's system qualification testing shall include testing on the
target computer system or an alternative system approved by the
acquirer.
5.11.3 Preparing for system qualification testing. The
developer shall participate in developing and recording the test preparations,
test cases, and test procedures to be used for system qualification testing
and the traceability between the test cases and the system requirements. For
software systems, the results shall include all applicable items in the
Software Test Description (STD) DID (see
6.2
). The developer shall participate
in preparing the test data needed to carry out the test cases and in providing
the acquirer advance notice of the time and location of system qualification
testing.
5.11.4 Dry run of system qualification testing. If system
qualification testing is to be witnessed by the acquirer, the developer shall
participate in dry running the system test cases and procedures to ensure that
they are complete and accurate and that the system is ready for witnessed
testing. The developer shall record the software-related results of this
activity in appropriate software development files (SDFs) and shall
participate in updating the system test cases and procedures as
appropriate.
5.11.5 Performing system qualification testing. The
developer shall participate in system qualification testing. This
participation shall be in accordance with the system test cases and
procedures.
5.11.6 Revision and retesting. The developer shall make
necessary revisions to the software, provide the acquirer advance notice of
retesting, participate in all necessary retesting, and update the software
development files (SDFs) and other software products as needed, based on the
results of system qualification testing.
5.11.7 Analyzing and recording
system qualification test results. The developer shall participate in
analyzing and recording the results of system qualification testing. For
software systems, the result shall include all applicable items in the
Software Test Report (STR) DID (see 6.2 ).
