Impact of adopting commercial practices in software development and maintenance

• Main Author: Mullins, Thomas E.
• Other Authors: McCaffrey, Martin J.
• Language: en_US
• Published: Monterey, California. Naval Postgraduate School 2013
• Online Access: http://hdl.handle.net/10945/31600

Modern Army armament systems are becoming increasingly reliant on embedded software. The latest Army version of the self-propelled howitzer, Paladin, includes in its subsystems: an inertial navigation and pointing system, an automatic fire control system, on-board prognostics and diagnostics, and embedded training. All of these subsystems are dependent upon software. The replacement for Paladin, Crusader, will be even more soft- ware intensive. The software in Paladin and previous armament systems was developed using military standards. On 29 June 1995, the Secretary of Defense directed the services to change from using military standards to commercial practices. MIL-STDA98, Software Development and Documentation, was approved on 4 November 1995 for interim use for two years. During those two years the military and industry are to develop a commercial replacement for MIL-STD-I98. For the two year period, existing commercial software standards are to he used to the maximum extent practicable. This thesis addresses the impact of adopting commercial practices in the development and maintenance of embedded software for Army armament systems. It provides initial insight into the impact on contracting for development and maintenance, test and evaluation, maintenance, potential contractors and risk for embedded armament system software. Paladin, Crusader and Sense and Destroy Armor (SADARM) are used as examples in the study. The thesis makes recommendations to reduce the impact of the change to commercial software practices. The insights developed in this thesis should provide a basis for early evaluation and modification of implementing procedures and guidelines.