Software intensive system dau

Defense unique software intensive program a system in which software represents the largest segment in one or more of the following criteria. In this domain, we applied traditional program and. Identify key laws and software acquisitionmanagement policies and practices that are required for the acquisition of adod softwareintensive system. Software sustainment under secretary of defense for. Dau page 1 of 2 software acquisition exam here is your test result. The following are best practices detailed in the defense acquisition guidebook dag in chapter 4. The domain i work in is categorized as software intensive system of systems sisos. Automated information system ais as defined in enclosure 1 table 1 of dodi 5000. Defense acquisition university core plus framework dau 2008. Sustaining software intensive systems, lapham, cmusei2006tn 007.

Productivity and policy naval postgraduate school acquisition symposium 11 may 2011 kathlyn loudin, ph. October 2008 integration of software intensive systems copyright 2008 lockheed martin corporation. Defense acquisition system overview defense acquisition. Aiss exclude hardware and software embedded in a weapons system. Enable department of defense dod, civilian government, and industry organizations to acquire, develop, operate. This paper examines software intensive system acquisition, including best practices and assessment framework. The pathway objective is to facilitate rapid and iterative delivery of software capability to the user. Esc made significant progress to reform software acquisition processes in the early 90s and was seen as an enlightened leader. As todays systems become increasingly reliant on software, the issues surrounding sustainment become increasingly complex. There are several definitions for software intensive systems including ieee 14712000. Software acquisition adaptive acquisition framework dau. Chapter 6 information technology and business systems 11.

Defense development and acquisition programs continue to experience software problems resulting in significant cost overruns, schedule slips and performance difficulties. Software systems are now pervading key areas for the daytoday functioning of our society. Comprehensive requirements to support, maintain and operate the software capabilities of a system. Guidebook for acquisition of naval software intensive systems.

Open systems architecture osa description an open systems architecture osa approach integrates business and technical practices that yield systems with severable modules which can be competed. The process of modifying a software system after delivery to correct faults, improve. The risks of ignoring these issues can potentially undermine the stability, enhancement, and longevity of systems in the field. Sustaining softwareintensive systems carnegie mellon university. Software intensive systems are inherent in todays complex. Acquisitions of software intensive systems by the department of defense. They are required to participate in heterogeneous networks of. Monitoring softwareintensive system acquisition sisa programs posted. Monitoring softwareintensive system acquisition sisa.

1552 221 1273 776 97 763 1145 1302 861 928 1487 1365 1124 631 793 1573 1409 987 688 1562 193 386 1138 948 708 30 987 711 1017 528 423 693 1454 834 902 381 636 218 770 184