[prodigal_erik]

I have seen class and sequence diagrams used on a few occasions. The others, never. My teams at Microsoft years ago were getting into statecharts (state machines made clearer with a few extra features, e.g., events which happen on any transition between groups of states) but not the UML notation for them that has apparently popped up. I have the impression these are more common in consulting shops which charge by the hour for reams of waterfall design docs which only roughly describe the actual software written as an afterthought. Even though the way we typically improvise software design is blatantly stupid, this stuff doesn't seem to be the solution.