Air Force Software Sustainment and Maintenance of Weapons Systems (2020) / Chapter Skim
Currently Skimming:
Appendix C: Workshop Proceedings in Brief
Appendix C: Workshop Proceedings in Brief
Pages 56-71
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 56... ...
This workshop was conducted as part of a broader study conducted by the Committee on Air Force Software Sustainment and Maintenance of Weapon Systems that is focused on addressing challenges and identifying oppor unities to effectively design and execute sustainment planning across USAF t systems and platforms. During the workshop, committee members heard from a wide range of subjectmatter experts in software sustainment from government to academia to examine how the USAF can improve planning, implementation, and management of software sustainment and maintenance of weapons systems.
|
From page 57... ...
. The DSB report emphasized that while software sustainment is sometimes perceived as routine maintenance, in reality, sustaining software code involves continuous development because every update is a change to the programming.
|
From page 58... ...
2 Government Accountability Office (GAO) , 2019, "Weapon System Sustainment: DOD Needs to Better Capture and Report Software Sustainment Costs," https://www.gao.gov/products/GAO-19-173, accessed June 2, 2020.
|
From page 59... ...
Wert said that when a software sustainment team does not own the code they are working on, they are primarily charged with integrating code written by other teams. If the contractor misses a necessary element of the software package, 3 Defense AcquisitionsUniversity, 2017, "Updated DoD Acquisition Life Cycle Wall Chart," https:// www.dau.edu/training/career-development/logistics/blog/Updated-DoD-Acquisition-Life-CycleWall-Chart, accessed June 2, 2020.
|
From page 60... ...
asked Wert how he managed the civilian software engineers working on classified programs. Wert re sponded that they have the civilian software engineers use stock photos to train a machine-learning software algorithm, and then classified data is analyzed by USAF personnel with the proper security clearances.
|
From page 61... ...
Discussion with Nick Guertin, SEI Nick Guertin (Senior Software Systems Engineer, Software Engineering Institute [SEI] , Carnegie Mellon University)
|
From page 62... ...
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. The most cyber resistant software system, according to Guertin, is that which has been most recently developed, because it is new and not fully understood by potential adversaries.
|
From page 63... ...
9 FIGURE C.2 Capability evolution and delivery constantly in motion. SOURCE: Nick Guertin, Software Engineering Institute, "Software Sustainment and the Challenge of Modular Capability Innovation," presentation to the workshop, February 28, 2019.
|
From page 64... ...
When Winston asked Gill how the program could apply agile software develop ment 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. A hardware wrapper can have a strong software development component.
|
From page 65... ...
INPUT FROM THE SOFTWARE ENGINEERING GROUPS Work Breakdown Structure Ryan Bishop (76th SWEG, Tinker AFB) led a discussion on the challenge of a work breakdown structure (WBS)
|
From page 66... ...
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 67... ...
When discussing workforce pay grades, Devin Bright (402nd SWEG, Robins AFB) said that government software sustainers are not oing tog match what the commercial technology community can provide.
|
From page 68... ...
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 69... ...
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. Nielsen said that Kessel Run has been highlighted in other reports, such as that by the DSB, so maybe the AFSB committee's consensus study can highlight what is being done at the USAF sustainment centers.
|
From page 70... ...
, 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
|
From page 71... ...
2020. Software Sustainment and Maintenance of Weapons Systems for the United States Air Force: Proceedings of a Workshop -- In Brief.
|
Key Terms
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.