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 standard system that must succeed but won't ruin the company if delayed. Surviving Object-Oriented Projects
Before writing a single line of code, identify the nature of your project to set realistic expectations and staffing: Avoid deep inheritance hierarchies (more than two levels
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. Before writing a single line of code, identify
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.