Innovations In Software Engineering For Defense Systems

Recent rough estimates are that the U.S. Department of Defense (DoD) spends at least $38 billion a year on the research, development, testing, and evaluation of new defense systems; approximately 40 percent of that cost-at least $16 billion-is spent on software development and testing. There is widespread understanding within DoD that the effectiveness of software-intensive defense systems is often hampered by low-quality software as well as increased costs and late delivery of software components. Given the costs involved, even relatively incremental improvements to the software development process for defense systems could represent a large savings in funds. And given the importance of producing defense software that will carry out its intended function, relatively small improvements to the quality of defense software systems would be extremely important to identify. DoD software engineers and test and evaluation officials may not be fully aware of a range of available techniques, because of both the recent development of these techniques and their origination from an orientation somewhat removed from software engineering, i.e., from a statistical perspective. The panel's charge therefore was to convene a workshop to identify statistical software engineering techniques that could have applicability to DoD systems in development.

Recent rough estimates are that the U.S. Department of Defense (DoD) spends at least $38 billion a year on the research, development, testing, and evaluation of new defense systems; approximately 40 percent of that cost-at least $16 billion-is spent on software development and testing. There is widespread understanding within DoD that the effectiveness of software-intensive defense systems is often hampered by low-quality software as well as increased costs and late delivery of software components. Given the costs involved, even relatively incremental improvements to the software development process for defense systems could represent a large savings in funds. And given the importance of producing defense software that will carry out its intended function, relatively small improvements to the quality of defense software systems would be extremely important to identify. DoD software engineers and test and evaluation officials may not be fully aware of a range of available techniques, because of both the recent development of these techniques and their origination from an orientation somewhat removed from software engineering, i.e., from a statistical perspective. The panel's charge therefore was to convene a workshop to identify statistical software engineering techniques that could have applicability to DoD systems in development.

Recent rough estimates are that the U.S. Department of Defense (DoD) spends at least $38 billion a year on the research, development, testing, and evaluation of new defense systems; approximately 40 percent of that cost-at least $16 billion-is spent on software development and testing. There is widespread understanding within DoD that the effectiveness of software-intensive defense systems is often hampered by low-quality software as well as increased costs and late delivery of software components. Given the costs involved, even relatively incremental improvements to the software development process for defense systems could represent a large savings in funds. And given the importance of producing defense software that will carry out its intended function, relatively small improvements to the quality of defense software systems would be extremely important to identify. DoD software engineers and test and evaluation officials may not be fully aware of a range of available techniques, because of both the recent development of these techniques and their origination from an orientation somewhat removed from software engineering, i.e., from a statistical perspective. The panel's charge therefore was to convene a workshop to identify statistical software engineering techniques that could have applicability to DoD systems in development.

During the past decade and a half, the National Research Council, through its Committee on National Statistics, has carried out a number of studies on the application of statistical methods to improve the testing and development of defense systems. These studies were intended to provide advice to the Department of Defense (DOD), which sponsored these studies. The previous studies have been concerned with the role of statistical methods in testing and evaluation, reliability practices, software methods, combining information, and evolutionary acquisition. Industrial Methods for the Effective Testing and Development of Defense Systems is the latest in a series of studies, and unlike earlier studies, this report identifies current engineering practices that have proved successful in industrial applications for system development and testing. This report explores how developmental and operational testing, modeling and simulation, and related techniques can improve the development and performance of defense systems, particularly techniques that have been shown to be effective in industrial applications and are likely to be useful in defense system development. In addition to the broad issues, the report identifies three specific topics for its focus: finding failure modes earlier, technology maturity, and use of all relevant information for operational assessments.

