Decoupling - The Basics

The next item is decoupling. And as we all know, coupling is bad for maintenance reasons. A coupling two responsibilities that don't belong together just introduces complexity and which we can avoid. So de coupling tries to reduce the dependencies among the responsibilities,. assuming the ties are on calculated in individual classes and components. Usually an inter phase, at least the inter phase and its implementation are separated. But here we also discuss about general responsibilities, having then them separated into individual artifects. This is based on separation and abstraction as basic mechanisms. Typical examples include delegation or strategy, a factory and but to me, also tod the general architectural workf of de coupling.