 Trade In this Item for up to £1.35
Get an extra £5 when you trade in books worth £10 or more until June 30, 2012. Trade in The Elements of UML(TM) 2.0 Style for an Amazon.co.uk gift card of up to £1.35, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Frequently Bought Together
Product details
|
More About the Author
Product Description
Review
From reviews of The Elements of UML Style by Scott Ambler: '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
Product Description
For all developers who create models using the Unified Modeling Language (UML) 2.x The Elements of UML™ 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™ 2.0 Style sets the rules for style that will improve your productivity.
Inside This Book
(Learn More)
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Explore More
Concordance
Browse Sample PagesConcordance
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Suggested Tags from Similar Products(What's this?)Be the first one to add a relevant tag (keyword that's strongly related to this product)
|
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
Most Helpful Customer Reviews
2 of 2 people found the following review helpful
Format:Paperback|Amazon Verified Purchase
This book won't teach you UML but it will help you gte the best from it. As with most tools UML can be used well or badly. If you are a new or infrequent user then this will help you set out your UML in a clear consisten and undertsndable way.
3 of 4 people found the following review helpful
Format:Paperback
This pocket-guide is an excellent quick help if you made some UML 2.x diagrams and you want a second opinion. Scott really has a lot of experience in how diagrams have to be structured, and which elements have to be used to make the 'one figure instead of 1000 words' promise reality.
I always give this small book to my junior colleagues when they made some new designs, and make them learn from it. Excellent book.
Disclaimer: you will not learn how to use UML with the book, it's a hint-book with best practices.
I always give this small book to my junior colleagues when they made some new designs, and make them learn from it. Excellent book.
Disclaimer: you will not learn how to use UML with the book, it's a hint-book with best practices.
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com:
13 reviews
26 of 26 people found the following review helpful
UML Style Redux
11 Feb 2006
Format:Paperback
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.
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.
10 of 12 people found the following review helpful
Certainly worth the price!
29 Jan 2006
Format:Paperback|Amazon Verified Purchase
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.
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.
4 of 4 people found the following review helpful
Good Foundational Advice
21 Sep 2007
Format:Paperback|Amazon Verified Purchase
Like the book "The Elements of Style" that I was given to use in High School to improve my writing, this book seeks to do the same for your UML diagrams. The author states that the purpose of this book is to "describe a collection of standards, conventions, and guidelines for creating effective UML diagrams". This book succeeds in its goal. I really like the fact that at the beginning of each chapter, each chapter covers one diagram type, a short description of what the diagram is used for is presented. As a designer, I see these rules not being followed or ignored much of the time. Rule 15 (Prefer Well-Known Notation over Esoteric Notation) is what I see as one of the most violated rules. Most people seem to diagram what they think is appropriate and ignore the UML rules. Hmmm, sounds like most people that write as well.
Were these reviews helpful?
Let us know
Listmania!
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
|
