Whiteboard visualization of your it architecture -

Once upon a time you have to draw a picture of your (planned) IT architecture / infrastructure on the whiteboard. Sometimes there are only IT people in the room, sometimes not. But anyway, generally you want to portray your IT system or architecture as a short description, not in full details.

What do I want to ask now, what stencils, diagrams, artifacts, etc., when you want to describe your architectural ideas, you use a system that excel import, XML export, an ASB in the middle , 3 different databases in different places, one web and one alone, Include? I think some people will come with a detailed UML class diagram, which will not serve well in this case. The sequence or activity diagram is good for the picture of the information flow, but not for more picture of the system.

So maybe we can gather some ideas about it.

Best agree,

Andi

PS: I thought it might be a good place to discuss it, but if it is too far So please tell me and I will close it or move on to a more appropriate place.

A short answer - The most relevant issue that works is that There is a way / language to communicate in the language which understands the audience .

I have some examples here that are clear very - if this is an independent debate, then they will not be there - nor should they also be a solution to the FYI I work as architect - boxes serve me well; I'm talking about most system references - where things fit in an existing scenario

To resolve some of your features:

• I use stick figures for roles and specific user groups - however boxes for business groups can be
• Data treasures (especially databases) work well as drums.
• Everything else is a box (if it's an important element in the radius of the diagram).
• It is important to add visual references to people - so it is good to create small boxes with lines to represent documents - possibly like a table for data sets.
• Arrows - the more solid it is, the faster it is, sometimes there is some indication that indirect or asynchronous.

I agree with your comment regarding UML: UML is very formal - when you are discussing in front of the bag, a white board is usually nothing.

Other things:

• Color use can really help, so do not be afraid to use it when appropriate.
• The order in which the diagram takes shape is relevant to the story that is telling it, do not be afraid to answer it for later use ...
• Whiteboard Most of the mobile phones are T-Hese days built cameras - use it.

()

()

()