Drawing Effective Architecture Diagrams with the C4 Model

Clarifying Basic Concepts

1. What Is Architecture

Architecture is an abstract description of entities in a system and their relationships, a series of decisions. It is structure and vision. System architecture embodies concepts, allocating functional and formal elements of matter/information, defining relationships among elements and with the environment.

2. What Is an Architecture Diagram

A system architecture diagram abstractly represents the overall outline of a software system, the relationships and constraints among components, physical deployment, and evolution direction.

3. Purpose of Architecture Diagrams

To solve communication barriers, reach consensus, and reduce ambiguity. A diagram is a vehicle to convey architectural decisions to stakeholders.

4. Architecture Diagram Classification

The popular 4+1 view model includes: Scenario View (use cases, typically UML use case diagrams), Logical View (component relationships, constraints, boundaries, typically UML component/class diagrams), Physical View (software-to-hardware mapping, deployment guidance), Process View (communication sequences, data input/output, typically sequence/flow diagrams), Development View (module organization, package structure for developers). These five views combine into an architecture blueprint.

What Makes a Good Architecture Diagram

First clarify the audience and the message to convey. Do not draw a view just for the sake of the view type; choose diagrams based on audience and message. A good diagram is self-descriptive, consistent, accurate, and maps to code.

Common Problems

1. What Do Boxes Represent?

Random use of rectangles vs circles causes confusion about meaning.

2. What Do Lines, Arrows, Colors Mean?

Arbitrary line styles (solid vs dashed), arrow directions, and colors lead to misinterpretation.

3. Runtime vs Compile-Time Conflicts? Level Conflicts?

Using a single diagram for complex architecture creates semantic chaos by mixing runtime and compile-time concerns or different abstraction levels.

Recommended Drawing Method: The C4 Model

The C4 model uses containers (applications, data stores, microservices), components, and code to describe static structure. It clearly defines the audience and purpose for each diagram level.

1. System Context Diagram

Shows the system to be built, its users, and external systems it interacts with. Example: an internet banking system using a mainframe banking system for customer accounts/transactions and an email system for notifications. Audience: technical and non-technical stakeholders. Purpose: convey what the system is, who uses it, how it fits into the existing IT environment. How to draw: place your system in the center, surround with users and interacting systems; clarify high-level dependencies.

2. Container Diagram

Expands the system from the context diagram. Example: the banking system decomposed into a Java/Spring MVC web application (functional entry), a Xamarin mobile app (mobile entry), a Java API application (services), and a MySQL database (storage). Interactions labeled on arrows. Audience: developers and operations. Purpose: show overall shape, high-level technology decisions, responsibility distribution, container interactions, and where developers write code. How to draw: boxes with name, technology, responsibilities; show interactions; mark external system boundaries.

3. Component Diagram

Expands a container to show internal modules. Audience: internal developers. Purpose: describe components/services, clarify relationships and dependencies, provide framework for development decomposition.

4. Code/Class Diagram

Standard UML class diagram for technical audience; omitted detailed explanation.

Case Study

An internal real-time data tool architecture diagram presented as a self-descriptive example; if unclear, the diagram needs improvement.

Conclusion

Many methodologies exist; the key is to think before drawing: who is the audience, what do they need to see, and how to make it understandable without explanation.

References

C4 Model Official Site: https://c4model.com/

Why Software Architecture Diagrams Are Needed: https://www.infoq.cn/article/GhprrUlOYyOqS8*FR1pH

Book: "Software Architecture for Developers" (《程序员必读之软件架构")

Code example

--完--
读到这里说明你
喜欢
本公众号的文章，欢迎
置顶（标星）
本公众号 架构师指南，这样就可以第一时间获取推送了~
在
本公众号 架构师指南，后台回复：
架构师
，领取2T学习资料 ！