Surviving Object-oriented Projects [FREE]

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

Focus on picking nouns for classes and verbs for methods to stay close to the actual business problem. Surviving Object-Oriented Projects

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. Avoid deep inheritance hierarchies (more than two levels

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

Before writing a single line of code, identify the nature of your project to set realistic expectations and staffing:

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