✳flâneur — a map of the web's best reading

The C4 model for visualising software architecture

c4model.com · 137 words · saved by 1 readers

1. A set of hierarchical abstractions (software systems, containers, components, and code). 2. A set of hierarchical diagrams (system context, containers, components, and code). 3. Notation independent. 4. Tooling independent. The C4 model is an easy to learn, developer friendly approach to software architecture diagramming. Good software architecture diagrams assist with communication inside/outside of software development/product teams, efficient onboarding of new staff, architecture reviews/evaluations, risk identification (e.g. risk-storming), threat modelling, etc. Ask somebody in the building industry to visually communicate the architecture of a building and you'll be presented with site plans, floor plans, elevation views, cross-section views and detail drawings. In contrast, ask a software developer to communicate the software architecture of a software system using diagrams and you'll likely get a confused mess of boxes and lines ... inconsistent notation (colour coding, shap

Home | C4 model Skip to main content Menu Expand (external link) Document Search Copy Copied C4 model The C4 model for visualising software architecture The C4 model is an easy to learn, developer friendly approach to software architecture diagramming: A set of hierarchical abstractions - software systems , containers , components , and code . A set of hierarchical diagrams - system context , containers , components , and code . An additional set of supporting diagrams - system landscape , dynamic , and deployment . Notation independent . Tooling independent . Visualising software architecture

Explore this link on the map →

related reading