The C4 model for visualising software architecture

Table of Contents
About the book
About the author
We have a failure to communicate
	What happened to SSADM, RUP, UML, etc?
	A lightweight approach
	Draw one or more diagrams
	Where do we start?
	Some examples
	Common problems
	The hidden assumptions of diagrams
A shared vocabulary
	Common abstractions over a common notation
	Static structure
	Components vs code?
	Modules and subsystems?
	Microservices?
	Serverless?
	Platforms, frameworks and libraries?
	Create your own shared vocabulary
The C4 model
	Hierarchical maps of your code
Level 1: System Context diagram
	Intent
	Structure
	Elements
	Interactions
	Motivation
	Audience
	Required or optional?
Level 2: Container diagram
	Intent
	Structure
	Elements
	Interactions
	Motivation
	Audience
	Required or optional?
Level 3: Component diagram
	Intent
	Structure
	Elements
	Interactions
	Motivation
	Audience
	Required or optional?
Level 4: Code-level diagrams
	Intent
	Structure
	Motivation
	Audience
	Required or optional?
Notation
	Titles
	Keys and legends
	Elements
	Lines
	Layout
	Orientation
	Acronyms
	Quality attributes
	Diagram scope
	Listen for questions
Diagrams must reflect reality
	The model-code gap
	Technology details on diagrams
	Would you code it that way?
Deployment diagrams
	Network and infrastructure diagrams
	Deployment diagrams
	Cloud architecture diagrams
Other diagrams
	Architectural view models
	System Landscape
	User interface mockups and wireframes
	Business process and workflow
	Domain model
	Runtime and behaviour
	And more
Appendix A: Financial Risk System
	Background
	Functional Requirements
	Non-functional Requirements