Skip to main content

Currently Skimming:

Software Sustainment and Maintenance of Weapons Systems for the United States Air Force: Proceedings of a Workshop - in Brief
Pages 1-12

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 1...
... REVIEW OF PREVIOUS WORK DEFENSE SCIENCE BOARD SOFTWARE REPORT Paul Nielsen (Committee Chair) introduced and welcomed the workshop participants and led an opening discussion.
From page 2...
... warned that the DoD push for agile software development practices will mean that cost benchmarks will no longer be hard and fast and programs will not know the full cost of development and sustainment upfront due to agile practices' need for flexibility. 1 Defense Science Board, Design and Acquisition of Software for Defense Systems, February 2018, https://www.acq.osd.mil/dsb/ reports/2010s/DSB_SWA_Report_FINALdelivered2-21-2018.pdf.
From page 3...
... Transforming a team under new processes means restructuring and moving forward together as a team into the agile software development sphere. 3 Defense Acquisitions University, "Integrated Defense Acquisition, Technology, and Logistics Life Cycle Management System," https://timemilitary.files.wordpress.com/2013/02/acquisition_life_cycle_management.pdf.
From page 4...
... money is used but there are no clear guidelines on how to use those categories for software development activities, nor is there a designated software sustainment category. Thornton mentioned that a key challenge to improving software sustainment, weapons systems, and networks is authority to operate (ATO)
From page 5...
... SOURCE: Nick Guertin, Software Engineering Institute, "Software Sustainment and the Challenge of Modular Capability Innovation," presentation to the workshop, February 28, 2019; adapted from Defense Science Board, Design and Acquisition of Software for Defense Systems, February 2018, www.acq.osd.mil/dsb/reports/2010s/ DSB_SWA_Report_FINALdelivered2-21-2018.pdf. nearly impossible to predict the next method or mechanism that will accelerate software development.
From page 6...
... Software sustainment and a software development mindset needs to be a part of the whole development community. When discussing new forms of software development, Guertin said that he struggled at the beginning with too many prototype initiatives.
From page 7...
... Sustainers need to balance the circle of development, because the warfighter wants the maximum available capability he or she can get at every moment. When Winston asked Gill how the program could apply agile software development metrics when it is married tightly to the current hardware construct, she said that the program could put boundaries out there and then manage the risk within those boundaries.
From page 8...
... Bishop concluded his talk by saying his team is looking forward to making things better. SOFTWARE ENGINEER PERSPECTIVES ON SOFTWARE SUSTAINMENT A panel of SWEG personnel discussed workforce structure, management, and improvements that could be made.
From page 9...
... Nielsen said that maybe the USAF should take a software-focused approach, where hardware follows along behind. To this, Rayner responded that perhaps software sustainment changes shouldn't be the focus, but maybe the USAF should be looking in how to change the hardware production process to be more like the software development model.
From page 10...
... In addition, Winston said that the National Security Agency hired someone who was in the USAF pipeline for 9 months, so this is not a government-wide issue, but particularly a USAF one. Boleng made the point that Kessel Run proved its success that quality software development and sustainment that is secure and deployable could be created without all of the regulations and hurdles other more traditional programs have to deal with.
From page 11...
... The USAF needs to plan for tests and continuous developments earlier on in the life cycle of a program, and those tests will help the testing process overall by planning them in advance. Penney mentioned that end user operators really value the capabilities that technology provides, and providing those capabilities to end users faster could make a difference.
From page 12...
... , Chair, Carnegie Mellon Software Engineering Institute; Matthew Alexander, MIT Lincoln Laboratory; Lieutenant General (ret.) Ted Bowlds, USAF, IAI North America; John Grosh, Lawrence Livermore National Laboratory; Kevin Martin, HRL Laboratories, LLC; Heather Penney, Mitchell Institute for Aerospace Studies; Stephen Welby, Institute of Electrical and Electronics Engineers; and Rebecca Winston, Winston Strategic Management Consulting RAPPORTEUR: Catherine Puma, Research Associate, Air Force Studies Board STAFF: Ellen Chou, Director, Air Force Studies Board; George Coyle, Senior Program Officer; Ryan Murphy, Program Officer; Adrianna Hargrove, Finance Business Partner; Marguerite Schneider, Administrative Coordinator; Steven Darbes, Research Associate; Catherine Puma, Research Associate SPONSORS: This workshop was supported by the U.S.


This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More information on Chapter Skim is available.