DOD-STD-2167A
Encyclopedia
DOD-STD-2167A titled "Defense Systems Software Development", was a United States defense standard
, published on February 29, 1988, which updated the less well known DOD-STD-2167 published 4 June 1985. This document established "uniform requirements for the software development that are applicable throughout the system life cycle." It was designed to be used with MIL-STD-2168, "Defense System Software Quality Program".
On December 5th, 1994 it was superseded by MIL-STD-498
, which merged DOD-STD-2167A, DOD-STD-7935A, and DOD-STD-2168 into a single document, and addressed some vendor criticisms.
. Although the document states "the contractor is responsible for selecting software development methods (for example, rapid prototyping)", it also required "formal reviews and audits" that seemed to lock the vendor into designing and documenting the system before any implementation began.
Another criticism was the focus on design documents, to the exclusion of Computer-Aided Software Engineering
(CASE) tools being used in the industry. Vendors would often use the CASE tools to design the software, then write several standards-required documents to describe the CASE-formatted data. This created problems matching design documents to the actual product.
One result of these criticisms was to begin designing a successor standard, which became MIL-STD-498
. Another result was a preference for formal industry-designed standards (such as IEEE 12207
) and informal "best practice
" specifications, rather than trying to determine the best processes and making them formal specifications.
Defense Standard
A United States defense standard, often called a military standard, "MIL-STD", "MIL-SPEC", or "MilSpecs", is used to help achieve standardization objectives by the U.S...
, published on February 29, 1988, which updated the less well known DOD-STD-2167 published 4 June 1985. This document established "uniform requirements for the software development that are applicable throughout the system life cycle." It was designed to be used with MIL-STD-2168, "Defense System Software Quality Program".
On December 5th, 1994 it was superseded by MIL-STD-498
MIL-STD-498
MIL-STD-498 was a United States military standard whose purpose was to "establish uniform requirements for software development and documentation." It was released Nov. 8, 1994, and replaced DOD-STD-2167A, DOD-STD-7935A, and DOD-STD-1703...
, which merged DOD-STD-2167A, DOD-STD-7935A, and DOD-STD-2168 into a single document, and addressed some vendor criticisms.
Criticism
One criticism of the standard was that it was biased toward the Waterfall ModelWaterfall model
The waterfall model is a sequential design process, often used in software development processes, in which progress is seen as flowing steadily downwards through the phases of Conception, Initiation, Analysis, Design, Construction, Testing, Production/Implementation and Maintenance.The waterfall...
. Although the document states "the contractor is responsible for selecting software development methods (for example, rapid prototyping)", it also required "formal reviews and audits" that seemed to lock the vendor into designing and documenting the system before any implementation began.
Another criticism was the focus on design documents, to the exclusion of Computer-Aided Software Engineering
Computer-aided software engineering
Computer-aided software engineering is the scientific application of a set of tools and methods to a software system which is meant to result in high-quality, defect-free, and maintainable software products...
(CASE) tools being used in the industry. Vendors would often use the CASE tools to design the software, then write several standards-required documents to describe the CASE-formatted data. This created problems matching design documents to the actual product.
One result of these criticisms was to begin designing a successor standard, which became MIL-STD-498
MIL-STD-498
MIL-STD-498 was a United States military standard whose purpose was to "establish uniform requirements for software development and documentation." It was released Nov. 8, 1994, and replaced DOD-STD-2167A, DOD-STD-7935A, and DOD-STD-1703...
. Another result was a preference for formal industry-designed standards (such as IEEE 12207
IEEE 12207
IEEE/EIA 12207.0, "Standard for Information Technology – Software Life Cycle Processes", is a standard that establishes a common framework for software life cycle process....
) and informal "best practice
Best practice
A best practice is a method or technique that has consistently shown results superior to those achieved with other means, and that is used as a benchmark...
" specifications, rather than trying to determine the best processes and making them formal specifications.