Search Results

Multiple model-based engineering (MBE) frameworks have emerged to cover the many requirements for the engineering of avionics systems: from early requirement capture to the final system and embedded software generation, through refinement and V&V activities. In this paper, we consider the SysML, AADL and FACE standards. They are promoted by different standardization bodies, with different objectives. We note they are often seen as competitive, while we argue it is the opposite: there is a potential for a synergistic coupling. To date, no complete open evaluation on the feasibility of such capability has been done. In this paper, we present one workflow that illustrates the joint use of SysML, AADL and FACE. We consider a basic flight control system to exercise the proposed process and gateways between the three notations.

This paper introduces a model-based systems and embedded software engineering, workflow for the design of control systems. The interdisciplinary approach that is presented relies on an integrated set of tools that addresses the needs of various engineering groups, including system architecture, design, and validation. For each of these groups, a set of best practices has been established and targeted tools are proposed and integrated in a unique platform, thus allowing efficient communication between the various groups. In the initial stages of system design, including functional and architectural design, a SysML-based approach is proposed. This solution is the basis to develop systems that have to obey both functional and certification standards such as ARINC 653 (IMA) and ARP 4754A. Detailed system design typically requires modeling and simulation of each individual physical component of the system by various engineering groups (mechanical, electrical, etc.).

Avionics systems are complex systems that integrate hardware, communication media, have many interactions with other subsystems, within or outside of the aircraft, and for the system discussed in this presentation, integrate software that must be developed according to DO-178B guidelines. System engineering and software engineering are two engineering disciplines that are historically handled by teams with different cultures, and when their engineering processes are supported by tools, use different and incompatible tools. This often leads to a difficult collaboration, with at some point, redundant information and inconsistencies. This presentation introduces a solution, based on the SysML standard for system modeling, and on the SCADE Suite product from Esterel Technologies for the development of DO-178B certified software components.

This presentation shows 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�, 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.

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.