How to Draw Effective Architecture Diagrams

The author, a senior architect, introduces the purpose of architecture diagrams: to abstractly represent a system’s overall structure, component relationships, deployment, and evolution, helping stakeholders understand and follow architectural decisions.

Key definitions are provided: architecture is a conceptual representation of the mapping between functional and structural elements, a set of decisions, and a vision. In the TOGAF framework, architecture is refined from strategy down to business, application, data, and technology layers.

The article outlines four major architecture categories:

Business Architecture : defined by business architects, influences organizational and technical design.

Application Architecture : designed by application architects, focuses on modular structure, interfaces, data exchange, and non‑functional attributes such as performance and security.

Technical Architecture : describes required services, technology components, and their interactions.

Data Architecture : covers data models, distribution, flow, lifecycle, and management.

Two popular diagram view models are introduced:

4+1 View Model

Scenario View : shows actors and use cases, usually a use‑case diagram.

Logical View : depicts component and class relationships, often using UML component/class diagrams.

Physical View : maps software components to hardware nodes, guiding deployment.

Process View : illustrates component communication sequences and data flow, typically with sequence or flow diagrams.

Development View : details module/package structure for developers.

Images illustrating each view are included in the original article.

C4 View Model

The C4 model breaks down a system into:

System Context Diagram : shows the system, its users, and external dependencies.

Container Diagram : expands the system into high‑level containers (applications, databases, micro‑services) and their interactions.

Component Diagram : drills into a container to reveal internal components and their relationships.

These diagrams are easier to draw and each has a clear audience and purpose.

When creating diagrams, the author emphasizes two crucial points: identify the audience first and ensure the diagram conveys the intended information without unnecessary detail, and use visual elements (shapes, colors, line styles) to differentiate meanings and avoid semantic confusion.

A good architecture diagram should be self‑describing, consistent, accurate, and aligned with the actual code base.

<section style="letter-spacing: 0.544px">
  <pre>
    最近面试BAT，整理一份面试资料《Java面试BAT通关手册》，覆盖Java核心技术、JVM、并发、微服务、数据库等。
    获取方式：关注公众号并回复“手册”领取。
  </pre>
</section>