Typically state machines generated from YAKINDU SCT state charts are used as black boxes. The code that embeds the state machines does not care about the internal execution of the state machine. But there are various use cases where information about internal execution events, especially state changes, must be observed. These kind of execution traces can be implemented manually by adding entry and exit actions that call operations or set variables. But this is very cumbersome and pollutes the statecharts with tracing code. Since version 2.6 the C code generator supports an option to enable tracing callbacks.

We proudly present the first version of YAKINDU Statechart Tools Pro Edition for beta testing. This edition includes everything that you may know from the Open Edition and adds a set of features that you will find very helpful for embedded systems development. This first beta version ...

Do you use Simulink® and Stateflow® from MathWorks? These tools are powerful and often a central part in the engineering tool chain. Models and block libraries created with them carry valuable engineering knowledge of your development team and organization. The more important the models are the more people use them as a source of information for their everyday work. Reflecting the development process, there are many usage scenarios that need access to the models but are not about editing and simulating models. This is typical in testing scenarios but can also be found within implementation tasks. For these scenarios, viewer for models and libraries would be sufficient. So what are the pros and cons of using Simulink and Stateflow viewers?