So let’s see, Information Expert guides us to assign responsibility to the best class, but how? Why?
One attribute the Expert regards highly is the principle of Low Coupling. Low Coupling is a barometer of how strongly one element is connected to, or has knowledge of, or depends on other elements. Coupling can be synonymous to dependency. If there is coupling between elements, the when the depended-upon element is changed, the dependent can also be affected. Low Coupling is one of the most crucial principles in software design. So how do we gain low coupling, meaning how do we reduce the impact of change? The most primitive and efficient answer to that is to assign responsibilities so that unnecessary coupling remains low. When determining that, we always have numerous alternatives; we should weigh-out our options and choose the best one according to this principle. Low coupling reduces time, effort, and defects in modifying software - words that sounds music to a developer’s ears.
Recent Comments