News for hackers. Stuff that matters.
Re:Statecharts: A Visual Formalism For Complex Systems (1987... by fsloth on Thursday December 18, 2014 @05:01AM (#8766680)
I started to figure out if I could use statecharts for systems design but then read this critical piece and became less enthusiastic mbreen.com/breenStatecharts.pdf

Could someone with practical experience of them comment of their usability?

Re:Statecharts: A Visual Formalism For Complex Systems (1987... by OliverM on Thursday December 18, 2014 @06:58AM (#8766876)
The paper has some good insights into how statecharts can obscure or confuse solutions, but some of the issues are avoided by experience or practice of using statecharts. Combining orthogonal states and history, for example, is rightly criticised in the paper and is the equivalent of a 'code smell' for me personally, largely because it becomes difficult to reason about the behaviour of the system being modelled. The two main benefits of state charts are the clustering notation and separation of concerns by linking statecharts with directed events (rather than using orthogonality). History is sometimes useful in specific circumstances, though those often arise from how you structured the statechart rather than a system design issue.

In short I'd say to try not using deep history or orthogonality and see how you get on. Use them minimally and rarely in combination. I've found statecharts to be fantastic at clarifying my understanding of systems and their design, but like any tool, they take practice.

Re:Statecharts: A Visual Formalism For Complex Systems (1987... by fsloth on Thursday December 18, 2014 @02:25PM (#8769154)
Thanks for the summary! This does sound a bit more encouraging towards Harel's work