Rating: 
Summary: It's not a book about UML !!!!!
Review: It's not a book covering UML. Moreover readers will just find a few paragraphs about UML. Otherwise it's a very good book talking about mapping OOAD notations to C++. It covers the whole of OOAD's notations and give C++ examples of implementation. Authors use abundantly Class-Responsibility-Collaboration (CRC) cards and not UML notations. Sometimes it's really hard to read; more explanations were necessary. I recommend this book for advanced C++ users, wanting to benefit by advice ( recommended approaches ) from big men as R. C. Lee and W. M. Tepfenhart.
Rating: 
Summary: There are many other excellent books compared to this
Review: This book is outdated (both first and second editions). It certainly does not teach you UML, it does not teach you C++, nor does it teach you OOAD the right way. I also found numerous errors, even in C++, supposedly their area of expertise.They confuse between OO technique and developmental process. They keep referring to development process as OO. Typically, OO is combined with UP in software projects. This is not mentioned anywhere. They also fail to see the forest, instead keep focussing on the trees. For example, there is a top-down analysis approach, and another is a bottom-up analysis approach. You can also do it both ways and come to the middle. Not a mention about this in this book. They keep preaching about their beliefs. That is annoying. Instead of saying, bottom-up analysis gives rise to more reusable class structure, they go on and on about Taoist philosophy. Lot of outdated stuff also in there. Who cares for Structured English. On the whole, reading this book will not help, will confuse you, and could potentially get you started in the wrong direction as an OO programmer/analyst. There are numerous other excellent books on the market that focus on the OOAD and software development lifecycle. Don't bother buying this one. The title is also nonsense. There is very little UML in this book. There is very little C++ in this book. It does not show you how to effectiely use C++ when you are grappling with certain design decisions. No mention of design patterns and how they could be represented effectively in C++. Can't find much virtue in this book honestly. Waste of paper.
Rating:
Summary: Not much UML just the title
Review: This book lacks lots of information about UML. It is just a summary of cases where authors used UML but not much information about UML. Also lots of general information about OO. As a C++ book it doesn't do much either. One chapter dedicated to the principles of C++. It is more a book geared for beginners the title is very misleading. Authors should have been more honest than just trying the old trick or bait and switch. As a OO book it is OK but it is not an UML book.
| 
