A consensus definition of this term is provided for this guidebook. Examine the impact of laws, policies, and regulations requiring the application of enterprise architecture concepts to dod it acquisition programs and projects. While dod has started using better software development approaches, we found some challenges to making them work. Gao196, accessible version, dod space acquisitions. The following are best practices detailed in the defense acquisition guidebook dag in chapter 4. In late 1991, the air force developed a process improvement program that was. The systems are deployed in a series of program increments, where each successive increment builds upon the capabilities and functionality previously deployed. It is distinguished from model 2 by the rapid delivery of capability through multiple increments. There is a critical need to rapidly transition stateoftheart technology and best practices to improve the acquisition, engineering, fielding, and evolution of softwareintensive dod systems. For example, vendor tools might identify anywhere between 25 and 45 inputs that are used to estimate software development. U software is key to meeting dods increasing demand for highquality, affordable, and timely national defense systems. Although the department of defense dod has a technical definition of sustainment, does the dod typically consider sustainment as maintenance.
Congressional appropriators would need to approve the idea of allocating funds into software dedicated accounts before the department could proceed. Key best practices applicable to dod software programs include the. The nine programs dod is teeing up for the pilot will be a mix of softwareintensive weapons systems and it business systems across the military services and defense agencies. The participating programs reflected a crosssection of both defense business systems and softwareintensive weapons systems. The dod faces the challenge that much of the early testing is done by the defense contractor, and by the time softwareintensive systems are handed over to the military, the testing is primarily integration, functional and performancedriven and is.
Also, although the army has developed an extensive software metrics program, it is of limited value because it is not connected to software failures in the field or. We looked at four software intensive dod space systems that had cost growth or delays. Dod to announce nine acquisition programs for software. Defense unique software intensive program a model of a program that is dominated by the need to develop a complex, usually defense unique, software program that will not be deployed until several software builds have been completed.
Chapter 6 information technology and business systems 11042019. Congressional appropriators would need to approve the idea of allocating funds into softwarededicated accounts before the department could proceed. Mar 05, 2020 the acquisition programs for the pilot will be a combination of information technology systems and software intensive weapons platforms across service branches and defense agencies. If you need to print pages from this book, we recommend downloading it as a pdf. Acquisition, development, operations, and sustainment of all dod softwareintensive system approved to use this pathway in order to demonstrate the viability and effectiveness of capabilities for operational use not later than one year after the date on which funds are first obligated to acquire or develop new software capability. The defense acquisition system is the management process by which the department of defense provides effective, affordable, and timely systems to the user. Acquisitions of software intensive systems by the department of defense dod. What is the definition of softwareintensive system. Defense unique software intensive program is a model of a program that is dominated by the need to develop a complex, usually defense unique, software program that will not be deployed until several software builds have been completed. Defense unique software intensive program a system in which software represents the largest segment in one or more of the following criteria. The secretary of defense should, to ensure dod has the knowledge it needs to oversee softwareintensive acquisitions, have acquirers require software contractors to collect and report metrics related to cost, schedule, size, requirements, tests, defects. Chapter 6 information technology and business systems 1104.
Mar 18, 2019 developing software for dod space systems, like gps, has historically taken longer and cost billions of dollars more than planned. Findings show that softwareintensive systems generally do not meet user. Forum software intensive systems engineering csiac. Gao suggests dod boost user inclusion in space program. This post, the first in a threepart series by robert ferguson, first explores the challenges to monitoring softwareintensive system acquisition sisa programs and presents the first two recommended best practices as detailed in the spruce post. Apr 16, 2018 armed with this new approach, we are exploring causal factors driving software cost within dod programs and systems. Pentagon teeing up nine programs to test new color of money.
We looked at four softwareintensive dod space systems that had cost growth or delays. Dod softwareintensive systems development semantic scholar. Reducing risk in dod softwareintensive systems development. Congress and dod should refactor statutes, regulations, and processes for software, enabling rapid deployment and continuous improvement of software to the field and providing increased insight to reduce the risk of slow, costly, and overgrown programs. Feb 01, 2019 software intensive systems are of various types, ranging from enterprise systems to iots and cps to industrial control systems where software plays a vital role towards design, construction and implementation of such systems.
The second post in this series will present the next three best practices. Defense unique software intensive program the model 2. Department of the air force office of the chief software. Product construction adopt life cycle configuration mgmt manage and trace requirements use systems based software design ensure data and db interoperability define and control interfaces design twice, code once.
The acquisition programs for the pilot will be a combination of information technology systems and software intensive weapons platforms across service branches and defense agencies. Applying extensive in the trenches experience, the spmn enables department of defense program managers to achieve program success and deliver quality systems on schedule and on budget. In addition, information on resources including labor hours, overhead costs, material costs, and other direct costs are available through the ccd report dd form 19211, functional costhour report. In addition to evaluating newly developed software swa guides for program managers and. Armed with this new approach, we are exploring causal factors driving software cost within dod programs and systems. What types of development and acquisition activities are required to sustain softwareintensive systems. Developing software for dod space systems, like gps, has historically taken longer and cost billions of dollars more than planned. Top 4 download periodically updates software information of dod full versions from the publishers, but some information may be slightly outofdate using warez version, crack, warez passwords, patches, serial numbers, registration codes, key generator, pirate key, keymaker or keygen for dod license key is illegal. Top 4 download periodically updates software information of dod full versions from the publishers, but some information may be slightly outofdate using warez version, crack, warez passwords, patches, serial numbers, registration codes, key generator, pirate. How does the increased use of commercialofftheshelf software complicate sustainment. Computer software does not include computer databases or computer software documentation. However, dod is inactive to implement the sisa practices because dod doesnt fully understand how and why the sisa practices affect the performance of softwareintensive system development.
Mar 04, 2016 which of the following are best practices that may be appropriate for software intensive programs. Acquisition, development, operations, and sustainment of all dod software intensive system approved to use this pathway in order to demonstrate the viability and effectiveness of capabilities for operational use not later than one year after the date on which funds are first obligated to acquire or develop new software capability. Used for software development programs where the deployment of the full capability will occur in multiple increments as new capability is developed and delivered, nominally in 1 to 2year cycles. The acquisition programs for the pilot will be a combination of information technology systems and softwareintensive weapons platforms across service branches and defense agencies. I n t e g r i t y s e r v i c e e x c e l l e n c e full assessment questionnaire translated into a 45 page questionnaire general interviewee and program information questions 37 related to the specific practice three bestworst practices interviewed three people on each project program manager chief engineer or chief architect software knowledgeable person in the program office. It describes problems uncovered in the last several months on several dod software intensive programs such as. Data is required from acat ia, acat ic or acat id programs containing software effort with a projected value. Government software acquisition policies dfars and.
This paper examines software intensive system acquisition, including best practices and assessment framework. Consider the risks of reusing existing software use metrics to manage and monitor risk to speed development, only test contractor chooses to use their own quality system at completion generate new code whenever possible 2 an example of. Select each model to learn more model 2 defense unique. Hybrid model b software dominant, depicts how a software intensive product development can include a mix of incrementally deployed software products or releases that include intermediate software builds. Analysis of softwareintensive system acquisition using. Jul 03, 2017 the dod faces the challenge that much of the early testing is done by the defense contractor, and by the time software intensive systems are handed over to the military, the testing is primarily integration, functional and performancedriven and is primarily related to frontend, black box testing. It describes problems uncovered in the last several months on several dod softwareintensive programs such as. Mar 11, 2020 the nine programs dod is teeing up for the pilot will be a mix of software intensive weapons systems and it business systems across the military services and defense agencies. All of the comments about incremental software fielding associated with model 3 in paragraph 5c3d apply to this model as well. What types of development and acquisition activities are required to sustain software intensive systems.
To identify proven industry and government software best practices and convey them to managers of largescale softwareintensive acquisition programs. Software acquisition adaptive acquisition framework. The four major department of defense dod softwareintensive space programs that. Which of the following are best practices that may be appropriate for software intensive programs. Computer software means computer programs, source code, source code listings, object code listings, design details, algorithms, processes, flow charts, formulae, and related material that would enable the software to be reproduced, recreated, or recompiled. Summary of a workshop on softwareintensive systems and. The term software intensive systems sis is used frequently in this guidebook, as well as throughout numerous air force and department of defense dod acquisition policy and guidance documents and joint chief of staff publications. Characteristics assesses the business environment and identifies existing commercial or government solutions that could be adopted to satisfy dod needs. Make security a firstorder consideration for all software intensive systems and acquisition programs, and prioritize regular and automated penetration testing to expose vulnerabilities and breach dod systems before adversaries do. Module 2 exam, part ii 1 which of the following are best practices that may be appropriate for software intensive programs select all that apply. Select all that apply possible answers please comment if you have the answer, thank you. Which of the following are best practices that may be. Unfortunately, this book cant be printed from the openbook. Excluded are computer resources, both hardware and software, that are an integral part of a weapon or weapon system.
Background an increasing number of dod softwareintensive systems are being procured with incremental acquisition strategies. Software program managers network software development. A new approach to dod software development and acquisition. Software program managers network 16 critical software practicestm dsb report on defense software nov 2000 source. Building on two prior bookssummary of a workshop on software intensive systems and uncertainty at scale and preliminary observations on dod software research needs and prioritiesthe present volume assesses the nature of the national investment in software research and, in particular, considers ways to revitalize the knowledge base needed to. Irreducible truths of softwareintensive program management. Dod and industry must change the practice of how software is procured and developed by adopting modern software development approaches, prioritizing speed as the critical metric, ensuring cybersecurity is an integrated element of the entire software life cycle, and purchasing existing commercial software whenever possible. Establish one or more new acquisition pathways for software that prioritize continuous integration and delivery of working software in. The challenge is really to apply new practices to all of our programs across the. The levelup team will also provide training and orientation on boarding to program office personnel and contractors, including assistance with instantiation of devsecops environments in cloud one or any existing dod approved environment, including classified and disconnected environments. The secretary of defense should, to ensure dod has the knowledge it needs to oversee software intensive acquisitions, have acquirers require software contractors to collect and report metrics related to cost, schedule, size, requirements, tests, defects, and.
Oct 26, 2015 this post, the first in a threepart series by robert ferguson, first explores the challenges to monitoring software intensive system acquisition sisa programs and presents the first two recommended best practices as detailed in the spruce post. Improving the acquisition of software intensive systems carnegie. Software and acquisition and practices study department of defense. Enable department of defense dod, civilian government, and. For example, program offices and system developers dont.