Innovation is the lifeline of national development. This handbook is a collection of chapters that provide techniques and methodologies for achieving the transfer of defense-targeted science and technology development for general industrial applications. The handbook shows how to translate theory and ideas into practical applications. Experts from national defense institutions, government laboratories, business, and industry contributed chapters to this handbook. The handbook also serves as an archival guide for nations, communities, and businesses expecting to embark upon science and technology transfer to industry. Included are several domestic and international case examples of practical innovation. Since the dawn of history, nations have engrossed themselves in developing new tools, techniques, and methodologies to protect their geographical boundaries. From the crude implements used by prehistorical people to very modern technologies, the end game has been the same. That is, to protect the homeland. Even in times of peace, efforts must be made to develop new machinery, equipment, processes, and devices targeted for the protection of the nation. The emergence of organized nations and structured communities facilitated even more innovative techniques of national defense. Evolution, revolution, and innovation have defined human existence for millennia. From the Ice Age to the Stone Age, the Bronze Age, the Iron Age, and to the modern age, innovation, rudimentary as it may be in many cases, has determined how humans move from one stage to the next. This comprehensive handbook provides a clear guide on the nuances of initiating and actualizing innovation. Both the qualitative and quantitative aspects of innovation are covered in the handbook. Features: Uses a systems framework to zero in on science and technology transfer Focuses on leveraging technical developments in defense organizations for general societal applications Coalesces the transfer strategies collated from various sources and practical applications Represents a world-class diverse collection of science and technology development, utilization, and transfer Highlights a strategy for government, academia, and industry partnerships

The development and application of technology has been an essential part of U.S. airpower, leading to a century of air supremacy. But that developmental path has rarely been straight, and it has never been smooth. Only the extraordinary efforts of exceptional leadership - in the Air Forces and the wider Department of Defense, in science and in industry - have made the triumphs of military airpower possible. Development Planning provides recommendations to improve development planning for near-term acquisition projects, concepts not quite ready for acquisition, corporate strategic plans, and training of acquisition personnel. This report reviews past uses of development planning by the Air Force, and offers an organizational construct that will help the Air Force across its core functions. Developmental planning, used properly by experienced practitioners, can provide the Air Force leadership with a tool to answer the critical question, Over the next 20 years in 5-year increments, what capability gaps will the Air Force have that must be filled? Development planning will also provide for development of the workforce skills needed to think strategically and to defectively define and close the capability gap. This report describes what development planning could be and should be for the Air Force.

Critical Code contemplates Department of Defense (DoD) needs and priorities for software research and suggests a research agenda and related actions. Building on two prior booksâ€"Summary of a Workshop on Software Intensive Systems and Uncertainty at Scale and Preliminary Observations on DoD Software Research Needs and Prioritiesâ€"the present volume assesses the nature of the national investment in software research and, in particular, considers ways to revitalize the knowledge base needed to design, produce, and employ software-intensive systems for tomorrow's defense needs. Critical Code discusses four sets of questions: To what extent is software capability significant for the DoD? Is it becoming more or less significant and strategic in systems development? Will the advances in software producibility needed by the DoD emerge unaided from industry at a pace sufficient to meet evolving defense requirements? What are the opportunities for the DoD to make more effective use of emerging technology to improve software capability and software producibility? In which technology areas should the DoD invest in research to advance defense software capability and producibility?

We cannot manage and control what we cannot measure and assess. Poor assessment results have been cited as a primary reason for project failures, in terms of cost, schedule, and quality. This book introduces metrics, rubrics, and standards pertinent to assessing innovation. Assessing Innovation: Metrics, Rubrics, and Standards provides a new view for the embracing of innovation and establishing a quantitative basis for determining innovation levels. It bridges innovation with practice and presents a systems view as it incorporates the human element and discusses the different roles carried out. This book offers standards that will guide readers as they tackle sustaining innovation and leverages Badiru’s Umbrella Model in the process. The inclusion of methodologies suitable for determining where and when innovation is happening, and to what extent it is currently being carried out, make this a unique book, along with being the only book that addresses innovation metrics, rubrics, and standards in an integrated fashion. Seen as a way to help advance the diverse pursuit of innovation, this book is an ideal read for those in engineering, business, industry, academia, government, and the military.