Software Defined Defence (SDD)

Upgradable, networked, and modular defense systems

Software-Defined Defense (SDD) applies the principle of software-defined systems to the defense sector. The goal is to develop or further develop military systems—such as vehicles, aircraft, ships, satellites, and cyber defense systems—in a way that allows new functions, security updates, and software-based capabilities to be integrated efficiently.

For nearly two decades, Fraunhofer IESE has been supporting the German Armed Forces and the defense industry in matters related to systems and software engineering.

Why is Software-Defined Defense relevant?

In modern defense systems, an increasing portion of functionality is provided by software. This includes, among other things:

System Integration
Integration of New Software Features
Faster adaptation to new requirements
Closing Skills Gaps
Use of Modular and Interoperable Components

SDD thus lays the foundation for not only defining systems at the time of commissioning, but also for continuing to develop them throughout their lifecycle.

How does a software-defined architecture work?

At its core is updatability. It enables:

Upgrading Existing and Legacy Systems
Continuous software updates
Enabling New Features
Prompt resolution of security vulnerabilities
Greater software portability across different platforms

A key goal is the decoupling of hardware and software. This allows features to be developed more flexibly without every change requiring a major overhaul of the hardware architecture.

In addition, SDD requires processes that enable updates to be deployed efficiently—ideally with minimal maintenance, clear dependencies, and a controlled, secure rollout.

Difference from Conventional Technology

Traditional, tightly coupled architecture	Software-Defined Architecture
The hardware and software are closely integrated	Hardware and software are becoming more decoupled
Changes are often time-consuming and tedious	Software can be customized and expanded more quickly
Updates pose significant risks in terms of dependencies and side effects	Modularity reduces dependencies and makes it easier to make changes
It is difficult to retrofit existing systems	Legacy systems can be modernized in a targeted manner
Interoperability is often limited by proprietary interfaces	Open and standardized interfaces promote collaboration

Traditional safety-critical systems were often not designed with the goal of updating software regularly and efficiently. This makes modifications more difficult, increases the effort required for certification, and limits the ability to respond to new technical or operational requirements.

What are the components of Software-Defined Defense?

SDD is not a single technology. It is an interplay of technology, governance, and procurement processes.

Technology

A software-defined architecture begins at the hardware abstraction layer and extends all the way to the ability to integrate third-party software into the system. The key factors are:

Modular software architectures that promote component-based software development, rather than a monolithic structure
Portable applications to ensure platform independence
Secure and maintainable interfaces
A reliable IT infrastructure foundation for updateability and connectivity

In this context, Fraunhofer IESE describes, among other things, the role of microkernel architectures and lightweight containerization for software-defined systems.

Governance and Standards

Efficiency and interoperability result not only from technology, but also from shared models, terminology, and interfaces. Relevant references include, among others:

NAF 4.0
ADMBw
SOSA
FACE
NGVA
WOSA

These standards and initiatives support the description, development, and interoperability of military systems. Fraunhofer IESE explicitly addresses NAF and ADMBw in the context of training and architecture.

Procurement Processes

Procurement must also take software-defined systems into account. A key reference point is MOSA. The goal is to incorporate modularity, open interfaces, and lifecycle management into the procurement process from the outset.

This is particularly relevant when components from different manufacturers need to be integrated into a single system.

What is the difference between SDD and Multi-Domain Operations (MDO)?

Multi-Domain Operations (MDO) refers to a deployment and operations concept that spans multiple domains, such as:

Land
Air
Sea
Space
Cyber and Information Domain

Software-Defined Defense (SDD), on the other hand, is the technological and infrastructural approach that effectively enables this connectivity, adaptability, and interoperability in the first place.

Kurz gesagt:

MDO describes operational collaboration across domains.
SDD provides the software and system-level foundation for this.

The German Armed Forces explicitly emphasize the connection between software-based adaptability, interoperability, and multi-domain operations.

Your Point of Contact for Software-Defined Defense

Are you looking to integrate Software-Defined Defense into your product development or to gradually enhance existing systems?

Fraunhofer IESE has been supporting organizations in the military sector for many years in the areas of software engineering, systems engineering, architecture, modularity, and interoperability.

The institute is also part of the Fraunhofer Defense, Prevention, and Security Division.