3 ms·
IMO UML adds negative value because, with only a very few exceptions, its semantics are carried by shapes that have no mnemonic relation to the concepts they ar
by lisper 10y ago
IMO UML adds negative value because, with only a very few exceptions, its semantics are carried by shapes that have no mnemonic relation to the concepts they are intended to communicate. What is the difference between a dashed line and a thin vertical box in a sequence diagram? A hollow vs a filled diamond in a class diagram? Does:
C1 ---> C2
mean that C1 inherits from C2 or that C2 inherits from C1? Does:
C1 ---* C2
[Note: the * is supposed to be a filled-in black diamond, but HN apparently doesn't allow unicode characters in comments.]
mean that C1 contains instances of C2 or that C2 contains instances of C1? What would it mean if the diamond were hollow instead of filled? What is the difference between a solid and a dashed line in a class diagram? A sequence diagram?
The only way you can possibly know the answers to these questions is if you have mastered an enormous amount of trivia. And then what have you actually gained? How is a class diagram better than simply writing out as text, "Class C1 inherits from C2, C3 and C4, and contains single instances of C6, C6 a set of C7s, and an ordered list of C8s?"
In >90% of cases, the information conveyed by UML can be much more easily and effectively communicated by plain text.
- dpark 10y ago> How is a class diagram better than simply writing out as text, "Class C1 inherits from C2, C3 and C4, and contains single instances of C6, C6 a set of C7s, and an ordered list of C8s?" I agree with much of your criticism of UML, but there is significant value in having a visual representation of class interactions. Your text takes longer to parse and understand than a simple diagram would be. For scenarios with numerous classes, the diagram becomes far easier than a text description.
- lisper 10y ago> the diagram becomes far easier than a text description If the text is hyperlinked it can be every bit as easy to follow as a diagram. In fact, it can be easier if things are really complicated because it allows you to focus your attention more easily just on the parts that matter to you at any given time.
- dpark 10y agoI don't agree with this at all. People naturally draw diagrams to demonstrate complex things. Any time a technical discussion gets complex, someone walks to a whiteboard or pulls out a piece of paper and starts drawing flows or interactions or whatever to clarify the discussion. Never have I seen someone say, "this is getting hard to follow, let me write some prose". If class diagrams are useless then so are bar graphs and scatter plots. You can just list out the data points and everyone can read them.
- lisper 10y agoNo, graphs and scatter plots are useful because the spatial distribution of markings actually conveys useful information: things that are physically close to each other are mathematically close to each other. But most UML diagrams aren't like that. And even for the ones that do try to convey information that has spatial analogs (like containment) UML doesn't actually take advantage of spatial relationships between elements. For example, the natural way to express containment is by putting one element inside the other in the diagram. That makes it obvious what contains what. But that's not how UML does it. Just about the only diagram that has a natural mapping from spatial relationships of the diagram elements to the actual underlying semantics is the sequence diagram.
- dpark 10y ago"Spatial" isn't particularly meaningful when talking about classes, so it's not surprising that UML doesn't generally attempt to express that. We can probably just agree to disagree here. I think class diagrams are often quite useful. They existed before UML and they are used even by people who don't use UML.
- lisper 10y ago> We can probably just agree to disagree here That works for me :-)