Computer Science › Section H · Software engineering › Topic H.4
Modularity: coupling and cohesion
Nobody can hold a million lines of code in their head, so large systems are split into modules that can be understood, built and changed one at a time. Two ideas measure how well the split was done: coupling between modules should be low, and cohesion within each module should be high.
In this topic
- Why divide software into modules
- Two ways to break up a problem
- Coupling
- The trouble with global data
- Worked example: counting hidden coupling
- Cohesion
- Cohesion in classes
- Worked example: removing a control flag
- Information hiding
- Components and reuse
- Common mistakes to avoid
- Key takeaways
This topic is part of Wuanberri Pro. Checking your access…