The Drive Toward Stability

As software software-intensive systems emerged in the latter half of the 20th century, and matured into ubiquity in the 21st, a number of emerging disruptions to the field have forced those of us concerned with software engineering to adopt new approaches for bringing engineering rigor to software and systems development. These disruptions are of particular concern to the Department of Defense (DoD), which now depends on software to deliver the majority of new capabilities necessary to maintain strategic advantage. As the only federally funded research and development center (FFRDC) focused on software, we share this concern with our sponsors in the DoD. This post will highlight how the SEI has reshaped its research strategy over the past several years to take on emerging disruptions, and how we’ve integrated a number of research threads to multiply our impact.

Software Engineering in an Era of Disruption and Instability

I’ll focus on three disruptions that have had the greatest impact on the DoD and our work here at the SEI. First, we have seen the emergence of communications technology that enables programs to connect directly with one another, demanding an entirely new level of trust. Second, interconnecting systems with multiple intersecting threads of execution have presented new security challenges: there’s no longer a single point of entry and exit to defend, and the complex programs operating in these systems present many more attack surfaces. Third, ultra-large-scale systems are constantly evolving because their component pieces are constantly evolving. Such systems are never static and can never be statically analyzed, allowing for the ever-present the danger of unintended consequences.

All three disruptions present threats to systems that control things in the physical world, and so we must now concern ourselves with dangers such as inadvertent weapons fire, failure of defense systems against an attack, or disinformation that could cause incorrect targeting. Systems that rely on machine learning (ML) can suffer from data poisoning and similar attacks.

The result is an unstable environment that gives rise to effects far more devastating than anything we previously confronted. Our job at the SEI is to address the following questions: How can software engineering help create stability in a world of software disruption? How can software architects design whole systems to be more stable so that there are fewer opportunities for adversaries?

A New SEI Strategy for Tackling Instability: Software Transforming the Mission

In this environment of disruption and instability, the ability of the DoD to produce and evolve software is central to its ability to maintain superiority across domains. Consequently, in 2019, we revised the SEI’s strategy. With our new strategic goal, Software Transforming the Mission, we seek to enable the DoD to realize advantage through software. To achieve this goal, we established four cross-cutting, targeted objectives:

• Automate the software development and DoD acquisition lifecycle to help the DoD produce assured software-enabled systems that are agile and responsive to DoD missions. Examples of this work include
• Automated Continuous Estimation
• Rapid Certifiable Trust
• Automated Design Conformance During Continuous Integration
• Create operational resilience for missions to help the DoD field and operate systems that support DoD missions even when attacked by a capable adversary. Examples of this work include
• Application of Cyber Camouflage Games to Cyber Threat Hunting
• Improving Human Decision Making with AI Decision Support Systems
• AI Robustness
• Certifiable Distributed Runtime Assurance in Cyber-Physical Systems
• Realize artificial intelligence (AI) and future computing to help the DoD ensure it capitalizes on emerging architectures, computing platforms, algorithms, and software-related technologies. Examples of this work include
• Developing the Discipline of AI Engineering
• Resource-Constrained Co-Optimization for High-Performance, Data-Intensive Computing
• Developing Trustworthy AI Systems
• Explainable AI
• Quantum Computing
• Integrate the preceding objectives into mission-capable systems. Examples include
• DevSecOps for AI Engineering
• ML in Cybersecurity
• Enabling Rapid Software Architecture Evolution
• Human-Centered AI

The first objective optimizes the development and acquisition lifecycle that produces software-enabled systems. The second objective ensures that software-enabled systems developed in objective one are resilient once fielded and informs the development and acquisition of future systems based on field experience. The third objective develops and identifies promising software technologies that could be used in the future by objectives one and two. The fourth objective addresses how we pull technical work threads together to improve technologies and development paradigms for systems today and in the future.

Three years after our strategy adjustment, these self-reinforcing objectives have begun to provide the DoD capable, timely, trustworthy, and affordable software.

Introducing Research Results Through Innovative Practices

To achieve these objectives, we close the loop between research and practice. The SEI facilitates the transition of research results to practice in DoD programs and OSD Science & Technology (S&T) initiatives and the transfer of those results to non-DoD U.S. government organizations where improvements will also benefit the DoD. By doing so, we gain deeper insight into mission needs that forms the basis for new research. In addition, we transition matured technologies more broadly to Defense Industrial Base organizations and others in the DoD software supply chain. Figure 1 highlights our primary technical activities: applied research and development (AR&D), engagement in the field, and transition.