4 ms·
There's quite a lot of hate in the comments for UML is seems. And while a lot of it is quite valid, I have to say that sometimes I miss _some_ of what UML could
by rytis 5y ago
There's quite a lot of hate in the comments for UML is seems. And while a lot of it is quite valid, I have to say that sometimes I miss _some_ of what UML could do, especially in form of documentation. Sometimes a simple sequence diagram is able to communicate the behavior of a system much clearer than 10's of pages of disjointed prose... Just my opinion.
- jugg1es 5y agoNothing is stopping you from creating diagrams, but UML is not required to create useful diagrams. Most concepts can be diagrammed using only boxes and lines.
- jhayward 5y agoThis could only be said by someone who hasn't sat through their Nth architectural overview where half the time is spent defining just exactly what was and was not intended by a particular line+arrow between two boxes when a simple sequence diagram would have been crystal clear.
- jugg1es 5y agoBoth simple box+line diagrams and sequence diagrams are entirely dependent on the creator's skill at creating diagrams. I've seen plenty of confusing sequence diagrams. I guess it also depends on whether your team find it useful that diagrams depict low-level highly detailed interactions as opposed to higher level architectural concepts.
- jorl17 5y agoSequence diagrams are the one UML diagram I regularly still produce to communicate behavior both to other developers and less technically minded people. I personally find them great (as long as you don’t get carried away in very minute notation)