SCADE or Simulink importers

The functional importers create AADL models skeletons using a functional model such as SCADE or Simulink. SCADE or Simulink provides a language to describe a functional description using a graphical notation. However, these models do not show many deployment information, which may result in limited analysis.

Such models are often used to simulate and prototype the system before architecture design efforts. For that purpose, import these functional models can help to make the initial models by automatically generating a model skeleton from existing prototyping efforts. The model skeleton can then be refine according to the design specification.

Using the plug-in

In both case, before selecting the menu, you have to select an empty directory in your OSATE installation (see picture below). This directory will then contain the generated AADL model. Then, the tool will ask to select the Simulink or SCADE model to import.

Importing Simulink Models

To import a Simulink model, make sure you have selected an empty directory in your workspace and then, select the menu entry Import Simulink model under the Analyses menu. This is shown in the figure below in the purple box. Please note that the importer support only Simulink models saved under the slx format.

Importing SCADE Models

To import a SCADE model, make sure you have selected an empty directory in your workspace and then, select the menu entry Import SCADE model under the Analyses menu. This is shown in the figure below in the red box.

Mapping Rules

The following sections provide an overview of the mapping rules to transform a Simulink or SCADE model into an AADL model

For both importers, the tool will create the following files:

  1. functional/-functional.aadl contains a functional view using abstract components.
  2. functional/-runtime.aadl contains the system structure (with subcomponents) using system components.
  3. functional/runtime_generic.aadl contains generic components used by all mapped components.

Simulink Mapping Rules

SCADE Mapping Rules

It is possible to import a single component (.xscade file) or a complete project (.etp file).

Common Problems

Bug report

If you have any question or would like to report a bug, please do it on the OSATE plug-in issue tracker on github. You can also ask questions on the AADL mailing-lists.