It's been a while since I've done a class diagram, but I still use sequence diagrams to coordinate non-trivial component interactions. Occasionally, I'll use a state diagram to describe workflow. More commonly, I've used ad-hoc network diagrams to describe the architecture of a system. I think flowcharts are still useful.
Ask HN: What Has Replaced UML?
11–14 of 14 posts
Re: Ask HN: What Has Replaced UML?
#12On a related note - are there diagramming tools that let you draw (and write) freehand and then automatically neaten the diagram up?
I'm imagining something on an iPad or Android tablet that lets me just draw my usual boxes, circles, lines, terrible handwriting, and so on, and then I can punch a button and get it as a draw.io (or whatever) compatible diagram...?
The Newton handheld had some abilities along this line in the mid nineties so it seems like it shouldn't be an impossible dream.
Re: Ask HN: What Has Replaced UML?
#13Nicely specced TTD style tests can show and then also verify that things work as you might expect them to.
They can serve as example and documentation on how the architectural pieces fit together in a piece of software.
That plus high level, loosely specced diagrams can encapsulate most simple/medium complexity apps.
Re: Ask HN: What Has Replaced UML?
#14The key problem with UML was that it was trying to work on a too low a level, essentially replacing code with diagrams, which didn't really work. The only UML diagram that is still relevant today is the sequence diagram, because it has just the right balance between being too abstract and being too specific.
In my experience, the best approach in documenting software systems is the C4 model: https://c4model.com/