From Art Form to Engineering Discipline?: A History of U.S. Military Software Development Standards, 1974-1998
PrePrint
ISSN: 1058-6180
DOI Bookmark:
http://doi.ieeecomputersociety.org/10.1109/MAHC.2009.58
From the mid-1970s until the mid-1990s, the U.S. Department of Defense (DoD) attempted to enforce software standards for the development of its defense systems. The history if this efforts played out as a struggle for control between the DoD and its contractors in the software and aerospace industries. The industry did not oppose software development standardization per se, but often objected to the specifics of the military's standards. Many software developers, however, resented the software development standards imposed by the DoD, which they felt violated the principle of professional judgment. In addition to highlighting the role that software standards played in debates about professional independence, this story also calls into question the image of a monolithic military-industrial complex. The ultimate failure of the military to get its way reflected, in part, the growing independence of software developers from the military market.
Index Terms:
D.2.0.d Standards, D.2.1 Requirements/Specifications, D.2.1 Requirements/Specifications, D.2.0.e Surveys of historical development of one particular area,
Citation:
Christopher McDonald, "From Art Form to Engineering Discipline?: A History of U.S. Military Software Development Standards, 1974-1998," IEEE Annals of the History of Computing, 08 Sept. 2009. IEEE computer Society Digital Library. IEEE Computer Society, <http://doi.ieeecomputersociety.org/10.1109/MAHC.2009.58>
Usage of this product signifies your acceptance of the
Terms of Use.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||