Technical architecture diagram summary

What is an architecture? An
architecture is an abstract description of the entities in the system and the relationships between entities. It is a series of decisions.
Architecture is structure and vision. The system architecture is the embodiment of the concept, the allocation of the correspondence between the function of the object/information and the form element, and the definition of the relationship between the elements and the relationship between the elements and the surrounding environment.
Doing a good architecture is a complex task and a big topic, so I won't go into it in this article. After the structure is in place, stakeholders need to understand and follow relevant decisions.

What is an architecture diagram? The
system architecture diagram is to abstractly represent the overall outline of the software system and the interrelationship and constraint boundaries between the various components, as well as the overall view of the physical deployment of the software system and the evolution direction of the software system.

The role of architecture diagrams
A picture is worth a thousand words. In order for stakeholders to understand and follow architectural decisions, the architectural information needs to be communicated. The architecture diagram is a good carrier.
So, the purpose of drawing the architecture diagram is to
resolve communication barriers,
reach consensus, and
reduce ambiguity

Ali God teaches you how to draw a technical architecture diagram

Personal summary: a
comprehensive description of the system
, logical/own thinking,
beautiful colors, hierarchical relationships,
use legends to clearly
mark the relationship between SD components

Guess you like

Origin blog.csdn.net/sxhexin/article/details/108312011