What is the difference between cohesion and coupling in software design?

Can you explain the difference between cohesion and coupling in software design?

Sure! Cohesion refers to how closely related and focused the responsibilities of a single module are, while coupling refers to how dependent modules are on each other.

Why is high cohesion important?

High cohesion is important because it makes modules easier to understand, maintain, and reuse. It leads to better organization of code.

And what about low coupling?

Low coupling is desirable because it reduces dependencies between modules, making the system more flexible and easier to modify.

Can you give an example of high cohesion and low coupling?

Certainly! A class that handles user authentication is an example of high cohesion. If it interacts with a database but doesn't depend on other unrelated classes, it demonstrates low coupling.