"Since its original introduction in 1997, the Unified Modeling Language has revolutionized software development. Every integrated software development environment in the world--open-source, standards-based, and proprietary--now supports UML and, more importantly, the model-driven approach to software development. This makes learning the newest UML standard, UML 2.0, critical for all software developers--and there isn't a better choice than this clear, step-by-step guide to learning the language." --Richard Mark Soley, Chairman and CEO, OMG

If you're like most software developers, you're building systems that are increasingly complex. Whether you're creating a desktop application or an enterprise system, complexity is the big hairy monster you must manage.

The Unified Modeling Language (UML) helps you manage this complexity. Whether you're looking to use UML as a blueprint language, a sketch tool, or as a programming language, this book will give you the need-to-know information on how to apply UML to your project. While there are plenty of books available that describe UML, Learning UML 2.0 will show you how to use it. Topics covered include:

• Capturing your system's requirements in your model to help you ensure that your designs meet your users' needs

• Modeling the parts of your system and their relationships

• Modeling how the parts of your system work together to meet your system's requirements

• Modeling how your system moves into the real world, capturing how your system will be deployed

Engaging and accessible, this book shows you how to use UML to craft and communicate your project's design. Russ Miles and Kim Hamilton have written a pragmatic introduction to UML based on hard-earned practice, not theory. Regardless of the software process or methodology you use, this book is the one source you need to get up and running with UML 2.0. Additional information including exercises can be found at www.learninguml2.com.

Russ Miles is a software engineer for General Dynamics UK, where he works with Java and Distributed Systems, although his passion at the moment is Aspect Orientation and, in particular, AspectJ. Kim Hamilton is a senior software engineer at Northrop Grumman, where she's designed and implemented a variety of systems including web applications and distributed systems, with frequent detours into algorithms development.

Amazon.com® Reader Reviews (Ranked by Helpfulness)

Average Amazon.com® Rating:  Based on 15 Ratings

A great book, not just for Java programmers! - 2008-06-07
Reviewer Rating:
I'm a junior Java programmer and the main reason why I came into contact with UML is because some of the major Java IDE's like Sun Java Studio and NetBeans have fully adopted support for UML modeling. Even though the tutorials on the Sun and NetBeans website give you a very good heads up and despite the fact that there are many UML tutorials available on the web I wanted more. Both a learning guide as well as some good reference.

And thats what I found in Learning UML from O'Reilly. What I like best about this book is that even though it covers the entire UML 2.0 spectrum it doesn't try to cover every little detail which don't add to the learning experience. Instead it gives you clear links for further reading or browsing (for example; it covers some of UML's history and gives you links for more detailed stories).

Another very important part for me is the way the book is setup. It seperates the different diagrams and follows a very logical order. From Use Case to Activity, Class (both regular and advanced), Object, Sequence, Communication, Timing, Component, State and Deployment. And because each chapter covers one diagram (with the exception of the class diagram which covers 2 chapters) its very easy to use this book both as learning tool as well as reference.

And the reason why I'm writing up this review.. This book assumes that the reader is already somewhat familiar with Object Oriented (OO) programming as well knows a little about Java. Examples where they show how some code snippets functionality are being displayed in a model are based on Java. However, despite that detail it doesn't result in a book which is only usable for Java (-like) programmers.

So summing up: A great book to learn UML and use as reference.

Best UML book for beginner - 2008-03-08
Reviewer Rating:
I've read a couple of other books that talk about UML, but they seem to just skim the surface and try to talk simple to you. This book is truly for someone who wants to learn about UML and how to use it properly.

I recommend reading through the whole book once quickly and then go back and read it again carefully. I believe that's the best way to learn the details presented in this book.

Quick read - 2009-08-31
Reviewer Rating:
It's a great over view of UML and design practices. This book is what it says it is, an introduction to designing with UML. If you have never worked with UML 2.x before then get this book. If you have already worked with UML and want a reference manual or something more in depth about design patterns and methods, go with something else. Although you could still use this book as a pseudo reference, it suggests other references for further reading on certain topics.

One thing I would have liked was to have exercise suggestions at the end of each chapter as a way to practice.

One the of best Printed UML Tutorials - 2008-12-22
Reviewer Rating:
I knew little about UML and its Diagrams before this book.

This book explains you most of the fundamental concepts in UML, most importantly, the relationship between these diagrams and concepts.

Wording is concise, yet precise (as a primer book on UML). Now I can use UML designing my software project!

Great Book for UML dummies! 5 Stars!

Good overview of UML 2.0 - 2008-10-09
Reviewer Rating:
I was looking for a way to present to a reviewing committee an educational video game which I am designing. "Learning UML 2.0" was at the right level of detail to show me what diagram types I might use.

The book is right for a person who taken a course in Java or C++ where you do many small problems, and now you need a plan for outlining a larger project. I think the book would be very difficult for anyone who had not programmed in Java or C++.

Many years ago I had vacillated among the notations of Rumbaugh, Booch and Jacobson. It is satisfying to see their ideas combined in a common notation.

Reading this book before and during an object-oriented design project will alert you to problems before they become errors.

Browse Similar Topics

Top Level Categories:
Programming
Software Engineering

Sub-Categories:
Programming > UML
Software Engineering > OOP
OOP > Methodology
OOP > Use Cases/Requirements
Software Engineering > UML