Visualise, Document and Explore Your Software Architecture

This talk examines how to visualize and document software architecture so diagrams reflect the code and help teams communicate. It discusses the C4 model, architecture description languages, and what documentation should capture beyond the code.

Syllabus

Introduction
Selected highlights
Moving fast in the same direction requires good communication
Why is there a separation between the logical and development views?
the architecture diagrams don't match the code
A common set of abstractions is more important than a common notation
The abstractions must reflect the technology
Think about the target audience
C4 is not a design process
retrospectively drawing diagrams
What is a "component"?
The code is the embodiment of the architecture
Is the architecture in the code?
Architecture description languages
Create an architecture description language using code
"Component Finder"
Working software comprehensive documentation
The code doesn't tell the whole story
Tribal knowledge
Product project
Microsoft Word?
Documentation should describe what the code doesn't
Tactics for better teams
The 1990's called and they want their tools back.
Do you have a ubiquitous language to describe your software?