The Unified Model-Based Design: how not to choose between Scade and Simulink - Archive ouverte HAL Accéder directement au contenu
Communication Dans Un Congrès Année : 2016

The Unified Model-Based Design: how not to choose between Scade and Simulink

Résumé

Software projects using Simulink or Scade use in fact a subset of Simulink or Scade. The 'alignment' of these two subsets gives rise to a new concept, the 'Unified MBD', interesting in two respects: on the academic side, it gives a simple semantics to our subset of Simulink, and on the industrial side, it permits at almost no cost the double-skill Scade/Simulink for software and system engineers. For the data-flow part, the unified subset is simply the 'clockless' part of the Scade/Simulink intersection. For the control-flow part, the unified subset is much more restricted, but the fundamental aspect is that it strictly conforms to a well-known paradigm called 'mode-automatas'.
Fichier principal
Vignette du fichier
paper_25.pdf (1.3 Mo) Télécharger le fichier
Origine : Fichiers produits par l'(les) auteur(s)
Loading...

Dates et versions

hal-01289662 , version 1 (17-03-2016)

Identifiants

  • HAL Id : hal-01289662 , version 1

Citer

Jean-Louis Dufour, Bertrand Corruble, Bertrand Tavernier. The Unified Model-Based Design: how not to choose between Scade and Simulink. 8th European Congress on Embedded Real Time Software and Systems (ERTS 2016), Jan 2016, TOULOUSE, France. ⟨hal-01289662⟩

Collections

ERTS2016
217 Consultations
2577 Téléchargements

Partager

Gmail Facebook X LinkedIn More