Creating and Maintaining Architectural Fitness Functions
summary
Defines architectural fitness functions as measurable rules (a formula) that show how close code is to an architectural goal and gives concrete examples: treat code coverage as an alarm that points to refactoring opportunities, write performance tests as fitness functions to prevent regressions (one feature fixed in sprint 7 reappears by sprint 30 because no perf test existed), and enforce constraints with ArchUnit tests that fail the build (example: detect a vehicle↔engine cycle, move interfaces into a separate module, tests fail then pass in CI).
AI-written summary · about
chapters (6)
- 0:00Introduction to fitness functions
- 12:44What is a fitness function?
- 28:30Examples of fitness functions
- 40:15Enforcing architectural constraints
- 56:28Automating with ArchUnit
- 1:00:19Continuous integration and Q&A
related talks
42mFitness Functions for Your Architecture – in Practice
02mInterview with Nathaniel Schutta
50mBuilding Evolutionary Architectures
51mTesting Software Architecture
25mThe Intersection of Fitness Function driven Architecture and Agentic AI
22mArchitecture & ArchUnit
01h 34mThe Intersection of Architecture and Implementation
39mPrinciples of Evolutionary Architecture
