The developer shall prepare for software use in accordance with the following requirements.
Note: If software is developed in multiple builds, the developer's planning should identify what software, if any, is to be fielded to users in each build and the extent of fielding (for example, full fielding or fielding to selected evaluators only). Preparing for software use in each build should be interpreted to include those activities necessary to carry out the fielding plans for that build.
The developer shall prepare the executable software for each user site, including any batch files, command files, data files, or other software files needed to install and operate the software on its target computer(s). The result shall include all applicable items in the executable software section of the Software Product Specification (SPS) DID (see 6.2).
Note: To order only the executable software (delaying delivery of source files and associated support information to a later build), the acquirer can use the SPS DID, tailoring out all but the executable software section of that DID.
The developer shall identify and record the exact version of software prepared for each user site. The information shall include all applicable items in the Software Version Description (SVD) DID (see 6.2).
The developer shall prepare user manuals in accordance with the following requirements.
Note: Few, if any, systems will need all of the manuals in this section. The intent is for the acquirer, with input from the developer, to determine which manuals are appropriate for a given system and to require the development of only those manuals. All DIDs permit substitution of commercial or other manuals that contain the required information. The manuals in this section are normally developed in parallel with software development, ready for use in CSCI testing.
The developer shall identify and record information needed by hands-on users of the software (persons who will both operate the software and make use of its results). The information shall include all applicable items in the Software User Manual (SUM) DID (see 6.2).
The developer shall identify and record information needed by persons who will submit inputs to, and receive outputs from, the software, relying on others to operate the software in a computer center or other centralized or networked software installation. The information shall include all applicable items in the Software Input/Output Manual (SIOM) DID (see 6.2).
The developer shall identify and record information needed by persons who will operate the software in a computer center or other centralized or networked software installation, so that it can be used by others. The information shall include all applicable items in the Software Center Operator Manual (SCOM) DID (see 6.2).
The developer shall identify and record information needed to operate the computers on which the software will run. The information shall include all applicable items in the Computer Operation Manual (COM) DID (see 6.2).
The developer shall:
a. Install and check out the executable software at the user sites specified in the contract.
b. Provide training to users as specified in the contract.
c. Provide other assistance to user sites as specified in the contract.
Translator: Simon Wright simon@pogner.demon.co.uk
Last updated: 22.iii.99