Figure 1 below shows the basis for the F-16 Mission Software architecture; it depicts the main architectural elements:

• Software that is unique to the application(s) for which the embedded computer exists, it represents some 80-90% of the total software (in terms of long-term development cost)


• Application Software Interface, the boundary between the Application Software and the Software Execution Platform. This provides the methods by which the Application Software can make requests and use the services of the Software Execution Platform and the Software Execution Platform can provide its services to the Application Software


• Software Execution Platform, low-level software, the purpose of which is to allow the Application Software to run on the hardware; The software execution platform incorporates device drivers, the built-in test and the RTOS.


• Hardware, the embedded system hardware for the F-16 Mission Management system.

The software execution platform effectively raises the abstraction level of the hardware to provide a platform on which code generated from Executable UML models can run directly. Lockheed Martin's goal of complete cross-platform compatibility implies a very strong form of platform independence whereby the UML models which specify the Application software behaviour can be ported without change even if the Application Software Interface changes.