Testing Software Architecture
summary
Describes automatic testing of software architecture using static code analysis to detect increasing global coupling, “big ball of mud” patterns, and exploding module APIs (e.g., a module growing from 10 to 110 public methods). Presents concrete checks, CI integration, time-series graphs of module boundaries, and heuristics to detect costly over- and under-engineering early so refactor costs remain bounded.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:26Architect's background
- 5:26What is software architecture
- 8:18Controlling complexity with modules
- 12:37Defining module boundaries
- 15:28Evolutionary architecture
- 17:36Testing architecture for issues
- 27:08Continuous feedback discipline
- 28:39Static analysis testing
- 34:21Company growth impact
- 38:16Key architecture recommendations
- 40:50Conclusion & Q&A
related talks
43mTesting Software Architectures
40mTesting Software Architecture
41mInside Software Architecture - Where the Bodies are Buried
49mBottom-up Architecture: Bridging the Architecture-Code Gap
24mThe too many faces of Architecture
45mSoftware Architecture for Humans!
49mArchitecture assessments
24mBuilding Software Architecture from First Principles