Abstract
It is not news that there are problems with acquisition of defense systems. Over the past ten years, there has been over 400 billion dollars of growth in acquisition costs, money which could have been used to provide additional capability to the warfighter. DoD has several initiatives to address this chronic problem. Software-intensive systems, however, pose some unique considerations, especially in the transition to the system design and development, and sustainment phases. This paper outlines some of the characteristics of software intensive systems in the context of DoD’s acquisition reform initiatives, and provides recommendations to better address software sustainment in defense systems.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
