Item — HN Reader

Nevertheless it would be useful if everyone knew which "arrows" mean subtyping vs. reference vs. ownership vs. instantiation, and which boxes mean action vs. object/class, etc. If you only have "arrow" and "box", you have to explain what you mean by them in the specific instance every time.

Also, UML does have some nice graphical notation like ——(o—— to denote interface and implementation (sockets and plugs).

1 comments

> explain what you mean by them in the specific instance every time.

this is a feature, not a bug.

The diagram isn't a substitute for the conversation. It's an aid for the conversation (and a way of remembering what was said afterwards).

The mistake was always trying to come up with a diagramming methodology that could communicate the entire design without the need for people to talk to each other.