
< session />
Tue, April 27Architecture & Distributed Systems
Software architecture diagrams are meant to help teams communicate, yet many end up as a confusing collection of boxes and arrows. Moving fast requires good communication, and a clear set of architecture diagrams can help align teams around a shared vision, get new joiners productive quickly, and ensure AI agents stay under control.
In this session, you will explore how to communicate software architecture visually using the C4 model. You will examine the importance of a shared vocabulary, diagram notation, and a lightweight model for describing a software system. You will also learn how the C4 model creates maps of your code at different levels of detail, allowing you to communicate different stories to different audiences, both during up-front design and when documenting an existing codebase.
What You Will Learn
How a shared vocabulary and clear diagram notation improve the communication of software architecture
How the C4 model describes a software system at different levels of detail
How to use C4 diagrams during up-front design and when documenting an existing codebase
Who Should Attend
Software Architects, Developers, Technical Leads, and engineering practitioners who design, document, or communicate software architecture.
< speaker_info />
Simon is the creator of the C4 model for visualising software architecture and Structurizr - the original developer-friendly "models as code" tooling for creating version-controlled software architecture diagrams based upon the C4 model. He is the author of "The C4 Model" (O'Reilly) and “Software Architecture for Developers” (Leanpub). Simon has worked with hundreds of organisations across ~40 countries, from startups to global household names in almost every industry sector, helping teams adopt the C4 model and communicate their software architecture more effectively.