Search Results

Cockpit Display System (CDS) suppliers need to now prepare for the cockpits of the future. The architecture, design and ergonomics of the cockpits have to be re-assessed in order to place the pilot at the center of the system, while taking into account the increasing complexity of the systems. Human Machine Interfaces (HMI) have to be simplified and made more intuitive. Thus, there is a need for dedicated HMI design tools and human-factor-oriented processes that are able to support both the required flexibility in the display creation for various types of interactive displays and the increasing demand for safety in avionics displays. This paper presents a COTS approach to these needs, which combines the SCADE Display model-based HMI software design solution, designed from the ground up for displays with safety objectives, with an associated prototyping and development process largely based upon human factors assessment.

Embraer began development of an ARINC 661-compliant cockpit display system with Esterel Technologies SCADE Solutions for ARINC 661 Applications. Over the past two years, Embraer has been able to build a fully-functional ARINC 661 demonstrator that includes all components necessary for CDS deployment under the ARINC 661 standard. The ARINC 661 demonstrator includes a fully-compliant ARINC 661 server based originally on Esterel Technologies SCADE 661 Server Creator using an automatic server generator. Embraer had successfully integrated a custom ARINC 661-4, widgets library, with Esterel Technologies widget library, designed with SCADE as the base. Embraer has also developed and integrated User Applications running on a IMA hardware system and communicating with the server using UDP over AFDX within a flight simulator system. This paper discuss the process followed by Embraer for development of the ARINC 661 demonstrator.

The increasing complexity of distributed embedded systems, as found today in airplanes or cars, becomes more and more a critical cost-factor for their development. Model-based approaches have recently demonstrated their potential for both improving and accelerating (software) development processes. Therefore, in the project DECOS1, which aims at improving system architectures and development of distributed safety-critical embedded systems, an integrated, model-driven tool-chain is established, accompanying the system development process from design to deployment. This paper gives an overview of this tool-chain and outlines important design decisions and features.

The ARINC 661 standard [1] defines a Cockpit Display System (CDS) interface intended for all types of aircrafts installations. This paper presents an integrated solution based on Commercial Off-The-Shelf (COTS) tools that allows, in the initial stage of an aircraft project, support for the expression of requirements with regards to the CDS definition and the CDS interaction with the User Applications (UAs). It also enables prototyping of the systems architecture from the point of view of functionalities and performance. At a later stage of the project, this same integrated tool suite can be used to produce and certify the final embedded software code within the CDS and to generate the communication code between the CDS and the UAs.

This paper presents the SCADE System™ product line for systems modeling and generation based on the SysML standard and the Eclipse Papyrus open source technology. SCADE System has been developed in the framework of Listerel, a joint laboratory of Esterel Technologies, provider of the SCADE® tools, and CEA LIST, project leader of the Eclipse component, Papyrus. From an architecture point of view, the Esterel SCADE tools are built on top of the SCADE platform which includes both SCADE Suite®, a model-based development environment dedicated to critical software, and SCADE System enabling model-based system engineering. SCADE System includes Papyrus, an open source component (under EPL license), integrated in the modeling platform of Eclipse. Using this integrated modeling platform, both system and software teams share the same environment for system development. Furthermore, other model-based tools can be added to the environment, due to the use of Eclipse.