Loading content
Coupling describes how strongly modules are interconnected, while cohesion refers to the internal consistency of a module. High cohesion and low coupling are desirable properties that enhance the maintainability and flexibility of software.
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 organizes, connects, or makes decisions possible.
Coupling describes dependencies between modules, while cohesion describes how closely a module's responsibilities belong together.
The terms come from structured software development and were established in software-design teaching by Yourdon and Constantine. They later became guiding criteria for modular and object-oriented architecture.
A good module is like a well-organized toolbox: its tools serve one related purpose, while the boxes connect through a few clear handles. Strong internal focus and limited external dependency make change easier.
The strength and number of dependencies between modules.
How closely a module's responsibilities belong together.
The interface through which a module communicates with others.
Together, the concepts help limit change propagation and clarify responsibilities. They do not automatically produce an optimal decomposition; domain boundaries and actual change patterns matter too.
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.