Object Oriented Analysis and Design with Applications (OBT) [Hardcover]

Some of the steps in becoming a good OOP programmer/architect are listed below (1 & 2 are often combined):

1. learn an OO language
2. learn OOP
3. learn how to *use* OOP

Step three is where this book and, for example, books on object-oriented design patterns (GoF) come in. Just because because you know what classes and inheritance are does not mean you will use them effectively. I cannot emphasise the importance of step 3 enough when architecting applications. If you are a coder, simply knowing OOP is fine, as an architect it is simply not enough.

In terms of organization, the book starts simple and builds on previous chapters in a very organized way. In the first chapter Booch delves into the philosophy of OOP and complex systems. This kind of broad introduction serves well as a way to show where OO analysis and design stand relative to other engineering disciplines.

The only problem I had with the book is the fact that it is a bit dated. It does not use UML (although what it uses is very similar) and even has a chapter devoted to client/server computing. (however, it also has a chapter on AI). If it were not for this its datedness, I would have easily given it 5/5.

Overall a great book from one of the father's of modern objected oriented analysis/design.

1. In 1994 when this book was published Java was in development and had no ways near the popularity it has today. (According to Cay Hortsmann Java did not burst onto the scene until late 1995)

2. Bertrand Meyer's book is great and contains valuable wisdom, but all of its examples are in Eiffel. While Eiffel is a great language what are my chances finding a job writing Eiffel.

But really all of the above comments are pointless. The fact of the matter is that the concepts in an Object-Oriented book should be language independent. However, to be most effective authors reinforce abstract ideas by including concrete examples. Which means the author must pick a language or write in pseudo code. Booch's book is a valuable reference to be used in learning how to apply Object-Oriented concepts to the analysis and design portion of the software development process. It is up to you to know your own problem domain or work with experts who do. I personally write software that deals with weapon trajectories and weapon effects and just because the book does not have any examples on this domain does note mean it is not valuable. The job of this book is to teach me how to think in terms of objects and how to find and design my classes and class hierarchies. It succeeds, Thanks Grady Booch.

I bought this book due to a positive comment in B. Stroustrup's "The C++ Programming Language" bibliography. I was not dissapointed. This book covers everything from terminology, to useful notations, to actual application of techniques.

I teach C++ as part of my job, and have found many design books to be shallow works which cover proprietary notations, with a few cookbook recipes thrown in. These books commonly show a lack of real development experience, and are more theory than practice.

This is not the case with this book, which combines work from many different sources. It also consistently includes references to alternative opinions when covering controversial material.

Mr. Booch stresses the need for intelligent, and sometimes ad hoc decisions which are based on good design principles, and are refined as a project evolves. But he doesn't stop there. He explains useful techniques and thought processes which are the primary tools of good OO A&D.

This is one of the best design books I have seen to date.