The book begins with a critique of today's software (which is expensive and often delivered behind schedule). The authors tour the history of software engineering, from early structured analysis to object-oriented techniques. Several sections of this book cover the ins and outs of defining objects, including identifying each object's responsibilities, static, and dynamic behavior (where the UML statechart, collaboration, and use case diagrams are used to document its behavior and iterations.)

Interestingly, the authors introduce the notion of "rules"--code executed with events--used with C++. (One of the authors has even developed a language enhanced with rules for C++ called R++.) The remainder of the book looks at how to design and implement objects, specifically in C++. The case study is a Breakout type of video game. Though not especially concerned with the details of UML, there's some considerable C++ expertise on display in this intelligently written title. --Richard Dragan

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.