4 ms·
The difference is that you can't really use proper UML to quickly explain something on a whiteboard, unless you were fluent in it. I personally get mental inhib
by Double_a_92 7y ago
The difference is that you can't really use proper UML to quickly explain something on a whiteboard, unless you were fluent in it. I personally get mental inhibitions when I have to quickly decide if the arrowhead needs to be hollow or filled, or if the arrow itself needs to be a line or dotted, or if the box needs to have rounded corners or not... Especially if it doesn't matter for the idea that I'm trying to explain (maybe even just to myself).
- rumanator 7y ago> The difference is that you can't really use proper UML to quickly explain something on a whiteboard, unless you were fluent in it. That's not true. Class diagrams are boxes with arrows, and so are component diagrams and communication diagrams and deployment diagrams. If you can draw a box and lines on a whiteboard, you can use UML on a whiteboard. AFAIK, the only thing that's not explicitly supported in UML is data flow diagrams (i.e., convey the data perspectice instead of describing software components and their interactions).