OO and Creating Changable Systems

Inevitably, a valuable system is forced to change. The system is altered, again and again, to provide additional value. This altering takes the system in directions that were not envisioned when the system was created.

Given that OO development is well suited to dealing with the inevitable change, why are so many organizations not harnessing the power that OO provides for creating these changable systems?

Could it simply be ignorance? A lack of knowledge and training? Underestimation of the paradigm shift needed to truly understand and implement OO systems?

In future posts I'll elaborate on the tenets that make up the basis of my understanding of OO development:

1. Encapsulation
2. Low Coupling
3. High Cohesion
4. Separation of Concerns