Pitfalls of Object Oriented Development

Like so many facets of science, Object-Oriented programming ( OOP) has been overhyped. With so many calling it the silver bullet of program development, it is reassuring that there are voices calling for the triumph of reason. As one who has made the transitions BASIC => FORTRAN => Pascal => C =>C++=> OOP, I am well aware that while OOP is an enormous aid in creating robust software, it does not cure all diseases. Like all tools, if not property used, the cure can be worse than the disease. Webster does an excellent job here in pointing out the locations of many of the land mines inherent in making the transition to OOP. <br> Leading off with a brief introduction to OOP that can be skipped without consequence, the heart of the book insists of 10 chapters. <br><br><p> 1)Conceptual Pitfalls <br> 2)Political Pitfalls<br> 3)Management Pitfalls<br> 4)Analysis and Design Pitfalls<br> 5)Environment, Language and Tool Pitfalls<br> 6)Implementation Pitfalls<br> 7)Class and Object Pitfalls<br> 8)Coding Pitfalls<br> 9)Quality Assurance Pitfalls<br> 10)Reuse Pitfalls <br><br> These chapters clearly cover the entire sequence of software development.<br> Each pitfall is split into several sections. <br><br> a)Title and explanation <br> b)Symptoms<br> c)Consequences<br> d)Detection<br> e)Extraction<br> f)Prevention<br> <br> In all cases, the advice is practical, not theoretical. While it may be difficult to implement the advice, it is very hard to argue with it. <br> One of the most valuable books devoted to OOP, this book should be required reading for everyone in software development using OOP. If all groups planning to use OOP were to make their first task a group study of this book, many projects that would otherwise fail would instead be a success. <br><br> Published in Mathematics and Computer Education, reprinted with permission.

We still recommend this book to our clients. Everyone talks about Object-oriented programming as though it were some sort of "silver bullet," but OO programming is still just a tool - it can be used or misused at the risk of your project's success.

Despite its title, not much in this 250-page book is actually about object-oriented technology. If you substituted "client-server" or just "large systems" for "object oriented" most of the content would still apply.Despite its lack of specific O.O. guidance, the advice Webster gives us is sound. Project managers and others responsible for important software development projects, object-oriented or not, should read and reread it. The style is friendly and readable. The book ends with a good bibliography of both project-management and object-oriented analysis topics.

The author presents an easy to follow guide for managers embarking on a development project. Not only does he outline pitfalls, but presents strategies to correct problems before they get out of hand.