(Disclaimer: I&#x27;m not UML&#x2F;architect expert)<p>I get your opinion from a programmer point of view. However from the big picture point of view, either from the architect or from the client (if she (even partially) gets UML), it could be really useful.<p>E.g. let&#x27;s consider working for a large financial institute, designing and&#x2F;or implementing very difficult workflows &#x2F; algorithms what would you use instead? In my experience most of the clients don&#x27;t take the time to read half (if at all) of the agreed spec, not to mention understanding. In that case an activity&#x2F;state diagram really helped a lot.<p>And on not versionable: you are right only to an extent (e.g. exported Visio diagrams to JPG...). However there are tools&#x2F;methods, which can be versioned (e.g. generetaing UML via Graphviz&#x2F;dot, and AFAIK Enterprise Architect supports versioning too).