(This section contains information of a general or explanatory nature that may be helpful, but is not mandatory.)
This standard contains requirements for the development and documentation of software. Its application is described in 1.2.
The following Data Item Descriptions (DIDs) must be listed, as applicable, on the Contract Data Requirements List (DD Form 1423) when this standard is applied on a contract, in order to obtain the data, except where DOD FAR Supplement 227.405-70 exempts the requirement for a DD Form 1423.
| Reference Para | DID Number | DID Title |
|---|---|---|
| 5.1.1 | DI-IPSC-81427 | Software Development Plan (SDP) |
| 5.1.2, 5.1.3 | DI-IPSC-81438 | Software Test Plan (STP) |
| 5.1.4 | DI-IPSC-81428 | Software Installation Plan (SIP) |
| 5.1.5 | DI-IPSC-81429 | Software Transition Plan (STrP) |
| 5.3.2 | DI-IPSC-81430 | Operational Concept Description (OCD) |
| 5.3.3 | DI-IPSC-81431 | System/Subsystem Specification (SSS) |
| 5.3.3, 5.5 | DI-IPSC-81434 | Interface Requirements Specification (IRS) | 5.4.1, 5.4.2, 5.13.5 | DI-IPSC-81432 | System/Subsystem Design Description (SSDD) |
| 5.4.1, 5.4.2, 5.6.1, 5.6.2, 5.6.3 | DI-IPSC-81436 | Interface Design Description (IDD) |
| 5.5 | DI-IPSC-81433 | Software Requirements Specification (SRS) |
| 5.6.1, 5.6.2, 5.6.3 | DI-IPSC-81435 | Software Design Description (SDD) |
| 5.4.1, 5.6.1, 5.6.3 | DI-IPSC-81437 | Database Design Description (DBDD) |
| 5.9.3, 5.11.3 | DI-IPSC-81439 | Software Test Description (STD) |
| 5.9.7, 5.11.7 | DI-IPSC-81440 | Software Test Report (STR) |
| 5.12.1, 5.13.1, 5.13.2, 5.13.4 | DI-IPSC-81441 | Software Product Specification (SPS) |
| 5.12.2, 5.13.3 | DI-IPSC-81442 | Software Version Description (SVD) |
| 5.12.3.1 | DI-IPSC-81443 | Software User Manual (SUM) |
| 5.12.3.2 | DI-IPSC-81445 | Software Input/Output Manual (SIOM) |
| 5.12.3.3 | DI-IPSC-81444 | Software Center Operator Manual (SCOM) |
| 5.12.3.4 | DI-IPSC-81446 | Computer Operation Manual (COM) |
| 5.13.6.1 | DI-IPSC-81447 | Computer Programming Manual (CPM) |
| 5.13.6.2 | DI-IPSC-81448 | Firmware Support Manual (FSM) |
The above DIDs were those cleared as of the date of this standard. The current issue of DOD 5010.12, Acquisition Management Systems and Data Requirements Control List (AMSDL), must be researched to ensure that only current, cleared DIDs are cited on the Form 1423.
If the CDRL calls for a DID different from the one named in corresponding paragraph(s) of this standard, all references to the DID in the standard should be interpreted to mean the one in the CDRL.
Depending on contract provisions, the developer may be permitted to satisfy CDRL requirements by delivering: 1) a repository or database containing the information specified in the cited DID; 2) a means of accessing that repository or database, such as a CASE tool, if not already available to the recipients designated on the CDRL; and 3) a hard-copy or electronically stored table of contents, specifying how and where to access the information required in each paragraph of the DID.
This standard and its Data Item Descriptions (DIDs) are applied at the discretion of the acquirer. In each application, the standard and DIDs should be tailored to the specific requirements of a particular program, program phase, or contractual structure. Care should be taken to eliminate tasks that add unnecessary costs and data that do not add value to the process or the product. Tailoring for the standard takes the form of deletion of activities, alteration of activities to more explicitly reflect the application to a particular effort, or addition of activities to satisfy program requirements. This tailoring is specified in the Statement of Work. Tailoring for the DIDs consists of deleting requirements for unneeded information and making other changes, such as combining two documents under one cover, that do not increase the required workload. DID tailoring for deliverables is specified in Block 16 of the CDRL.
Developer cost/schedule reports should be prepared at the CSCI level. The cost reports should indicate budgeted versus actual expenditures and should conform to the Work Breakdown Structure (WBS) applicable to the development effort. These reports should also indicate to the acquirer planned, actual, and predicted progress.
Figure 2 identifies a set of standardization documents related to software development. These and other standardization documents may be imposed or quoted in the Statement of Work to supplement the requirements in MIL-STD-498. MIL-STD-498 does not invoke these documents. The acquirer should use caution to ensure that supplemental standards are appropriate to the project and that any conflicts among these standards or with MIL-STD-498 are identified and resolved.
The following list of key words may be used to catalog or characterize key topics in this standard.
Builds/incremental development
Computer software configuration item
Database
Joint technical/management reviews
Operational concept
Reusable software
Risk management
Security/privacy
Software
Software configuration management
Software development
Software documentation
Software implementation
Software management indicators
Software product evaluation
Software quality assurance
Software requirements analysis
Software safety
Software support
Software testing
Software unit
Tailoring
Translator: Simon Wright simon@pogner.demon.co.uk
Last updated: 22.iii.99