Surviving Object-oriented | Projects

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

The most common cause of OO project failure is the "big bang" release. Surviving projects focus on: 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

Building a successful object-oriented (OO) project is less about mastering syntax and more about navigating the human and structural "holes" that swallow most software initiatives. Based on the principles in Alistair Cockburn's seminal work, Surviving Object-Oriented Projects , and modern industry insights, Based on the principles in Alistair Cockburn's seminal

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