Introduction

Diagrams are a great way to visually communicate something. However, the majority of software architecture diagrams don’t really express what they intend to, lacking description of its elements and with lots of implicit notations only understood by those who drew the diagram. Also, they try to express more than one vision (high level, infrastructure, flow order, etc) in only one diagram, making it even harder for non-technical people or people outside the project to understand.

In this post, I’ll present the C4 model and how it can produce software architecture diagrams that are inclusive to non-technical people, easier to understand and, consequently, better to document our software systems.