# Coupling and Cohesion

**In short:** Coupling describes how strongly modules depend on each other. Cohesion describes how well the parts inside one module belong together. Low coupling often goes with high cohesion.

## Explanation

Coupling and cohesion are two ways to judge how a system is split into parts. The ideas come from structured design, published by Stevens, Myers and Constantine in 1974. A module is one such part (see the article *Module*).

**Coupling** is about the links *between* modules. It can be low (also called loose or weak) or high (also called tight or strong). See *Loose Coupling* and *Reduce Coupling*.

**Cohesion** is about the inside of one module. It is the degree to which the elements in a module belong together. See *High Cohesion* and *Increase Cohesion*.

The two ideas often move together. Low coupling often goes with high cohesion, and the reverse also holds.

**Levels of cohesion.** Cohesion comes in types, from weak to strong:

- **Coincidental:** the weakest. Parts are grouped arbitrarily.
- **Sequential:** parts are grouped because the output of one is the input of the next.
- **Functional:** the best. All parts contribute to one well-defined task.

The article *Types of Cohesion* covers the range.

**Link to modifiability.** The SEI report on modifiability tactics bases its tactics on coupling, cohesion and cost motivations. It also ties the tactics to the parameters of quality attribute models. See *Modifiability Tactic*.

## Example

A shop system has a module called "Utilities". It holds price rounding, email sending and image resizing. These parts have nothing in common, so its cohesion is coincidental. A second module, "Invoice Calculation", only computes invoice totals. Every part serves one task, so its cohesion is functional. The second module is easier to describe and to find your way around in.



## Checks

- Modules are described by one well-defined task each, rather than grouped arbitrarily.
- Where modules depend on each other, the document shows how strong that coupling is (loose or tight).

## Related

- [Loose Coupling](https://arc.fuet.ch/concepts/principles/loose-coupling.md)
- [High Cohesion](https://arc.fuet.ch/concepts/principles/high-cohesion.md)
- [Types of Cohesion](https://arc.fuet.ch/concepts/principles/types-of-cohesion.md)
- [Reduce Coupling](https://arc.fuet.ch/concepts/tactics/reduce-coupling.md)
- [Increase Cohesion](https://arc.fuet.ch/concepts/tactics/increase-cohesion.md)
- [Modifiability Tactic](https://arc.fuet.ch/concepts/tactics/modifiability-tactics.md)
- [Module](https://arc.fuet.ch/concepts/domain-driven-design/module.md)
- [Information Hiding](https://arc.fuet.ch/concepts/principles/information-hiding.md)

## Sources

- [Coupling (computer programming) - Wikipedia](https://en.wikipedia.org/wiki/Coupling_(computer_programming)) — en.wikipedia.org, accessed 2026-11-08
- [Cohesion (computer science) - Wikipedia](https://en.wikipedia.org/wiki/Cohesion_(computer_science)) — en.wikipedia.org, accessed 2026-11-08
- [Modifiability Tactics | CMU Software Engineering Institute](https://www.sei.cmu.edu/library/modifiability-tactics/) — sei.cmu.edu, accessed 2026-11-08