Explore effective software architecture visualization, documentation, and exploration techniques in this GOTO 2016 conference talk. Learn why diagrams can become messy, the pros and cons of UML, and how to create clear visual representations of software systems. Discover practical approaches to bridging the model-code gap, encoding architecture effectively, and creating supplementary documentation. Gain insights into tooling options and best practices for documenting software architecture. Understand the importance of balancing comprehensive documentation with working software in agile development, and acquire valuable tips for improving your software architecture communication skills.
Visualise, Document & Explore Your Software Architecture
Overview
Syllabus
Intro
Points of Interest
Selected Highlights
Visualization
Why your diagram such a mess
Should we use UML
UML is falling out of fashion
Visualising is hard
Notation
Logical View
Model Code
Quiz Time
Component
UML
Containers
Diagrams
Notations
Other considerations
Structure Iser
Model Code Gap
Components
Encoding
Architecture Description Language
Structure Isis
Find Components
Documentation
Single Tip
Supplementary Document
Tooling
Document length
Exploring
Summary
Conclusion
Taught by
GOTO Conferences
