I’m not a big fan on spending an inordinate amount of time on diagramming solutions or concepts down to the nth detail primarily because that level of detail will always, always, always change and you will be left with outdated diagrams that when someone goes to look at what they are will be confused.
I am a big fan of drawing out ideas on the whiteboard though (big fan) and do realize that these diagrams have their place in getting people on board to adopt a solution.
Hence, keys to putting together an Architecture Diagram that people will get behind.
- Make it Simple – if your diagram is overly complex with icons all over the place, simplify it, break it into multiple diagrams. If you can’t understand it and describe what is going