Problem Statement
Which characteristic describes a software design with low coupling?
Explanation
Low coupling implies modules depend little on others, so you can modify one without triggering cascade changes. This supports maintainability and agility.
Practice Sets
This question appears in the following practice sets: