Why do I need architecture diagram, how to draw?

Technorati Tags: architecture diagram, architecture, communication, layout

Unconsciously in the architect has been 4 years, the initial feeling is just a name, no longer the code as a mandatory task, and then began to slowly change the work content. Drawing, became my main work. I may not be writing code every day, but I am drawing every day, and I feel more and more that drawing makes it easier for me to be clear.

The easel composition has several advantages: see what parts the system contains, what responsibilities each part implements, and what the relationship is between each other. When discussing with others, it is easy to frame the discussed problem in a definite scope, and it is easy to perceive some areas where there is misunderstanding, such as to a lower component. This will prevent two of people to discuss the half-day, and found that you are talking about a module, I am talking about the B module.

When I need to explain a problem to someone, by drawing, you can effectively explain the background of the problem, what is relevant and what is irrelevant. The person who listens to me can quickly enter my role, ask a specific question, and understand my requirements.

So how can you draw a high-quality architecture diagram?

First you need to understand that the purpose of your drawing is to show whether it is business or technology, whether it is a whole or a part, whether it is completed or pending.

After determining the purpose, it is necessary to determine what the key factors to achieve this goal, for example, in order to illustrate the business, I need to explain who the user is, what the purpose of doing this business, do business when the system needs to complete what tasks, after the completion of other systems will be affected;

After determining the key factors, you need to choose a method to express the key factors, independent blocks, blocks contained within the block, flow, mesh;

Finally, to start drawing, we must first draw high-level modules, determine the location of each module, determine the core content of each module, and then sub-module filling the contents. Don't start off with a small module, get caught in the details prematurely.

Why do I need architecture diagram, how to draw?