The developer shall perform project planning and oversight in accordance with the following requirements.
Note: If a system or CSCI is developed in multiple builds, planning for each build should be interpreted to include:
a) overall planning for the contract,
b) detailed planning for the current build, and
c) planning for future builds covered under the contract to a level of detail compatible with the information available.
The developer shall develop and record plans for conducting the activities required by this standard and by other software-related requirements in the contract. This planning shall be consistent with system-level planning and shall include all applicable items in the Software Development Plan (SDP) DID (see 6.2).
Note 1: The wording here and throughout MIL-STD-498 is designed to:
1) Emphasize that the development and recording of planning and engineering information is an intrinsic part of the software development process, to be performed regardless of whether a deliverable is required;
2) Use the DID as a checklist of items to be covered in the planning or engineering activity; and
3) Permit representations other than traditional documents for recording the information (e.g., computer-aided software engineering (CASE) tools).
Note 2: If the CDRL specifies delivery of the information generated by this or any other paragraph, the developer is required to format, assemble, mark, copy, and distribute the deliverable in accordance with the CDRL. This task is recognized to be separate from the task of generating and recording the required information and to require additional time and effort on the part of the developer.
Note 3: The software development plan covers all activities required by this standard. Portions of the plan may be bound or maintained separately if this approach enhances the usability of the information. Examples include separate plans for software quality assurance and software configuration management.
The developer shall develop and record plans for conducting CSCI qualification testing. This planning shall include all applicable items in the Software Test Plan (STP) DID (see 6.2).
The developer shall participate in developing and recording plans for conducting system qualification testing. For software systems, this planning shall include all applicable items in the Software Test Plan (STP) DID (see 6.2). (The intent for software systems is a single software test plan covering both CSCI and system qualification testing.)
The developer shall develop and record plans for performing software installation and training at the user sites specified in the contract. This planning shall include all applicable items in the Software Installation Plan (SIP) DID (see 6.2).
The developer shall identify all software development resources that will be needed by the support agency to fulfill the support concept specified in the contract. The developer shall develop and record plans identifying these resources and describing the approach to be followed for transitioning deliverable items to the support agency. This planning shall include all applicable items in the Software Transition Plan (STrP) DID (see 6.2).
Following acquirer approval of any of the plans in this section, the developer shall conduct the relevant activities in accordance with the plan. The developer's management shall review the software development process at intervals specified in the software development plan to assure that the process complies with the contract and adheres to the plans. With the exception of developer-internal scheduling and related staffing information, updates to plans shall be subject to acquirer approval.
Translator: Simon Wright simon@pogner.demon.co.uk
Last updated: 22.iii.99