I always treated UML as a window into the domain, not as a precursor to the code. With just a few Use Case diagrams, some class diagrams, and maybe some sequen

I always treated UML as a window into the domain, not as a precursor to the code. With just a few Use Case diagrams, some class diagrams, and maybe some sequence diagrams, you could communicate what the final system should do and how people will interact with it. The details of how to implement would be derived from the architecture used. I always found even a few basic diagrams with little detail (classes without fields) very useful and miss them now that people don't want to "waste time".