Sequence diagrams, the only good thing UML brought to software development

Re:Sequence diagrams, the only good thing UML brought to sof... by marcosdumay on Thursday June 15, 2023 @02:04PM (#36344324)

I don't think I have ever seen anybody actually getting value from a class diagram. I have seen many people creating them, but they are always useless.

I also don't think the UML variant of state machines and workflow are any popular. But well, there is probably somewhere where people use them. Also, those lists usually ignore entity-relationship diagrams, where UML just adopted the popular format (without even minor changes, like for workflows), and thus everybody uses the UML one.

But yes, people don't remember about deployment diagrams. Those are used a lot.

[ Parent | on HN ]

Re:Sequence diagrams, the only good thing UML brought to sof... by francois14 on Thursday June 15, 2023 @02:13PM (#36344445)

Class diagrams are a good way to detect circular dependencies.

[ Parent | on HN ]

Re:Sequence diagrams, the only good thing UML brought to sof... by marcosdumay on Thursday June 15, 2023 @02:55PM (#36344999)

If your class diagram is comprehensive enough to get circular dependencies, then I'm completely sure¹ nobody will use them for anything.

Computers are much better at this kind of checks anyway, and they don't need diagrams.

1 - Instead of "well, maybe it's possible despite I never seeing it"

[ Parent | on HN ]

Re:Sequence diagrams, the only good thing UML brought to sof... by ivan_gammel on Thursday June 15, 2023 @06:40PM (#36347745)

> I have seen many people creating them, but they are always useless.

Not every artifact is worth keeping, instead the value can come from the process of creation as a way to structure your thoughts or to explain or brainstorm possible solution. The value of class diagrams for those people is in the moment and it’s ok to throw them away later if they become useless.

[ Parent | on HN ]