Designing Object Oriented C++ Applications Using The Booch Method (Hardcover)

~ (Author) "Before we get into subject of what OOD is, I would like to address a number of questions that are commonly asked by people who..." (more)
Key Phrases: Pot Removed, Liskov Substitution, Circuit Security Operator Zone Control (more...)

Editorial Reviews

Product Description

Taking on a global orientation to software programming, this practical guide offers scores of tested methods for using the C++ programming language with object-oriented design techniques for creating a variety of applications and solving a host of programming problems.

From the Publisher

A practical, problem-solving approach to the fundamental concepts of Object Oriented Design and their application using C++. This book is written for the "engineer in the trenches". It is a serious guide for practitioners of Object-Oriented design. The style is narrative, and accessible for the beginner, and yet the topics are covered in enough depth to be relevant to the consumate designer. The principles of OOD explained, one by one, and then demonstrated with numerous examples and case studies.

See all Editorial Reviews

Product Details

• Hardcover: 512 pages
• Publisher: Prentice Hall; 1st edition (February 15, 1995)
• Language: English
• ISBN-10: 0132038374
• ISBN-13: 978-0132038379
• Product Dimensions: 9.4 x 7 x 0.7 inches
• Shipping Weight: 2.2 pounds
• Average Customer Review: 4.7 out of 5 stars  See all reviews (10 customer reviews)
• Amazon.com Sales Rank: #543,306 in Books (See Bestsellers in Books)

  Popular in this category: (What's this?)

  #29 in

  Books > Computers & Internet > Programming > C > Objects

Customer Reviews

Most Helpful Customer Reviews

5 of 5 people found the following review helpful:

5.0 out of 5 stars Essential, thorough and immensely pracitcal guide to OOD, April 15, 1997

By A Customer

I have used this book in the years since it was first pubished and have reccommended it on numerous occasions. It tackles the chasm that seperates idealistic design from realistic implementation. I refer to it no matter which OO design methodology I am using, no matter which OO language a system is being implemented in. I have found that the difference between the designs of people who exercise the principles of this book and those who don't are noticeable - especially during the design of large systems

3 of 3 people found the following review helpful:

5.0 out of 5 stars My "Aha!" Moment for O-O Programming, January 28, 2002

By A Customer

Even if you don't know C++ or use the Booch method, this is the best work I've read on how to engineer software systems. The principles presented in this book apply regardless of computer language or design notation. And, while the book is geared to O-O, those priciples, I think, apply to software design in general. When you finish this book you will think "Of course! Why would you do it any other way?!". Despite over 20 years experience is software design and programming (including 10 in O-O), this book was the "Aha!" moment that made me truely understand how to design and build software systems. I can't reccommend it highly enough. Now, if Martin would just do the same book using Java and UML...

5 of 6 people found the following review helpful:

4.0 out of 5 stars Well done for its time, but showing its age, July 22, 2002

By A Customer

Of course, anyone up on the world of software development can tell that this book is long-in-the-tooth just by the title. Even Grady Booch doesn't use the Booch method anymore.

Robert Martin includes one of the best sections on software metrics you are going to find anywhere. His discussion of coupling is clear and usable. He was a little too zealous when he "defined" representational objects as "not-OO" because they didn't fit on his "main sequence." His main sequence analysis is useful, but he's a little too rigid about it.

His definition of the famous "Open-Closed" principle is obscure, but he makes up for it with copious examples.

I really must praise his Security System example as one of the best thought out examples in the literature. His use case analyses, though, are really not up with the times, and were not very well explained in the first place.

Unfortunately, there aren't a lot of folks writing better books in the time since. For use cases, Check out Alistair Cockburn. For modeling, pretty much anything post 1999 from Rational Software will give you better method introductions. Read this book, though, for examples of how even big projects can be done well.