# System modeling workflow example

**URL:** <https://discourse.julialang.org/t/system-modeling-workflow-example/67612>\
**Category:** Modelling & Simulations\
**Tags:** examples, workflow, modelingtoolkit\
**Created:** [September 3, 2021, 1:05am UTC](https://discourse.julialang.org/t/system-modeling-workflow-example/67612 "2021-09-03T01:05:38Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![zdenek\_hurak](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/zdenek_hurak/32/53118_2.png) [@zdenek\_hurak](https://discourse.julialang.org/u/zdenek_hurak)\
**Post date:** [September 3, 2021, 9:15am UTC](https://discourse.julialang.org/t/system-modeling-workflow-example/67612/3 "2021-09-03T09:15:05Z")

</div>

Let me state, that coming from Simulink, you should be aware of a complete change of the modeling approach. The modeling approach followed by Simulink is called _causal_ (also _assignment-based_). Simulink actually models _signal flows_ (every block in the Simulink _block diagram_ produces an output signal in response to an input signal). On the other hand, ModelingToolkit follows (similarly as (Open)Modelica and Modelica-inspired Julia package [Modia](https://youtu.be/N94si3rOl1g)) the so-called _acausal_ (also _equation-based_) approach, where you do not have to classify the signals/variables as inputs or outputs. This turns out very useful for modeling complex interconnected systems. Well, for a couple of years even Simulink users can enjoy the latter modeling approach through the the extension library called [Simscape](https://www.mathworks.com/products/simscape.html). Besides possible ModelingToolkit examples and tutorials, some intro to (Open)Modelica or Modia can make your transition easier, because it is really a transion from one mental framework to another rather than just a switch from one software to another.

---

_[View the full topic](https://discourse.julialang.org/t/system-modeling-workflow-example/67612)._