WBJECA 2025 — Computer PYQ

In software engineering, Coupling refers to the degree of interdependence between software modules. A primary goal of good software design is to achieve Low Coupling, which means that modules are as independent as possible. Reducing dependencies makes the system easier to maintain, test, and understand.

To visualize the concept, consider the dependency intensity ($I$) between two modules:

$$I_{Coupling}\propto \text{Number of direct dependencies}$$

When we design software, we aim to minimize this intensity:

$$\text{Goal: }\min (I_{Coupling})$$

Comparison with other concepts:

• Cohesion: Refers to the degree to which the elements inside a single module belong together. High cohesion is desirable (meaning a module performs one well-defined task).

• Modularity: The broader principle of dividing a system into separate, interchangeable modules.

• Abstraction: Hiding complex implementation details and showing only the necessary features of an object or system.

In summary, while Cohesion focuses on what is inside a module, Coupling focuses on the relationships between modules. High-quality software design is often described as having High Cohesion and Low Coupling