Can I ask what the role of UML is in an Agile landscape these days? When I think of software design, we dont really have any OTHER way to express relationships in code. Is this just an ad-hoc thing we use every now and then, or do some teams use it more formally?
I still would like to learn how to _model_ with UML instead of just drawing. Never seen a UML model in a tool where all diagrams are really connected through the database model.
I would call what you call “drawing” “modeling”, too. I’ve seen the kinds of models you refer to, but they’re only worth the effort in particular circumstances
Some skills are useful, some are not so much. Here is an interesting list medium.com/swlh/41-skills-to… and i feel some of these skills are better than learning UML (imo)
UML is the boomer “architects conceptual toolbox” 😀. Similar to “JavaScript the Good Parts”. The same applies to UML. It got a bad rep because it was overloaded for use. Generate requirements, tests, code, etc. all from diagrams.... oh and XML and friends 😀
Because most people use it with the wrong tools or as documentation only. We use EMF and it is glorious! Create your model, generate the code and we instantly get our DB and API model in a way even the non technical people understand.