Coupling is a measure that measures the level of dependency

Solution

coupling is the degree of interdependence between software modules; a measure of how closely connected two routines or modules are; the strength of the relationships between modules

Coupling is usually contrasted with cohesion. Low coupling often correlates with high cohesion, and vice versa. Low coupling is often a sign of a well-structured computer system and a good design, and when combined with high cohesion, supports the general goals of high readability and maintainability.

Coupling can be \"low\" (also \"loose\" and \"weak\") or \"high\" (also \"tight\" and \"strong\").

Tightly coupled systems tend to exhibit the following developmental characteristics, which are often seen as disadvantages:

So, It is desired to be low to make it easier to maintain

its TRUE

As for coupling, it refers to how related are two classes / modules and how dependent they are on each other. Being low coupling would mean that changing something major in one class should not affect the other. High coupling would make your code difficult to make changes as well as to maintain it, as classes are coupled closely together, making a change could mean an entire system revamp.

All good software design will go for high cohesion and low coupling.