Loading content
High cohesion is a principle in software architecture aimed at ensuring that modules perform closely related functions. This results in improved maintainability, reusability, and understandability of code, as changes in a high-cohesion module have less impact on other modules.
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.
High cohesion means that a module’s elements belong closely together and jointly serve a clearly recognizable purpose.
The term comes from software design and research on modularity and information hiding. Larry Constantine and Edward Yourdon made cohesion, alongside coupling, practical for evaluating module quality.
Sort responsibilities like tools in drawers: things that perform one task together stay together; things involved only by accident go in another drawer.
A module’s elements contribute to the same domain or technical purpose.
A boundary that bundles related responsibility.
Dependency between separate modules, which should remain low.
High cohesion improves understandability, changeability, and local testing. It is a design heuristic; overly fine-grained decomposition can multiply interfaces and coupling.
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.