Air Force Software Sustainment and Maintenance of Weapons Systems (2020) / Chapter Skim
Currently Skimming:
2 Current State of USAF Software Sustainment
2 Current State of USAF Software Sustainment
Pages 12-27
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 12... ...
While the USAF is taking active measures to address the current sustainment workload, the ability to keep pace in the future will not be possible unless the USAF updates its software sustainment enterprise. The USAF has an active and committed effort to sustain its software.
|
From page 13... ...
While different SWEG teams had tensions with contractor groups depending on how different programs were run, contractors still play a critical role in providing expertise and support to USAF software sustain ment processes. From several presentations, USAF software engineers demonstrated a com mand of modern software engineering approaches and how to apply these in a judicious manner.
|
From page 14... ...
That said, multiple individuals stated that ALC management's breadth in scope limits the USAF's ability to accommodate the specific challenges of manag ing software engineering personnel, facilities, and business practices. For example, software sustainment personnel are being treated like hardware and maintenance engineers.
|
From page 15... ...
For one of the older aircraft programs (F-22) , Hill AFB staff commented that there was no one at the SPO with whom to discuss software sustainment.
|
From page 16... ...
The SWEGs participate in a broad range of software projects, from those using modern cloud technologies and DevSecOps programming to those developing code using obsolete computer programming languages, such as Jovial and Ada, to support 25-year-old microprocessors. In addition, the USAF continues to sustain important code for outdated operating systems, such as Microsoft Windows XP and Solaris.
|
From page 17... ...
Recruiting software engineering expertise into the SPO is a challenge, which is typically not seen as a viable career for software engineers. The lack of technical talent at the SPOs is a chronic and profound problem for both acquisition and sustainment, reducing the ability of the USAF to make appropriate trade-offs between software and non-software related activities.
|
From page 18... ...
In both cases, the nature of the work to be performed is fundamentally identical -- the delivery of an improved software configuration item capable of delivering improved functionality, while addressing evolved requirements and an evolved target-operating environment. Although the fundamental technical nature of software development for sustainment versus acquisition is essentially the same, the USAF has histori cally faced challenges managing the transition from the presystems and system acquisition phases into the sustainment phase.
|
From page 19... ...
Many of the new steps are vectored in the right direction, but this type of staff management needed to be established 5-10 years ago.8 In addition, F-22 sustainment faces challenges of lack of access to source code that inhibits USAF ability to perform system testing and debugging. This issue is linked directly with the data rights issue, which will be discussed in subsequent sections.
|
From page 20... ...
Finding 3: The USAF distinguishes between software development and soft ware sustainment. Conclusion 3: As the USAF looks to the future, the current arbitrary approach to separating software acquisition and sustainment will continue to create systemic barriers that severely inhibit a pathway toward continual and vital improvement.
|
From page 21... ...
The issue of ownership of the technical baseline is a much more contentious and critical issue. For software, the key issue is ownership or use of the data rights for source code, software design tools, technical documentation, interface descrip tions, and so on.
|
From page 22... ...
Given the need to sup port rapid software development and overall shortages of software development staff, robust government-contractor relationships are key for rapid and efficient software sustainment for the USAF. DATA RIGHTS OWNERSHIP AND USAGE AGREEMENTS Software "data rights" refer to the government's licensing rights to use and modify contractor software.
|
From page 23... ...
Finding 5: Data rights for software is a critical issue that either enables or restricts the USAF's and government's ability to rapidly adapt and enhance platform software. Conclusion 5: Addressing data rights for existing and new systems will require sufficient expertise in software engineering, contracting, and intellectual prop erty working as an articulated team, which is currently beyond the capabilities within the USAF software sustainment community.
|
From page 24... ...
Last, government staff at the SWEGs lack the tools and experience to adapt cloud, agile, and DevSecOps environments to current USAF security requirements. Software assurance (SA)
|
From page 25... ...
INFRASTRUCTURE REPRESENTING CHALLENGES FOR USAF SOFTWARE SUSTAINMENT One of the more surprising challenges facing the SWEGs were shortages and restrictions on facilities, networking, and IT support. The three SWEG facilities support a range of office space for software development and SILs.
|
From page 26... ...
Finding 7: Poor network and IT performance is having an impact on USAF software sustainment staff effectiveness, morale, and retention. SOFTWARE ENGINEERING PERSONNEL NOT TREATED AS A STRATEGIC ASSET USAF staffing levels supporting software sustainment has steadily grown over the past 10 years (Figure 2.3)
|
From page 27... ...
. The 76th SWEG is at Tinker AFB; the 402nd is at Robins AFB; and the 309th is at Hill AFB.
|
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.