Filter
Top Products
HONEYWELL Aerospace Electronic Systems Page 15
Use or disclosure of information on this page is subject to the restrictions on the title page of this document.
through an automated code generation system specific to the target environment. Automated test scripts
are also derived from the model database. (See Figure 6).
The software architecture was developed to isolate target-specific components from the core software
components. The combination of the model-based approach and isolating target-specific components
allowed Honeywell to develop a Communications Management Function (CMF) that can be readily hosted
on other hardware targets including the Honeywell integrated platforms VIA and Epic (and in the future B-777
AIMs). This common communications function allows Honeywell to maintain a single communications
baseline across platforms, ensuring consistent implementations. This is beneficial to an airline that may
have a mixed fleet containing both federated and integrated architecture aircraft. A prime example is the
Embraer regional jet family. The Honeywell standalone Mark III CMU has been selected by many airlines for
their ERJ-135 and ERJ-145 aircraft. The next generation ERJ-170 and ERJ-190 contain the Primus Epic
integrated avionics cockpit which includes the CMF. Although the Mark III CMU and the Primus Epic are
different hardware platforms, the same core CMF capability exists on both platforms.
Figure 6 Communication Management Function (CMF) for Both Federated and Integrated
Platforms
Another driving goal of the software architecture was to provide as flexible a system as possible by utilizing
a database-driven design. This design approach allows quick and easy changes to the Mark III CMU without
modifying the embedded operational software. (See Figure 7).
Mark III
VIA
Epic
CMF
Target-specific