Summaries and Customer Reviews are supplied by Amazon.com

This book begins by outlining a basic process of software design using iterative, object-oriented techniques. The case study used for this text is a point-of-sale (POS) system, a helpful real-world example. The book constructs use case diagrams and basic conceptual and class models for this system. The author then adds sequence diagrams to show how the POS system will do its processing and collaboration diagrams to show how objects will interact with one another. The author uses standard UML diagrams to document the design.

When it comes to refining class design, the author's experience with patterns really shines. His General Responsibility Assignment Software Patterns (GRASP) suggest guidelines for designing classes that work together effectively. Larman believes that the ability to assign responsibilities to classes effectively is one of the most important aspects of good object-oriented design. His patterns allow this to happen and provide an interesting contribution to the design process. (The author also introduces more widely used software patterns to enhance the design process.)

When it comes to coding the design, Java is the programming language of choice for this text. Further chapters discuss how to refine an initial design using an iterative process of software engineering. While it's unlikely that readers will adopt Larman's approach to software design in its entirety, his guidelines--and application of patterns to class design, all documented using UML--make this a worthwhile text for the more experienced reader. --Richard Dragan

Average Customer Rating:

Examples are not good	Customer Rating:
This book is good overview for UML however examples given are too easy and not comprehensive enough to explain the subject.

Great work Craig Larman!

Customer Rating:

This is one of my MOST favorite books. I always have it on my table whenever I am working on the design and analysis phase of the development. I'll strongly recommend it to anyone sincerely wish to understand the concepts of OOD, UML and design patterns, and particularly applying the design patterns. Craig Larman is a master author, he makes everything easy and straightforward to follow as if he could understand the mind of the reader. This book is definitely a MUST HAVE.

The BEST book for learning OO design

Customer Rating:

This book started me off in the right direction many years ago. When Grady Booch was espousing starting off with noun lists and static models and then creating the dynamic models and reconciling them against the static model ad infinitum, Larman proposed starting with the dynamic models and letting the static model flow from there. Following Larman's approach you will design software that directly solves the problem, not a huge object framework that is usually outdated before it even gets completed. Flowing directly from the use cases, this methodology is a natural step towards service oriented architectures. And it's a very clear tutorial on UML to boot.

Great textbook on Object Oriented Analysis and Design	Customer Rating:
I taught an Object Oriented Analysis and Design course at college using this book. It was the ideal textbook. No book on OOAD I know comes close to it. I think the negative reviews here were decieved by the title. This book doesn't teach UML and Patterns it teaches Object Oriented Analysis and Design.

The Rosetta Stone for Applying UML	Customer Rating:
This book is more about the identifying and satisfying the dependencies that are such stumbling blocks for new or naive practioners of OO design with UML. Although I had attended UML courses and read other OO and UML books, applying UML and gaining benefit from doing so seemed impossible until I read this book. This book communicates something I never found in other OO/UML books I've read.