Yes, exactly. Modelling things has many uses (collaborative thinking, communication, dependency tracing, complexity management etc.) and specifying things is pr

Yes, exactly. Modelling things has many uses (collaborative thinking, communication, dependency tracing, complexity management etc.) and specifying things is probably one of the least useful of these. I work with UML (and Sparx EA) primarily as a high-level architecture tool. Once everybody has a rough shared understanding of what and why we are building, people get to coding and UML stops. Should we get to a problem, we dig up the initial idea, validate it, us it for problem-solving and move on. Sometimes sequence diagrams might be used for making sure everybody has the same understanding of how an interaction should go. But that’s it. Communication, problem-solving, knowledge management. And not specification.