Visualise, Document and Explore Your Software Architecture

Explore software architecture visualization, documentation, and exploration techniques in this 50-minute conference talk from GOTO Copenhagen 2016. Learn why effective communication is crucial for team alignment and discover the importance of bridging the gap between logical and development views in architecture diagrams. Understand the significance of common abstractions that reflect technology, and gain insights into the C4 model for software architecture. Examine the relationship between code and architecture, including the concept of creating an architecture description language using code. Delve into the balance between working software and comprehensive documentation, addressing tribal knowledge and the limitations of code in telling the whole story. Investigate tactics for better team collaboration, modern tools for documentation, and the value of a ubiquitous language in describing software systems.

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?