Improve your architecture with the Modularity Maturity Index (MMI)
summary
A concrete scoring system called Modularity Maturity Index (MMI) rates codebases 0–10 (under 4 = bad, 4–8 = okay, >8 = good) based on 22 factors across modularity, hierarchies and pattern consistency; measurement combines static-analysis tools (example: sonograph), metric scripts/Excel and expert review. Empirical dataset covers ~500 systems (sizes 20k–50M LOC), finds nasty dependency tangles like a 119-class cycle, and shows MMI pinpoints where to refactor, replace, or leave alone.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker intro
- 2:28Problem with legacy systems
- 6:21Introducing Modularity Maturity Index
- 8:51Cognitive science behind modularity
- 12:45Chunking and modularity principles
- 15:14Hierarchies in software architecture
- 16:14Schemata and design patterns
- 23:28Technical and domain layering
- 29:33Domain modules and big ball of mud
- 31:19Class-level hierarchies and cycles
- 33:51Tools for modularity analysis
- 36:00Pattern consistency and violations
- 40:39Annual rings and pattern bloat
- 42:25Calculating the Modularity Maturity Index
- 43:52Q&A session
related talks
54mResolving technical debts in software architecture
01h 15mHow to measure your architecture
49mRealizing Domain Design Through Architectural Modularity ...
38mDomain-Driven Transformation - how to improve the structure of legacy systems
59mNavigating the MV* Mess
44mTesting Software Architecture
52mWhat Does a Good Microservice Architecture Look Like?
57mUnderstanding the Differences Between Modularity and Granularity