Coupling and cohesion in Software Engineering - Step-by-Step Execution

Concept Flow - Coupling and cohesion

Start: Design Module

↓

Check Cohesion

↓

Good

↓

Check Coupling

↓

Good

↓

Final Design Decision

The flow shows checking cohesion first, aiming for high cohesion, then checking coupling aiming for low coupling, leading to a good module design.

Execution Sample

Software Engineering

Module A: Handles user login
Module B: Processes payments
Module C: Sends notifications

Check cohesion and coupling between modules

This example shows three modules with different responsibilities; we check if each module is focused (high cohesion) and if modules interact minimally (low coupling).

Analysis Table

Step	Module	Cohesion Level	Coupling Level	Action	Result
1	Module A	High	Low	Evaluate	Good cohesion and low coupling
2	Module B	Medium	High	Evaluate	Needs improvement in coupling
3	Module C	Low	Medium	Evaluate	Needs improvement in cohesion
4	Design Decision	-	-	Refactor Module B and C	Improve coupling and cohesion
5	Module B (after)	High	Low	Re-evaluate	Good cohesion and low coupling
6	Module C (after)	High	Low	Re-evaluate	Good cohesion and low coupling
7	Final	-	-	Confirm	Modules well designed with high cohesion and low coupling

💡 All modules have high cohesion and low coupling, indicating good design.

State Tracker

Module	Initial Cohesion	Initial Coupling	After Refactor Cohesion	After Refactor Coupling
Module A	High	Low	High	Low
Module B	Medium	High	High	Low
Module C	Low	Medium	High	Low

Key Insights - 3 Insights

Why is high cohesion important in a module?

High cohesion means the module focuses on a single task, making it easier to understand and maintain, as shown in execution_table steps 1 and 5.

What problems arise from high coupling between modules?

High coupling means modules depend too much on each other, making changes risky and complex, as seen in step 2 before refactoring.

How does refactoring improve coupling and cohesion?

Refactoring reorganizes code to reduce dependencies and focus module tasks, improving both cohesion and coupling, demonstrated in steps 4 to 6.

Visual Quiz - 3 Questions

Look at the execution_table at step 2. What is the coupling level of Module B?

A High

B Low

C Medium

D None

💡 Hint

Check the 'Coupling Level' column in row for step 2.

At which step does Module C achieve high cohesion after refactoring?

A Step 3

B Step 1

C Step 6

D Step 7

💡 Hint

Look at the 'Cohesion Level' for Module C after refactor in step 6.

If Module B had remained with high coupling, what would likely happen to the design?

A Modules would be independent

B Changes in Module B could affect others negatively

C Design would be easier to maintain

D Cohesion would automatically improve

💡 Hint

Refer to key_moments about problems caused by high coupling.

Concept Snapshot

Coupling and Cohesion Quick Reference:
- Cohesion: How focused a module is on a single task; aim for high cohesion.
- Coupling: How much modules depend on each other; aim for low coupling.
- High cohesion + low coupling = easier maintenance and better design.
- Refactor to improve cohesion and reduce coupling.
- Check modules individually and their interactions.

Full Transcript

This visual execution trace shows how software modules are evaluated for cohesion and coupling. Cohesion measures how focused a module's tasks are, with high cohesion meaning the module does one thing well. Coupling measures how much modules depend on each other, with low coupling meaning modules are independent. The trace evaluates three modules: Module A has high cohesion and low coupling, Module B has medium cohesion and high coupling, and Module C has low cohesion and medium coupling. After refactoring, Modules B and C improve to high cohesion and low coupling. Key moments clarify why high cohesion and low coupling matter and how refactoring helps. The quiz tests understanding of these concepts using the execution table. The snapshot summarizes the key points for quick review.