Software Engineering · Architecture
How tightly a module's responsibilities relate to one single purpose, rather than being a grab-bag of unrelated tasks.
Example: A module that only sends emails is more cohesive than one that also handles payments and analytics.
In practice: High cohesion and low coupling tend to go together — a module that does one thing well rarely needs to know much about its neighbors.