If you learn only one diagram from UML, take the time to understand and use Sequence Diagrams [1]. Being able to break down an interaction into a sequence diagram (especially between 2 or 3 servers) is a powerful thought tool for specifying interactions and its easy for people to understand. [1] http://en.wikipedia.org/wiki/Sequence_diagram
zenbowman's reply is [dead]. Why?
Ask HN: Is UML still relevant today?
41–50 of 69 posts
Re: Ask HN: Is UML still relevant today?
#42Are squiggly boxes with lines and words in them still usefull? And maybe we should have some convention around them squigglies?
Well, considering you're reading this on a screen filled with squiggly boxes and lines and words, yes, I'd say that much is still useful.
The advantage of UML, as with any standard, is that it is a universal way of drawing those squiggly lines and boxes. If you've ever tried to draw a software representation, you'll realize its actually quite difficult to do.
Until language and conventions stop being useful, UML will remain.
Re: Ask HN: Is UML still relevant today?
#43Re: Ask HN: Is UML still relevant today?
#44ERDs? Documentation tools? Or do you simply tell the engineer to read the code?
Re: Ask HN: Is UML still relevant today?
#45Re: Ask HN: Is UML still relevant today?
#46Personally, in about a decade of programming, I've only had call to say "You know what we need right now? A UML diagram, that's what." about two or three times, and it is always about a sequence diagram for fairly complicated protocols.
Re: Ask HN: Is UML still relevant today?
#47For database designs, textual schemas, E/R diagrams or plain SQL are sufficient. I've drawn plenty of state diagrams without crediting UML handbooks. E/R diagrams can double as "class diagrams" in the sense that you don't need all the complexity of properties and methods in a diagram to convey which classes exist and how they're related.
People who think that drawing bubbles with arrows between them is a language, in more than a philosophical-linguistic sense, should probably take some more certificates.
To be fair, and to repeat some answers I've read so far: Of course, some diagrams are very useful. But to credit UML because individuals find it useful and necessary to draw things is stretching it.
Re: Ask HN: Is UML still relevant today?
#48If not UML, what do you recommend for most effective communication? ERDs? Documentation tools? Or do you simply tell the engineer to read the code?
Re: Ask HN: Is UML still relevant today?
#49If you learn only one diagram from UML, take the time to understand and use Sequence Diagrams [1]. Being able to break down an interaction into a sequence diagram (especially between 2 or 3 servers) is a powerful thought tool for specifying interactions and its easy for people to understand. [1] http://en.wikipedia.org/wiki/Sequence_diagram
I co-wrote a book on UML years ago, used to be an enthusiast. Now I write some sequence diagrams, and once in a while might write a high level class diagram.
It is all about communication, and a sequence diagram is good for that.
Re: Ask HN: Is UML still relevant today?
#50Earlier quoted context omitted.
A great open source tool for these is http://www.mcternan.me.uk/mscgen/
Also https://www.websequencediagrams.com/ and http://www.umlet.com/ (if you need to do more then just sequence diagrams)