Product Details
The Elements of UML(TM) 2.0 Style

The Elements of UML(TM) 2.0 Style
By Scott W. Ambler

List Price: $16.99
Price: $15.29 & eligible for FREE Super Saver Shipping on orders over $25. Details

Availability: Usually ships in 24 hours
Ships from and sold by Amazon.com

49 new or used available from $7.14

Average customer review:

Product Description

For all developers who create models using the Unified Modeling Language (UML) 2.x The Elements of UML(TM) 2.0 Style sets the rules for style that will improve your productivity - especially in teams, where understandability and consistency are critical. Coming from renowned UML expert Scott Ambler, the book furnishes a set of rules for modelling in the UML and describes a collection of standards and guidelines for creating effective UML diagrams that will be concise and easy to understand. It provides conventions for: Class diagrams; Timing Diagrams; Use case diagrams; Composite Structure Diagrams; Sequence diagrams; Interaction Overview Diagrams; Activity diagrams; Object diagrams; State machine diagrams; Package diagrams; Communication diagrams; Deployment diagrams and Component diagrams. The Elements of UML(TM) 2.0 Style sets the rules for style that will improve your productivity.


Product Details

  • Amazon Sales Rank: #198524 in Books
  • Published on: 2005-05-09
  • Original language: English
  • Number of items: 1
  • Binding: Paperback
  • 200 pages

Editorial Reviews

Review
"Just as Strunk & White's The Elements of Style provides rules of usage for writing in English, this text furnishes a set of rules for modeling in the Unified Modeling Language."
IEEE Computer

"It's fully loaded with information that can make your UML diagrams far better than most. That's because the author doesn't waste space. Once you get to the body of the book there are no blank pages, and few (if any) wasted words, just lots of recommendations for simple ways to improve your UML diagrams...In summary, this is an excellent book full of good advice on improving your UML 2.0 modeling."
Javalobby

Praise for Scott Ambler's previous books:

"...Scott Ambler's book delivers exactly what it promises--a robust look into building object applications."
Software Development on Building Object Applications That Work (Cambridge, 1998)

"...the best book I've read that covers the basic fundamentals of object-oriented software engineering and process. It is easy to understand and is a must read for those new to OO."
Mike Stefano, New York Life Insurance Company, on The Object Primer (Cambridge, 2001)

About the Author
Scott W. Ambler is a senior consultant of Ronin International, Inc., a software services consulting firm that specializes in software process improvement, mentoring, and training. He is also founder and thought leader of the Agile Modeling (AM) methodology and the Enterprise Unified Process (EUP). He is a popular international speaker, a regular columnist for Software Development magazine, and the award-winning author of several books, including The Object Primer 3/e, Agile Modeling, and Agile Database Techniques.


Customer Reviews

UML Style Redux5
With the release of UML 2.0 into the wild, it was inevitable that Ambler would update his Elements of UML Style book. Like its predecessor, this little book is more a companion than a teacher. You will not learn how to do UML modeling from this guide--that is not its intent--but you will learn how to make your UML models more readable and consistent. Ironically, books that do intend to teach you UML modeling do not talk about "goodness" or accessibility of the model's representation. This guide brings that balance to your use of UML.

There are many "gems" sleeping in his book. In his section on the Sequence diagram Ambler recommends putting the message text near the receiver side of the message arrow. This is not subtle: it makes the model significantly easier to read--especially when evolving the diagram in real-time on a white board. "Prefer Names over Types for Parameters" is another, and especially true when modeling from an analysis mindset rather than describing design. I could go on, but that would be redundant. Get the book. Read it. Consider his recommendations, and feel free to go in another direction if you can justify that direction is an improvement in clarity and communication.

Not everything Ambler says should be taken as "the way", of course. As an experienced modeler I have certain style preferences to which I gravitate, and which violate some of Ambler's precepts. In use case diagrams, for example, I always denote an arrowhead on the actor-to-use case association. I also note specific stereotypes on the actors of a use case diagram because not all actors in a system are equal in importance in the project lifecycle. But I follow, and have independently adopted, many of Ambler's recommendations. Indeed, I know that many of his recommendations are derived from the common usage of the modeling community, plus his own unique additions.

If you are just starting out with UML diagramming, this little guide will help you adopt some consistency as you navigate the new landscape of 13 diagrams in UML 2.0. Not all of those diagrams are equally important, either, and I was very pleased to see Ambler clearly stating his reservations about the Composite Structure diagram. Many of us wonder about the value of this offering in UML when other issues such as data modeling and UI modeling have been so prominently absent since UML's inception.

Certainly worth the price!4
As others have noted, this book is not intended to "teach" you UML, but instead to build on (and subsequently enhance) one's knowledge of the UML.

The Good: It serves as a quick reference for your UML diagrams. That being before (and during) your artifact creation, this book can be used as a "check-list" to ensure your modeling techniques are sound. I personally use it as a "bathroom" book, in that you can pick it up at any point and quickly derive information based on your current need.

The Bad: The physical size (not the volume) of the book is rather small. I prefer larger books, but that is my subjective opinion. Additionally, the examples Ambler uses are the same old "Online Ordering", "School Enrollment", "Sales Clerk", etc. he uses in other literature he's produced. No big deal, really-but it would be nice to see new examples to drive his point across.

All in all, I would definitely recommend this book to ANYONE interested in increasing their UML knowledge. And for $10.00 it is a real bargain! Just remember, if you are wanting to learn UML basics, this book is not for you.

For Intermediate to Advanced UML Modelers5
The goal of this book is to enhance your existing UML modeling skills, it is not to teach you UML. It assumes that you understand the fundamentals of the UML but now want to improve the way that you apply the UML in practice. By following the guidelines presented in this book, you will improve the quality and communication value of your UML diagrams.

The book also includes some tips for properly applying the UML notation.