Coupling and cohesion in Software Engineering - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is coupling in software engineering?

Coupling is the measure of how much one module or component depends on another. Low coupling means modules work independently, which is good for easier maintenance.

beginner

Define cohesion in the context of software modules.

Cohesion refers to how closely related the tasks performed by a single module are. High cohesion means a module focuses on one task, making it easier to understand and maintain.

intermediate

Why is low coupling preferred in software design?

Low coupling reduces dependencies between modules, so changes in one module have less impact on others. This makes the system easier to update and less error-prone.

intermediate

What does high cohesion help achieve in a software module?

High cohesion helps a module do one thing well, improving clarity, reusability, and ease of testing.

beginner

Give a real-life example to explain coupling and cohesion.

Think of a car: the engine parts have high cohesion because they all work together to make the engine run. The engine and the radio have low coupling because they work independently; changing the radio doesn't affect the engine.

What does low coupling mean in software modules?

A Modules depend heavily on each other

B Modules work independently with few dependencies

C Modules perform many unrelated tasks

D Modules are tightly connected

Low coupling means modules have few dependencies and work independently.

Which of the following best describes high cohesion?

A A module focuses on a single task or related tasks

B Modules share many variables

C Modules are highly dependent on each other

D A module performs many unrelated tasks

High cohesion means a module focuses on one task or closely related tasks.

Why is high cohesion beneficial?

A It improves clarity and ease of maintenance

B It increases dependencies between modules

C It makes modules harder to understand

D It forces modules to do many unrelated things

High cohesion improves clarity and makes modules easier to maintain.

Which scenario shows tight coupling?

A Modules have clear, separate responsibilities

B Modules can be changed independently

C Modules perform focused tasks

D Changing one module requires changes in many others

Tight coupling means modules depend heavily on each other, so changes affect many parts.

In the car analogy, which pair shows low coupling?

A Engine and pistons

B Engine parts

C Engine and radio

D Radio speakers

The engine and radio work independently, showing low coupling.

Explain in your own words what coupling and cohesion mean in software design.

Think about how modules depend on each other and how focused their tasks are.

Describe a real-life example that helps you understand coupling and cohesion.

Use everyday objects or systems you know well.