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.

6.3 Relationship between standard and CDRL. 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.

6.4 Delivery of tool contents. 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.

6.5 Tailoring guidance. 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.

6.6 Cost/schedule reporting. 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.

6.7 Related standardization documents. 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.

Topic and MIL-STD-498 Paragraph	Related Stadardization Documents (Determine latest version before use)
Behavioral design (5.4.1, 5.6.1)	MIL-STD-1B01, User Computer Interface MIL-HDBK-761, Human Engineering Guidelines for Management Information Systems
Computer security (4.2)	DOD-5200.2B STD, DoD Trusted Computer System Evaluation Criteria
Configuration management (5.14)	ANSI/IEEE Std 828, Standard for Software Configuration Management Plans ANSI/IEEE Std 1042, Guide to Software Configuration Management MIL-STD-973, Configuration Management MIL-HDBK-61 Guidelines for Configuration Management
Continuous acquisition and life-cycle support (CALS)	MIL-STD-1840, Automated Interchange of Technical Information MIL-STD-1556, Government-Industry Data Exchange Program MIL-HDBK-59, Government Acquisition and Life-Cycle Support Program Implementation Guide MIL-HDBK-800, Documentation Streamlining MIL-D-28000, Digital Representation for Communication of Product Data: IGES Application Subset and IGES Application Protocols MIL-M-28001, Markup Requirements and Ggeneric Style Specification for Electronic Printed Output and Exchange of Text MIL-R-28002, Requirements for Raster Graphics Representation in Binary Format MIL-D-28003, Digital Representation for Communication of Illustration Data: CGM Application Profile
Joint technical and management reviews (5.18, App. E)	ANSI/IEEE Std 1028, Standard for Software Reviews and Audits MIL-STD-499, Engineering Management MIL-STD-1521, Technical Reviews and Audits for Systems, Equipments, and Computer Software  (audit portion superseded by (MIL-STD-973)
Programming Languages (5.7.1)	FIPS-PUB-119, Ada (also issued as ANSI/ISO/IEC 8652: formerly ANSI/NIL-STD-1815, Ada Programming Languauge
Software design (5.4, 5.6)	ANSI/IEEE Std 1016, Recommended Practice for Software Design Descriptions IEEE Std 1016.1, Guide for Software Design Descriptions IEEE/ANSI Std 990, Recommended Practice for Ada as a Program Design Language
Software development environment (5.2)	IEEE Std 1209, Recommended Practice for the Evaluation and Selections of CASE Tools DOD-STD-1467 (AR), Software Support Environment MIL-HDBK-782 (AR), Software Support Environment Acquisition
Software development planning (5.1.1)	ANSI/IEEE Std 1058.1, Standard for Software Project Management Plans
Software development process (4.1, App. G)	ISO/IEC 12207 (when issued), Software Life-Cycle Processes ANSI/IEEE Std 1074, Standar for Developing Software Life Cycle Processes MIL-STD-1803 (USAF), Software Development Integrity Program Guidebook on MIL-STD-498 (when issued) MIL-HDBK-498 (when issued)

Note: MIL-STD-498 does not invoke any of these documents.

Figure 2: Related Standardization Documents

6.8 Subject term (key word) listing. The following list of key words may be used to catalog or characterize key topics in this standard.

 

	Builds/incremental development             Software documentation

 	Computer software configuration item       Software implementation

 	Database                                   Software management indicators

 	Joint technical/management review          Software product evaluation

 	Operational concept                        Software quality assurance

 	Reusable software                          Software requirements analysis

 	Risk management                            Software safety

 	Security/privacy                           Software support

 	Software                                   Software testing

 	Software configuration management          Software unit

 	Software development                       Tailoring