Decoding the Architecture of Modern Fighter Aircraft Software
The software powering a modern fighter jet isn’t a single, monolithic program. Instead, it’s a complex ecosystem built on layers of abstraction. This hierarchical approach, known as a layered architecture, allows engineers to separate different functions, ensuring that a change in one area doesn’t crash the entire system. From the flight controls to the mission systems, this design is what enables the agility and reliability required in high-stakes aerial combat.
The Shift to Integrated Modular Avionics (IMA)
Traditionally, aircraft used federated architectures, where each function had its own dedicated hardware. Modern jets have moved toward Integrated Modular Avionics (IMA). IMA is a real-time computer network airborne system consisting of computing modules that support multiple applications with varying levels of criticality.
Unlike older systems, the IMA concept uses an integrated architecture where application software is portable across a set of common hardware modules. This shift has been central to the design of fourth-generation jet fighters, including the F-22, F-35, and the Dassault Rafale, since the beginning of the 1990s.
How Layered Architecture Simplifies Development
By dividing software into layers, developers can isolate the application layer from the underlying hardware. This structure provides several critical advantages:
- Simplified Integration: Because the module network is unified, it’s mandatory to use a common API to access network and hardware resources. This streamlines the integration of hardware and software.
- Reduced Risk: Application developers can focus solely on the application layer, which reduces the chance of faults occurring in the lower-level software layers.
- Easier Maintenance: Since modules share much of their hardware and lower-level software architecture, maintaining them is simpler than with previous, aircraft-specific architectures.
- Increased Availability: If a primary module fails during operation, applications can be reconfigured on spare modules, keeping essential avionics functions online.
Communication within these systems occurs via high-speed internal computer buses or external networks, such as ARINC 429 or ARINC 664 (part 7).
The FACE Reference Architecture and Portability
To further increase flexibility, the military is adopting the Future Airborne Capability Environment (FACE) reference architecture. FACE is a layered software architecture designed specifically to allow any software component to be replaced rapidly as needed.
The goal of the FACE architecture is to make software more portable and reusable across different military aircraft. By implementing a standardized layer, it allows various software applications to function regardless of the specific platform they are deployed on, reducing the time and cost associated with upgrading military avionics.
Standards and Safety Certification
Ensuring a fighter jet is airworthy requires rigorous safety certification. While military avionics previously relied on a variety of standards like MIL-STD-882 and MIL-STD-516, there’s a clear transition toward the DO-178C standard.
The move to DO-178C, supported by the FACE Consortium, aims to reduce costs and risks while increasing the quality and deployment speed of new airborne technologies. Other critical standards used in IMA environments include ARINC 653 and DO-297, which define roles and responsibilities for delivering software into these integrated systems.
Key Takeaways: Modern Avionics Architecture
- IMA vs. Federated: Modern jets use Integrated Modular Avionics to share hardware across multiple applications, replacing the classic “one box, one function” federated model.
- Portability: Standards like FACE enable software to be reused across different aircraft, avoiding the demand to rewrite code for every new platform.
- Reliability: Layered design allows for “spare” modules, meaning the plane can reroute critical functions if a hardware module fails mid-flight.
- Certification: The industry is consolidating around the DO-178C standard to streamline safety certifications and reduce deployment timelines.
As military aviation continues to evolve, the focus remains on creating open, modular systems. By decoupling software from hardware, the next generation of fighter aircraft will be able to update their capabilities via software patches rather than costly and time-consuming hardware overhauls.
Keep reading