The Modular Maturity Index (MMI) — associated with Dr. Carola Lilienthal — provides a structured way to assess “modularity” based on observable criteria rather than gut feel. It makes architectural quality visible through measurable signals such as coupling, cohesion, dependency structures, and change dynamics, and turns the findings into actionable improvem…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
The Modular Maturity Index assesses how well a software architecture is divided into clear, changeable, and maintainable modules.
The index was developed as a practical architecture metric to make modularity and technical debt visible together. O'Reilly describes it as a metric that makes module boundaries and dependencies useful for maturity decisions.
Judge a building by its apartments: clear entrances, few shared walls, and separate utilities make renovation easier. Many openings and hidden connections reduce modularity.
A module groups functions that belong closely together.
Dependencies show how strongly changes cross module boundaries.
Metrics make architecture quality comparable and observable over time.
The index supports architecture decisions and refactoring when teams use measurements as a discussion aid alongside engineering judgment.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.