M. Romdhani

Multilanguage design of heterogeneous systems

Multilanguage solutions are required for the design of heterogeneous systems where different parts belong to different application classes, e.g. control/data or continuous/discrete. The main problem that needs to be solved when dealing with multilanguage design is the refinement of communication between heterogeneous subsystems. This paper discusses the basic concepts of multilanguage design and introduces MUSIC a multilanguage design approach. The paper also shows the application of this approach in the case of a mechatronic system.

MCI—multilanguage distributed co-simulation tool

Nowadays the design of complex systems requires the cooperation of several teams belonging to different cultures and using different languages. It is necessary to dispose of new design and verification methods to handle multilanguage approaches. This paper presents a multilanguage co-simulation tool that allows co-simulation of multilanguage specifications for complex systems. The main idea of our approach is to allow validation of the functional completeness of the system at a behavioral level. MCI starts with a configuration file that describes the interconnection between modules written in different languages. It generates automatically a software co-simulation bus and the interfaces required to connect the different simulators in a distributed way. The proposed tool is used to assist the design of an adaptive speed control system that was described in three different languages (VHDL, SDL and MatLab).

Languages for System-Level Specification and Design

Chapter 6 introduced concepts and abstract models for designing at the system level. This chapter discusses concrete specification languages and intermediate models used for transforming such system-level designs into realizations.

Multilanguage specification for system design

This chapter discusses specification languages and intermediate models used for system-level design. Languages are used during one of the most important steps of system design: the specification of the system to be designed. A plethora of specification languages exists. Each claims superiority but excels only within a restricted application domain. Selecting a language is generally a trade off between several criteria such as the expressive power of the language, the automation capabilities provided by the model underlying the language and the availability of tools and methods supporting the language. Additionally, for some applications, several languages need to be used for the specification of different modules of the same design. Multilanguage solutions are required for the design of heterogeneous systems where different parts belong to different application classes e.g. control/data or continuous/discrete.

Evaluation and composition of specification languages, an industrial point of view

This paper deals with experience with specification languages at AEROSPATIALE Aircraft, Systems and Avionics Division. We describe first the current avionics development environment. Then, we present our results and viewpoints on the use of the three specification languages: LOTOS, ESTEREL, and B. The evaluation studies we performed, showed that each of these languages does not cover in a complete way our needs in specification, validation, and development of avionics. Afterwards, we propose and illustrate an investigation approach that allows to structure and compose different formal specification languages in the same environment.

Modeling and rapid prototyping of avionics using STATEMATE

The paper presents a methodology and an experiment for rapid avionics prototyping using the STATEMATE environment. The methodology is based on SA-RT structured analysis principles. It shows first the context of STATEMATE use in the current avionics development process. Therefore, it sets up some key steps and use recommendations in order to enhance the modeling quality The experiment deals with the re-design of all existing avionics system that is part of the AIRBUS A340 on-board systems family. It highlights the STATEMATE modeling, validation and rapid prototyping facilities. Results and perspectives are also outlined.

Co-specification for co-design in the development of avionics systems

Abstract Hardware-software concurrent design, referred to as “co-design”, is a new methodology that integrates the development of both hardware and software. It is made up mainly by the steps of specification, partitioning, and prototyping. This paper addresses the specification step. It proposes a specification paradigm based on the use of more than one single language. This approach is referred to as “co-specification”. It deals with formalizing the requirements through several partial specifications. These are therefore composed in a unified model that is used for later co-design steps. The approach is illustrated through the specification of an avionics system that is part of the Airbus A340 on-board systems family.

Composing ActivityCharts/StateCharts, SDL and SAO specifications for codesign in avionics

This paper deals with the composition of system-level specifications, and more generally a multi-formalisms codesign methodology in the context of AEROSPATIALE Aircraft avionics systems. The methodology is based on a unified system model, named SOLAR, which is used to compose three specification languages: ActivityCharts/StateCharts, SDL, and SAO. The model serves the rest of codesign tasks. Multi-formalisms composition principles are illustrated on an avionics system that is part of AIRBUS A340 on-board systems family. Results and perspectives are also outlined.

Hardware/Software co-design

Co-design is an important step during rapid system prototyping. Starting from a system-level specification, Co-design produces a heterogeneous architecture composed of software, hardware, and communication modules. This paper gives a taxonomy of co-design starting from a system-level specification and producing a heterogeneous architecture including the descriptions of hardware and software. Co-design is generally decomposed into four refinement steps: system-level specification, system-level partitioning, communication synthesis, and architecture generation. However, the co-design process depends on the kind of input language (synchronous/asynchronous, single thread/multi-thread) and the target architecture (mono-processor/multi-processor). The main co-design concepts are also detailed through the presentation of a co-design tool called COSMOS

Co-Specifications for Co-Design in Avionics Systems Development

Abstract Hardware-software concurrent design, referred to as co-design, is a new methodology that integrates both the development of hardware and software. It is made up mainly by the steps of specification, partitioning, and prototyping. This paper issues the step of specification. We propose a specification paradigm based on the use of more than one single language. This approach is referred to as co-specifications. It deals with formalizing the requirements through several partial specifications. These are therefore composed in a unified model that is used for later co-design steps. We illustrate the approach through the specification of an avionics system that is part of the AIRBUS A340 on-board systems family.