Not just you. What little exposure I've had to UML as a whole suggests that it is more appropriate for projects and systems much larger than what suits my taste. However, it just so happens that UML adopted Harel Statecharts as one of the means for modelling behavior using "extended" state machines. I have always liked FSMs for what they do well and liked Petri Nets for what they do well. Harel Statecharts combine the best of both, but with notation and semantics that simplify the whole mess. It's the statecharts part only of UML that I'm keen on -- nothing else at this point.


Yes, plus statecharts are much better at handling concurrency without the state "explosion" and reduce complexity through event/action inheritance when using state hierarchies.