As a matter of fact I'm not an UML fan nor I particularly favour unified process. Indeed, I'm much more into Agile Development and XP.

The authors do not try to explain why unified process should be better than other processes. They just describe the method: It's up to the reader to decide which parts of the method are good or bad for his job. The reader is not bored with long enthusiastic comments on how he will be a more capable engineer after learning UML and UP. Unified Process is described in an unbiased and precise way: even those who do not favour UP may gather new and interesting ideas to incorporate in their development method.

The approach on UML is even more interesting. The basic ideas is that graphics should be a view, but what matters is text (which *is* something that the UML creators *did* think). Far to many lesser books focus on diagrams and miss to explain the interesting part is their semantics and their descriptions. Indeed, I try not to use UML unless I'm rather sure it's the best way to express a given concept: this book is a helpful reference on how to write correct and practical specifications using UML.

This is a great useful book.

This book gives a good introduction into modern software enigeering and I think that especially the first chapters about basics in object orientation and how the whole process works should be read by every person participating in a software project. I think these chapters are also worth reading for non computer science people.

This book gives a good introduction into modern software enigeering and I think that especially the first chapters about basics in object orientation and how the whole process works should be read by every person participating in a software project. I think these chapters are also worth reading for non computer science people.

Before reading this book I read "The Unified Modeling Language User Guide". I can say that "The Unified Modeling Language User Guide" is about the theory and "UML 2 and the Unified Process..." 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.

UML has grown. A few years ago, when UML was just getting accepted, a book on how to use it would have been much thinner. 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.