3 ms·
From prior experience working with non-UI statecharts: 1) State transitions are essentially "goto". Structured programming offers abstractions that are easier
by adinisom 9y ago
From prior experience working with non-UI statecharts:
1) State transitions are essentially "goto". Structured programming offers abstractions that are easier to think about and less fragile to requirement change. But in some situations small state machines can be a win.
2) Statecharts offer "structure" in the form of substates and superstates which are much like inheritance in OOP. In my experience these are fragile to requirement change.
3) Statecharts are advertised as being explicit and therefore easier to check for correctness. They can be, although if there are multiple state machines operating concurrently or even an "outside world" acting on them, the set of possible states is no longer explicit.