Integrating SysML with Simulation Environments (Simulink) by Model Transformation Approach

System-level co-simulation for embedded systems

“…Chabibi et al 33 attempted to generate the Simulink model from a conceptual level described by SysML based on model transformations and metamodeling. This method did not support the simulation of a multi-level model like in our case.…”

“…Dehghanimohammadabadi et al, 9 Discrete-event/continuous SIMIO/Matlab Manufacturing systems Integration Liang et al, 27 Discrete-event/continuous Arena/Matlab Manufacturing systems Integration Sanz et al, 28 Discrete-event/continuous Arena/Siman and Modelica Queuing systems Integration Süß et al, 29 Discrete-event/continuous PLCOpenXML, Modelica, Manufacturing systems Co-simulation and Matlab Barbieri et al, 30 Discrete-event/continuous Matlab, FlexSim, SysML, Mechatronics system Co-simulation IndustrialPhysics, and PLC Chabibi et al, 33 Discrete-event/continuous Simulink/SysML Queuing system Integration Lora et al, 35 Discrete-event Custom C/C++ Embedded system Integration Edward et al, 36 Discrete-event/continuous CyPhySim/Ptolemy II Cyber-physical system Commune Ben Ayed et al, 37 Discrete-event/continuous SystemC/Matlab/ Mechatronics system Co-simulation HW accelerator Törngren et al, 38 Discrete-event/continuous . .…”

Bridging proprietary modelling and open-source model management tools: the case of PTC Integrity Modeller and Epsilon

“…Five configurations were used in total: (1) Visual Basic, (2) EVL and the Epsilon-IM driver without caching, (3) with both caches enabled and finally (4,5) two experiments with only one of the two caches enabled each time. The constraints were executed three times on each model, and the execution time was logged for each iteration.…”

“…When import/export facilities into exchange modelling formats are missing from a modelling tool, developers rely on any available API that could be used to bridge the tool with others. As in our case study, transformations from SysML to Simulink models have motivated several research works such as [5,22,27]. Those three papers have used model-totext transformation that produce MATLAB scripts which are used to create and populate Simulink models from SysML.…”

“…In addition, [27] proposes a way back from Simulink into SysML through a MATLAB script that parses the Simulink model and produces an XML model description file that can be parsed by the SysML tool. Further differences in their approaches are that [22] generates several MATLAB scripts that populate different parts of the Simulink model, while [5] proposes a UML profile to annotate the SysML diagrams before the MATLAB code generation. In contrast, our case study used a direct model-to-model transformation that involved three heterogeneous models: IM, Simulink and Excel.…”