> 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 dia

> 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).