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

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 Surviving Object-Oriented Projects

Surviving Object-Oriented Projects: Cockburn, Alistair - Amazon.com Avoid deep inheritance hierarchies (more than two levels

Develop in small, testable chunks that result in running code. Alistair - Amazon.com Develop in small

The survival of a project often hinges on social factors. Research shows that many failed projects are saved only when new "core developers" step in to assume ownership.

The most common cause of OO project failure is the "big bang" release. Surviving projects focus on: