- Amazon Student members save an additional 10% on Textbooks with promo code TEXTBOOK10. Enter code TEXTBOOK10 at checkout. Here's how (restrictions apply)
The Elements of UML(TM) 2.0 Style Paperback – May 9 2005
|New from||Used from|
Special Offers and Product Promotions
Customers Who Bought This Item Also Bought
No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.
To get the free app, enter your e-mail address or mobile phone number.
"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."
"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."
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)
For all developers using the Unified Modeling Language (UML) 2.x this book sets rules for style that will improve productivity - especially in teams, where understandability and consistency are critical. It does not tell you how to create the models, but instead describes how to create clean, easy-to-understand diagrams.See all Product Description
Inside This Book(Learn More)
Most Helpful Customer Reviews on Amazon.com (beta)
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.
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.
Book is riddled with references to diagram objects that are not there. Another one is #113 where the author refers to "itemNumber" which is not present in the diagram. Unforgivable for this type of reference.
Have the other reviewers not read past page 50?
Spelling mistakes are also not lacking (enough to cause you to pause and think if you've missed something)!
Look for similar items by category
- Books > Computers & Technology > Computer Science > Software Engineering
- Books > Computers & Technology > Programming > Languages & Tools
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Object-Oriented Design
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > UML
- Books > Computers & Technology > Software
- Books > Textbooks > Computer Science & Information Systems > Object-Oriented Software Design
- Books > Textbooks > Computer Science & Information Systems > Programming Languages
- Books > Textbooks > Computer Science & Information Systems > Software Design & Engineering