CrossTalk: The Journal of Defense Software Engineering. Volume 20, Number 5, May 2007
Abstract
Acquiring software intensive systems (SIS) for large tactical weapons or information systems is, of course, much more difficult than buying a car. For one thing, software is part of a system (we usually acquire systems, not software) and this system is often part of a larger system. As our systems become more complex, we see the bulk of the functionality being implemented in software rather than hardware. Another aspect affecting the complexity of acquiring an SIS is that not all system functionality is known at time of contract award. Despite complexity and uncertainty, acquirers of an SIS must be smart buyers in order to deliver products that meet user requirements, that are delivered on time, and that are within budget. In this issue, the United States Army Program Executive Offices provide a unique perspective on software acquisition in "Software Acquisition in the Army," noting the similarities and differences in the issues programs face. Key aspects of software assurance are addressed in "Software Assurance: Five Essential Considerations for Acquisition Officials." The added complexity and interdependencies inherent in joint program acquisition is presented in "The Acquisition of Joint Programs: The Implications of Interdependencies." Finally, four key recommendations in "Defense Acquisition Performance Assessment -- The Life-Cycle Perspective of Selected Recommendations" are discussed from the perspective of their implementability.
Document Details
- Document Type
- Technical Report
- Publication Date
- May 01, 2007
- Accession Number
- ADA487054