Learning UML 2.0: A Pragmatic Introduction to UML 1st Edition

This book gives very good understanding of UML who don't know anything about it. Details are covered as a example

Unified Modeling Language (UML) is the best standardized way to graphically depict a complex software system. It makes a technical language of glyphs to portray software integrations so that large software efforts can be more easily understood by developers. Certifications exist that allow individuals to support UML professionally.As a developer, the main problem I have with UML is that it itself is complex, often too onerous for my efforts. I deal with complex software, but usually only on smaller teams where we can keep the software in our heads. Maintaining a complex web of diagrams can become a big chore whose value is not always evident.Recently, Mermaid markdown language has encourage me to use UML at a smaller scale. Instead of keeping thorough specifications on drawing tools, Mermaid contributes a language to describe my thoughts and automatically generate the graphics for me. Automated generation makes maintenance easier. Mermaid transforms UML into more of a simple communication tool instead of an intricate documentation tool.This book mainly uses Java to illustrate its concepts, but UML, like the concepts in the book, is language-agnostic. I work in a LAMP stack for web development, so perhaps Java-based developers might find this book more useful. The book also describes the finer aspects of the language that only UML experts will aspire to master. Overall, it provided me a helpful way to learn more about this language.

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!

Great book. A must to keep on hand in your library to look back upon when you need to reminder. Very happy to have it in my library.

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.

Excellent book. Entertaining, not distracting with formal details or innecessary stuff that only appears in the UML specification. This book will give you excellent practical insight on the stuff that matters in the day to day development using UML.

My perspective:Looking for a solid introductory book to UML. No financial investments in product or author.Overall:This book met my goal of obtaining an introduction to UML.Good:1. Better than the last book: "UML 2.0 In Action"2. Solid foundation covering many different types of diagrams, their uses, and notationSuggestions:1. Could do better describing the order the diagrams are typically constructed during the planning stages of a project. For example, after constructing the use case diagram, would you suggest creating the package diagrams or the activity diagrams? (The former is the second chapter, while the later is one of the last chapters.)2. As far as I can tell the book completely omits a discussion of UML modeling programs. It would be nice to at least mention a few of the popular programs. It does mention the limits of "some" modeling programs throughout the book. (Here is a list from wikipedia: [...])3. References the UML in a Nutshell book one too many times. It's quite distracting and humorous at times.

The manual was delivered quickly and in good condition. I was very satisfied. The content of the manual is enabling me to build on a critical business analysis skill.