| ||||||||||||||||||||||||||||||
|
There is a newer edition of this item:
|
The first edition of Object-Oriented Design with Applications was instrumental in making object-oriented technology a practical reality--hundreds of projects applied Booch's notation and process to complex problems in diverse domains. In this eagerly-awaited new edition, Grady Booch draws upon the rich and varied results of these projects to offer improved methods for object development and a new, unified notation. With numerous examples, all of which are now implemented in C++, Booch illustrates essential concepts, explains the method, and shows successful applications in a variety of fields. You'll also find pragmatic advice on a host of issues including classification, implementation strategies, and cost-effective project management.
Features of the New Edition:This is the essential reference for anyone who implements or manages object technologies, or who wishes to begin exploration of this important new paradigm.
Product Details
Would you like to update product info or give feedback on images?
|
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
62 of 66 people found the following review helpful:
4.0 out of 5 stars
A book on *using* OOP,
This review is from: Object-Oriented Analysis and Design with Applications (2nd Edition) (Hardcover)
After reading some of the less flattering reviews of this book, it seems that many reviewers were expecting a book on object-oriented programming in general. If you want to learn how program, this is not the book for you. This book is about *using* object-oriented techniques to architect systems. The content you should take away from it is entirely independent of any particular language. Some of the steps in becoming a good OOP programmer/architect are listed below (1 & 2 are often combined): 1. learn an OO language 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.
47 of 50 people found the following review helpful:
5.0 out of 5 stars
A beacon of light in a world of darkness,
This review is from: Object-Oriented Analysis and Design with Applications (2nd Edition) (Hardcover)
After reading the other reviews I have a few comments.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.
21 of 23 people found the following review helpful:
3.0 out of 5 stars
Too many words,
Amazon Verified Purchase(What's this?)
This review is from: Object-Oriented Analysis and Design with Applications (3rd Edition) (Hardcover)
This book's reputation as one of the bibles of OOAD is probably deserved because (to someone relatively new to it) the essentials seem to be thoroughly covered. It just seems too much like wading through muck to find them.
The problem begins at the very beginning; on the first pages of the preface. In describing changes between publication of the second edition and this third edition, the author lists "robots are cruising on the surface of Mars" and "Personal hovercraft are available." Tongue-in-cheek? Unfortunately, no, unless it's firmly planted there. As the book continues, the reader all too often wants to start skimming as paragraph after paragraph, sometimes page after page, of non-essential prattle clouds the essentials. For journeyman designers and developers, sections on the topology of old-fashioned procedural languages, on the importance of documentation, task planning, release planning (twice!) and more may be frustrating drags on learning the essentials of thinking through a good design and taking it to the doorstep of implementation. A highly-simplified greenhouse application is used for examples throughout the first part of the book, leaving too many more-common scenarios unexplored and occasionally trapping skimmers who have not captured every concept in the design of that application along the way. Late chapters illustrate some concepts with (finally!) other applications including an all-important (for many of us) web application as well as applications for satellite tracking, data aquisition for a weather station, artificial intelligence, and a control system for traffic management. Interesting, but again wordy and by the time you get there you're exhausted! I did learn from this book, but I'm still looking for The Book that efficiently teaches OOAD, and I've read four or five already. So far I've learned more from a couple of implementation-level books: Martin Fowler's superb book Refactoring: Improving the Design of Existing Code, and his UML Distilled. These have been very instructive in part because Fowler's style is lean and very clear, un-clouded by distracting non-essentials. I've just ordered Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development by Craig Larman. Fingers are crossed, maybe that will be The Book.
Share your thoughts with other customers: Create your own review
|
|
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
|
This product's forum
Active discussions in related forums
Search Customer Discussions
|
Related forums
|