Comment by lucamark

First, thanks for the questions. Initially it can look like other model based design tools (like Simulink as you mentioned) but actually it is a vertical solution to deploy the algorithms into your embedded system.

Particularly, Modeloop allows developers to iterate on the design and test the solutions before putting on actual hardware.

In Modeloop there are basically two phases: 1) Mathematical verification: developers can insert contracts on the signals on the model design. These contracts specify the maximum and minimum range allowed for each variable. In the code generation phase, they are used to check that are no mathematical inconsistencies in the model. For example, code generation fails if you try to multiply inputs A ∈ [0,10] and B ∈ [0,20] and asserts C (C = A × B) ∈ [0,100]. 2) Testing: developers can not only perform model simulation with defined input profiles, but also they can make unit tests on subsystems - a container of different blocks . This makes the testing phase extremely rigorous.