Using behaviour three notation for behaviour description in Capella in comparison with statechart notation

[kubsztal]

@dsryzhov

After exit action the reason of the leaving is analyzed and on transition actions are executed, and new stated is set.

This will only work in case of no guards.

@dsryzhov

We can see that statemachine representation is much more compact even for one state

What just confirms that trying to replace HSM notation with BTrees makes rather not too much sense If then flowchart < BTree < HSM is true and Capella provides mode/state machines notation, what would be the benefit of having BTrees? Perhaps figures 2.3 and 2.4 in https://arxiv.org/pdf/1709.00084.pdf are the answer here, but I’m not so sure if this HSM couldn’t be designed in a bit more compact way, e.g. ‘choice’ and ‘event guards’ could be used to simplify transitions from all states to all states on given state event, preventing such “spaghetti of transitions”: