The Elements of UML(TM) 2.0 Style

UML 2.0 in a Nutshell (In a Nutshell (O'Reilly))

Applying UML and Patterns : An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition)

UML Distilled: A Brief Guide to the Standard Object Modeling Language, Third Edition

Uml

UML 2 and the Unified Process : Practical Object-Oriented Analysis and Design (2nd Edition) (Addison-Wesley Object Technology Series)

Format: Paperback
Author: Jim Arlow
ReleaseDate: 27 June, 2005
Publisher: Addison-Wesley Professional
Rating:

Practical approach to OOAD with UML
I can say that "The Unified Modeling Language User Guide" is about the theory and "UML 2 and the Unified Process. Before reading this book I read "The Unified Modeling Language User Guide".. . " is about practice.

I think that both books are must for UML beginners and reference for the UML professionals.

In "UML 2 and the Unified Process. . " authors show UML in action within the Unified Process, a framework for software development. The book describes how to analyze and design a software by giving a real example. Given examples are also complete and available online.

The language of the book is simple (easy to understand) and its contents is organized very well.

This book gave me an insight about the UML and also introduced me to the Unified Process. I would recommend it with 5+ stars to everybody.

a natural union of UML, UP and OO design
A few years ago, when UML was just getting accepted, a book on how to use it would have been much thinner. UML has grown. But the successful broad uptake of UML led to its semantic notation being expanded. What the authors give us here is a thorough exposition of UML 2. 0 and how to use it.

As you might expect, there are numerous examples in UML. Which, to many readers, might be more understandable than a mere abstract diagram. But the book is more than just about explaining the UML semantics. It also goes into the Unified Process for running a project, and how this can be documented in UML. By doing so, the authors hope to better enable an understanding of both.

There is also something else, related to the above, but sufficiently different and important to warrant notice. If you write in any object oriented language, it requires certain skills in designing classes and how they interact. Part 4 of the book concerns these issues, which it discusses under the rubric of "Design". A good explanation of the basic concepts. Like inheritance versus aggregation, or inheritance versus interfaces. Or why the lack of multiple inheritance in a language like C# or Java is not necessarily a deficiency.