Surviving Object-oriented Projects Official

Instead of modeling the entire world, plan by feature and build a list of tangible functionalities to deliver. 3. Invest in "Object-Think" Over Tools

A standard system that must succeed but won't ruin the company if delayed.

Develop in small, testable chunks that result in running code. Surviving Object-Oriented Projects

Focus on picking nouns for classes and verbs for methods to stay close to the actual business problem.

Many teams transition to object technology expecting a "silver bullet" for productivity, only to find themselves trapped in refactoring loops or complex inheritance hierarchies that make the codebase brittle. To survive, you must treat the project not just as a technical challenge, but as a management and cultural shift. Instead of modeling the entire world, plan by

Avoid deep inheritance hierarchies (more than two levels is often "brittle") and prefer composition to keep the system maintainable. 4. Manage the Human Element

A small, elite team tackling a highly difficult, isolated problem. Develop in small, testable chunks that result in

Organizations often spend thousands on CASE tools while neglecting the developers' mindset. Training developers in "object-think"—the ability to model problem domains effectively—is the single most significant cost but also the highest predictor of success.