Explore the intersection between software architecture and code in this 46-minute conference talk from GOTO Amsterdam 2014. Delve into effective communication strategies for software architecture, examining how code embodies architectural decisions. Learn about the importance of aligning abstractions in diagrams with actual code structure, and understand why software developers are crucial stakeholders in architectural decisions. Discover insights on code organization, the limitations of diagramming tools, and the impact of architecture on agility. Challenge common practices like unit testing and gain practical advice on improving difficult-to-work-with software systems. Emphasize the significance of software structure and decomposition strategies in creating maintainable and adaptable systems.
Overview
Syllabus
Introduction
The intersection between software architecture and code
How do we communicate software architecture?
boundaries for TDD
Logical and development separated
BRAIN FREEZE!
The code is the embodiment of the architecture
Does your code reflect the abstractions that you think about?
Organisation of code
Diagramming tools See packages and classes rather than components
Abstractions on diagrams should reflect the code
Software developers are the most important stakeholders of software architecture
Did it start out that way?
Don't do unit testing!
A good architecture enables agility
The structure of your software and the decomposition strategy you use to get there are important
Think about how to align the software architecture and the code
If your software system is hard to work with, change it!
Taught by
GOTO Conferences
