FACE: Interfaces for portable avionics software
Part of the Open Architecture Field Guide.
The Future Airborne Capability Environment (FACE) Technical Standard defines software segments and interfaces for avionics reuse. It separates portable application logic from services tied to its computing platform.
In this guide
Why moving software involves more than copying its code
An avionics application depends on the computer around it. It obtains data from devices, uses operating-system services, and exchanges information with other software. If those dependencies are mixed throughout its processing logic, moving the application to a new computer requires understanding and changing each platform-specific connection.
Software portability concerns the amount of application work that can be reused when the host changes. The Future Airborne Capability Environment (FACE) Technical Standard addresses that problem by organizing software into segments with defined interfaces. This places the application's portable logic on one side of a boundary and services associated with its environment on the other. [1]
Consider an application that receives navigation measurements and calculates a displayed quantity. Its calculation may remain useful across aircraft. The method used to obtain a measurement from a particular device, however, can vary with the computer, operating system, and equipment installation. A portable design makes the calculation depend on a defined service or data interface rather than scattering device access through the calculation itself.
The responsibilities behind the segment boundaries
The Portable Components Segment contains application logic intended for reuse. The surrounding segments account for the services that allow that logic to run and communicate. The Operating System Segment supplies the underlying execution environment, while the I/O Services Segment handles input and output associated with devices. [1]
The Platform-Specific Services Segment provides services whose implementation depends on the platform. The Transport Services Segment supports exchanges of data between software components. These segments organize responsibilities so that a change in one part of the environment has an identifiable interface through which it affects the application.
For the navigation example, the architecture separates the calculation from the work required to obtain, represent, and deliver its inputs. The application developer can describe the data and services the calculation needs. The platform team can then supply those interfaces through the software appropriate to its host.
Scroll horizontally to inspect the diagram.
The figure shows responsibilities, rather than a required sequence in which every observation passes through every segment. An actual application uses the interfaces relevant to its function. Understanding which services it calls is the starting point for assessing its dependencies.
Planning the move to another computer
When the application moves, the receiving team examines those dependencies against the new host environment. The computational logic can be retained where the required interfaces and data meanings are preserved. Services tied to the original equipment can be implemented for the new platform at the corresponding boundary.
The selected FACE profile helps define that environment. A profile is a set of requirements and permitted interfaces appropriate to a particular context, including general-purpose, safety, or security applications. The standard edition and profile identify the rules under which the component was developed and assessed. [1]
Conformance evidence then records whether the implementation meets the selected requirements. Combined with its data definitions and required services, that evidence gives the receiving team a basis for integration. Tests can focus on the actual inputs, outputs, and host interactions through which the application performs its function.
Connecting portable software to mission functions
The software's host dependencies are only one view of its role. The surrounding aircraft also needs to know what information it produces and how other mission functions use it. Open Mission Systems (OMS) addresses mission-system integration, and the Universal Command and Control Interface (UCI) provides a common model for mission messages. [2]
An application can therefore be organized using FACE interfaces while participating in an OMS-based mission system. FACE helps describe how its logic is hosted; OMS and UCI help describe its exchanges with the wider system. In the navigation example, these views connect the reusable calculation to the computer that executes it and the consumers that use its result.
References
- The Open Group, FACE Technical Standard and approach.
- OACWG / AFLCMC, Open Mission Systems Standard v2.5: Definition and documentation set.