Visualise, document and explore your software architecture
summary
Claims that teams should model architecture with a small, consistent vocabulary and generate diagrams from a code-backed model rather than hand-drawn Visio art. Uses the C4 model and open‑source libraries for Java and .NET to build an executable architecture description, a component finder that discovers components in code, and exporters to Graphviz and PlantUML or the hosted Structurizr service to produce up‑to‑date context/container/component views. Workshop experience: 25+ countries, 10,000+ people; design down to components and keep docs as a concise “software guidebook.”
AI-written summary · about
chapters (24)
- 0:00Introduction
- 2:30Jersey Visitor Map
- 4:03Jersey Castle
- 5:57Visualise
- 6:54Group exercise
- 9:12UML
- 9:59Is UML worth using
- 13:19Four plus one view model
- 14:51Logical vs physical design
- 15:12Model vs code
- 17:22Common language
- 23:12Environment language UML
- 29:18Generalpurpose tooling
- 31:12Reverse engineer diagrams
- 34:48Reverse engineer code
- 35:28Architecture 11 encoding
- 40:55Visualisation
- 44:05Documentation
- 44:34Documentation naming
- 46:24Constantly evolving
- 46:40tooling
- 47:57exploring
- 50:37summary
- 52:06questions
related talks
01h 00mVisualise, document and explore your software architecture
42mSoftware Architecture vs Code
45mSet your data free with model-based architecture diagramming
54mC4 models as code
34mDiagram as Code - Decoding Architectural Diagrams
01h 00mC4 models as code
49mReverse-engineering Architecture Diagrams
48mDown the Ivory Tower towards Agile Architecture