This book is good if you are familiar with the concepts of OO and abstraction but not really sure how it all fits into UML and how to apply it. Richter spends time detailing examples. If you want an A-Z guide on UML this is not the book. Its about how to use the methodology. It is not overly verbose, so you have to study the book. The examples are simple and usually this is a disadvantage because it lacks "real world" applicability. But Richter has used simple examples to highlight critical points about a designing OO systems. So its definitely not light reading.

With very little understanding of UML and its many facets i still found this book to be quite informative and educational. It brings together basic techniques that you can use in the process of analysis and design before you start to code. The book is logically sequenced and builds your knowledge on each chapter. Richter's writing style is concise and to the point and assumes you know how systems are coded.

One of the strengths of this book is that Richter shows you how a particular technique is used and also in many cases when not to use it and why. One other review criticise this book on a minor point that is subjective and i think is dwarfed by the strengths of this book. This book is a summation of Richter's experience of analysis and design. Read it and you will learn.

The book "Designing Flexible Object-Oriented Systems with UML" is absolutely brilliant.I have just ventured into the UML field,I found the articles lucidly explained. I found the Design Problems and Object-Oriented Solutions very helpful,it's given me a fantastic start in a very small timeframe,Something like a rocket firing off at the countdown of 10.

I have gone thru the device polling problem. [ Design Problem 1 You must develop software that allows clients to periodically check for changes in the status of devices in a network. ]

Just from one sentence ,The way the problem was tackled can teach a layman to design a given system.

Cheers

Quite simply, you can dispense with a shelf of 'other' UML and OO design books. Concisely written and clearly illustrated, this volume is indispensable. Richter summarizes the best analysis methods and diagramming techniques of Booch, the three amigos, Bob Martin, Larman, Coad and others. It is all right here. The companion to this text is, of course Fowler's "UML Distilled" (and ... well ... OK, one more ... Booch's "UML User Guide". An excellent reference and modeling resource in a single tome ... covers a lot of ground with copious examples. (And if you are STILL hashing around with Uses vs. Extends (v1.1), Richter's examples are the cleanest anywhere.)

Quite simply, you can dispense with a shelf of 'other' UML and OO design books. Concisely written and clearly illustrated, this volume is indispensable. Richter summarizes the best analysis methods and diagramming techniques of Booch, the three amigos, Bob Martin, Larman, Coad and others. It is all right here. The companion to this text is, of course Fowler's "UML Distilled" (and ... well ... OK, one more ... Booch's "UML User Guide". An excellent reference and modeling resource in a single tome ... covers a lot of ground with copious examples. (And if you are STILL hashing around with Uses vs. Extends (v1.1), Richter's examples are the cleanest anywhere.)

I found Charlie's book very informative and useful to our design efforts. The book is very good as a learning tool for anyone who has not had exposure to UML. We are going to use this book as a training tool for both our technical team and our Product Managers (Business Partners). This is definitely a book you want in your library.

This book is a terrific tutorial on UML and includes the guidelines that I needed on developing class diagrams as well as class diagramming notation. The order processing example was great in helping me to understand these concepts. The same example was used to give detailed instruction on developing dynamic diagrams. This example provided a coherent transition from static to dynamic design which worked well in helping me understand the concepts. However, it really helped that other examples such as an elevator control system were used which helped me see how to apply the concepts to different systems.

I found the coverage of flexibility guidelines to be of particular interest in my job and have recommended that everyone in my group have a copy of this book as a reference in our new project. As a 15 year veteran in the industry I found this to be the best coverage of UML that I've found.

This book is a terrific tutorial on UML and includes the guidelines that I needed on developing class diagrams as well as class diagramming notation. The order processing example was great in helping me to understand these concepts. The same example was used to give detailed instruction on developing dynamic diagrams. This example provided a coherent transition from static to dynamic design which worked well in helping me understand the concepts. However, it really helped that other examples such as an elevator control system were used which helped me see how to apply the concepts to different systems.

I found the coverage of flexibility guidelines to be of particular interest in my job and have recommended that everyone in my group have a copy of this book as a reference in our new project. As a 15 year veteran in the industry I found this to be the best coverage of UML that I've found.

I'm not sure why I even bothered with this book. It gives little to clarify the use of the many tools that UML offers, and little to help you understand either where or how to design flexibility into your systems. It felt more like a collection of disjoint ideas with little practical experience behind it (perhaps some classroom or academic experience), dubious interpretation and semantics added onto the UML, a hokey description of things like activity diagrams and refinement.

I found many reasons why I would not want to be on a project that designed based on this book. e.g. I would never defer consideration of external systems in use-case interactions to design-time, or decide on association directions as recommended here, or either use design patterns the way this book does. Some of the designs I would end up with would be terrible.

Overall not impressive and only marginally useful. As a point of reference, I am moderately experienced with OOD.

Practical and understandable. Very good read - espeicially for the beginner.