Contents
The MIL-STD-498 Documents
| Document | PDF Size | Download |
|---|---|---|
| MIL-STD-498 Application and Reference Guidebook, pp i–24 | 258,911 | |
| MIL-STD-498 Application and Reference Guidebook, pp 25–344 | 2,004,843 | |
| MIL-STD-498 Application and Reference Guidebook, pp 345–389 | 121,598 | |
| MIL-STD-498 Contract Data Requirements List (CDRL) | 1,489,031 | |
| MIL-STD-498 Info | 94,336 | |
| MIL-STD-498 Overview and Tailoring Guidebook | 749,429 | |
| MIL-STD-498 Software Development and Documentation | 683,798 | |
| Data Item Description (DID) | PDF Size | Download |
| Computer Operation Manual (COM) | 24,064 | |
| Computer Programming Manual (CPM) | 21,447 | |
| Database Design Description (DBDD) | 38,978 | |
| Firmware Support Manual (FSM) | 23,041 | |
| Interface Design Description (IDD) | 31,220 | |
| Interface Requirements Specification (IRS) | 36,762 | |
| Operational Concept Description (OCD) | 34,929 | |
| Software Center Operator Manual (SCOM) | 31,963 | |
| Software Design Description (SDD) | 51,038 | |
| Software Development Plan (SDP) | 57,574 | |
| Software Input Output Manual (SIOM) | 59,345 | |
| Software Installation Plan (SIP) | 31,259 | |
| Software Product Specification (SPS) | 33,035 | |
| Software Requirements Specification (SRS) | 64,458 | |
| System Subsystem Design Description (SSDD) | 40,863 | |
| System Subsystem Specification (SSS) | 56,274 | |
| Software Test Description (STD) | 38,137 | |
| Software Test Plan (STP) | 40,417 | |
| Software Test Report (STR) | 27,134 | |
| Software Transition Plan (STrP) | 29,364 | |
| Software User Manual (SUM) | 34,958 | |
| Software Version Description (SVD) | 22,504 |
Data Item Descriptions (DIDs)
Request for Quotation Phase
Operational Concept Description (OCD)
Software Development Plan (SDP)
Software Test Plan (STP)
System Design Phase
Interface Requirements Specification (IRS)
Software Requirements Specification (SRS)
The Software Requirements Specification (SRS) specifies the requirements for a Computer Software Configuration Item (CSCI) and the methods to be used to ensure that each requirement has been met. Requirements pertaining to the CSCI’s external interfaces may be presented in the SRS or in one or more Interface Requirements Specifications (IRSs) (DI-IPSC-81434) referenced from the SRS.
The SRS, possibly supplemented by IRSs, is used as the basis for design and qualification testing of a CSCI.
This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by specific and discrete task requirements as delineated in the contract.
This DID is used when the developer is tasked to define and record the software requirements to be met by a CSCI.
Requirements pertaining to CSCI interfaces may be presented in the SRS or in IRSs.
The Contract Data Requirements List (CDRL) (DD 1423) should specify whether deliverable data are to be delivered on paper or electronic media; are to be in a given electronic form (such as ASCII, CALS, or compatible with a specified word processor or other support software); may be delivered in developer format rather than in the format specified herein; and may reside in a computer-aided software engineering (CASE) or other automated tool rather than in the form of a traditional document.
This DID supersedes DI-MCCR-80025A and DI-MCCR-80301.
Automated techniques. Use of automated techniques is encouraged. The term “document” in this DID means a collection of data regardless of its medium.
Alternate presentation styles. Diagrams, tables, matrices, and other presentation styles are acceptable substitutes for text when data required by this DID can be made more readable using these styles.
System/Subsystem Specification (SSS)
Development Phase
Database Design Description (DBDD)
Interface Design Description (IDD)
Software Design Description (SDD)
System/Subsystem Design Description (SSDD)
Software Test Description (STD)
Testing Phase
Software Test Report (STR)
Manuals
Software Center Operator Manual (SCOM)
The Software Center Operator Manual (SCOM) provides personnel in a computer center or other centralized or networked software installation information on how to install and operate a software system.
The SCOM is developed for software systems that will be installed in a computer center or other centralized or networked software installation, with users accessing the system via terminals or personal computers or submitting and receiving inputs and outputs in batch or interactive mode.
This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by specific and discrete task requirements as delineated in the contract.
This DID is used when the developer is tasked to identify and record information needed by persons who will operate software in a computer center or other centralized or networked software installation, so that the software can be used by others.
This DID is often used with the Software Input/Output Manual (SIOM) (DI-IPSC-81445). This pair of manuals is an alternative to the Software User Manual (SUM) (DI-IPSC-81443).
The Contract Data Requirements List (CDRL) (DD 1423) should specify whether deliverable data are to be delivered on paper or electronic media; are to be in a given electronic form (such as ASCII, CALS, or compatible with a specified word processor or other support software); may be delivered in developer format rather than in the format specified herein; and may reside in a computer-aided software engineering (CASE) or other automated tool rather than in the form of a traditional document.
This DID supersedes DI-IPSC-80695.
Automated techniques. Use of automated techniques is encouraged. The term “document” in this DID means a collection of data regardless of its medium.
Alternate presentation styles. Diagrams, tables, matrices, and other presentation styles are acceptable substitutes for text when data required by this DID can be made more readable using these styles.
Software Input/Output Manual (SIOM)
Software User Manual (SUM)
Delivery Phase
Software Product Specification (SPS)
Software Version Description (SVD)
Rarely Used DIDs
Computer Operation Manual (COM)
The Computer Operation Manual (COM) provides information needed to operate a given computer and its peripheral equipment. This manual focuses on the computer itself, not on particular software that will run on the computer.
The COM is intended for newly developed computers, special-purpose computers, or other computers for which commercial or other operation manuals are not readily available.
This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by specific and discrete task requirements as delineated in the contract.
This DID is used when the developer is tasked to identify and record information needed to operate the computer(s) on which software will run.
The Contract Data Requirements List (CDRL) (DD 1423) should specify whether deliverable data are to be delivered on paper or electronic media; are to be in a given electronic form (such as ASCII, CALS, or compatible with a specified word processor or other support software); may be delivered in developer format rather than in the format specified herein; and may reside in a computer-aided software engineering (CASE) or other automated tool rather than in the form of a traditional document.
This DID supersedes DI-MCCR-80018A and DI-MCCR-80316.
Automated techniques. Use of automated techniques is encouraged. The term “document” in this DID means a collection of data regardless of its medium.
Alternate presentation styles. Diagrams, tables, and other presentation styles are acceptable substitutes for text when data required by this DID can be made more readable using these styles.
Computer Programming Manual (CPM)
Firmware Support Manual (FSM)
Software Transition Plan (STrP)
The Software Transition Plan (STrP) identifies the hardware, software, and other resources needed for life cycle support of deliverable software and describes the developer’s plans for transitioning deliverable items to the support agency.
The STrP is developed if the software support concept calls for transition of responsibility from the developer to a separate support agency. The STrP may also be used by the acquirer for updating the Computer Resources Life Cycle Management Plan.
This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by specific and discrete task requirements as delineated in the contract.
This DID is used when the developer is tasked to develop and record plans for transitioning deliverable items to the support agency.
The Contract Data Requirements List (CDRL) (DD 1423) should specify whether deliverable data are to be delivered on paper or electronic media; are to be in a given electronic form (such as ASCII, CALS, or compatible with a specified word processor or other support software); may be delivered in developer format rather than in the format specified herein; and may reside in a computer-aided software engineering (CASE) or other automated tool rather than in the form of a traditional document.
This DID supersedes DI-MCCR-80024A.
Automated techniques. Use of automated techniques is encouraged. The term “document” in this DID means a collection of data regardless of its medium.
Alternate presentation styles. Diagrams, tables, matrices, and other presentation styles are acceptable substitutes for text when data required by this DID can be made more readable using these styles.
Miscellaneous
Software Installation Plan (SIP)
The Software Installation Plan (SIP) is a plan for installing software at user sites, including preparations, user training, and conversion from existing systems.
The SIP is developed when the developer will be involved in the installation of software at user sites and when the installation process will be sufficiently complex to require a documented plan. For software embedded in a hardware-software system, a fielding or deployment plan for the hardware-software system may make a separate SIP unnecessary.
This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by specific and discrete task requirements as delineated in the contract.
This DID is used when the developer is tasked to develop and record plans for performing software installation and training at user sites.
The Contract Data Requirements List (CDRL) (DD 1423) should specify whether deliverable data are to be delivered on paper or electronic media; are to be in a given electronic form (such as ASCII, CALS, or compatible with a specified word processor or other support software); may be delivered in developer format rather than in the format specified herein; and may reside in a computer-aided software engineering (CASE) or other automated tool rather than in the form of a traditional document.
This DID supersedes DI-IPSC-80699.
Automated techniques. Use of automated techniques is encouraged. The term “document” in this DID means a collection of data regardless of its medium.
Alternate presentation styles. Diagrams, tables, matrices, and other presentation styles are acceptable substitutes for text when data required by this DID can be made more readable using these styles.