- File Size: 7071 KB
- Print Length: 191 pages
- Page Numbers Source ISBN: 0321193687
- Simultaneous Device Usage: Up to 5 simultaneous devices, per publisher limits
- Publisher: Addison-Wesley Professional; 3 edition (August 30, 2018)
- Publication Date: August 30, 2018
- Sold by: Amazon.com Services LLC
- Language: English
- ASIN: B07H4WN84Z
- Text-to-Speech: Enabled
- Word Wise: Not Enabled
- Lending: Not Enabled
- Amazon Best Sellers Rank: #397,253 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
UML Distilled: A Brief Guide to the Standard Object Modeling Language (Addison-Wesley Object Technology Series) 3rd Edition, Kindle Edition
Use the Amazon App to scan ISBNs and compare prices.
The Amazon Book Review
Book recommendations, author interviews, editors' picks, and more. Read it now
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Customers who bought this item also bought
From the Back Cover
- Would you like to understand the most important elements of Class diagrams? (See page 35.)
- Do you want to see the new UML 2.0 interaction frame notation for adding control flow to sequence diagrams (see page 58) and the unofficial notation that many prefer? (See page 60.)
- Do you want to know what changes have been made to all versions of the UML? (See page 151.)
- Do you want a quick reference to the most useful parts of the UML notation? (See the inside covers.)
- Do you want to find out what diagram types were added to the UML 2.0 without wading through the spec? (See page 11.)
More than 300,000 developers have benefited from past editions of UML Distilled . This third edition is the best resource for quick, no-nonsense insights into understanding and using UML 2.0 and prior versions of the UML.
Some readers will want to quickly get up to speed with the UML 2.0 and learn the essentials of the UML. Others will use this book as a handy, quick reference to the most common parts of the UML. The author delivers on both of these promises in a short, concise, and focused presentation.
This book describes all the major UML diagram types, what they're used for, and the basic notation involved in creating and deciphering them. These diagrams include class, sequence, object, package, deployment, use case, state machine, activity, communication, composite structure, component, interaction overview, and timing diagrams. The examples are clear and the explanations cut to the fundamental design logic.
If you are like most developers, you don't have time to keep up with all the new innovations in software engineering. This new edition of Fowler's classic work gets you acquainted with some of the best thinking about efficient object-oriented software design using the UML--in a convenient format that will be essential to anyone who designs software professionally.
--This text refers to the paperback edition.
About the Author
Martin Fowler is an independent consultant who has applied objects to pressing business problems for more than a decade. He has consulted on systems in fields such as health care, financial trading, and corporate finance. His clients include Chrysler, Citibank, UK National Health Service, Andersen Consulting, and Netscape Communications. In addition, Fowler is a regular speaker on objects, the Unified Modeling Language, and patterns.
--This text refers to the paperback edition.
Would you like to tell us about a lower price?
There was a problem filtering reviews right now. Please try again later.
The bibliography is really great though and the book really does serve well as a reference book for later on.
The first chapter is an introduction to UML, including some short history on the language. The second chapter covers the Development Process with a quick overview of a couple of them - i.e. Agile, RUP, ...- followed by some guidance on choosing the right one.
The following chapters cover the main UML diagrams, respectively, the Class, Sequence, Object, Package, Deployment, Use Case, State Machine, Activity, Communication, Composite Structure, Component, Collaboration, Interaction Overview and Timing Diagrams. At the end, there is an appendix that summarizes the changes between UML versions.
Not all of the diagrams get in-depth coverage. Whereas Class Diagrams get the most attention of the author with two chapters specifically dedicated to them, Object, Deployment, Communication, Composite Structures, Component, Collaboration, Interaction Overview and Timing Diagrams get only a few pages, between two and four. Some of them are just limited to the sample diagrams that illustrate the chapter, with no or little text to support them. Rather than a shortcoming, this seems to be ensuing from the author's willingness to have the book limited to a few pages - 150 exactly, without the appendix -, covering what he considers to be essential.
As such, this book is no replacement for the three classic UML books, i.e. the User's Guide, the Reference Manual and the Unified Process of the Booch/Jacobson/Rumbaugh Object Technology Series that the reader, in my opinion, will anyway have to go through until he/she gains sufficient working proficiency with the language. If the reader's intention is so, he/she'll be better inspired reading "UML Distilled" after, or better, in parallel with the User's Guide, diagram after diagram and have a look at the Reference Manual on selected dictionary terms, as necessary. The Unified Process book can be read independently.
This is not a book an OOA/OOD. As prerequisite, the reader is expected to be comfortable enough with OO concepts such as Class, Object, Relationship, Aggregation, Composition, Inheritance, etc. Although not required, working proficiency with a former OO modeling method - e.g. Fusion, in my case - will help.
UML Distilled is the OO design analog of K&R C. I tore through this book in about a week. It's actually a fun read which is an extreme rarity for anything computer science related. The author did a good job of cutting the fat off a very fat-rich specification. And I think the author quickly turns design via UML into a collaborative effort and not an automata (MDA? Really?).
Reviews of reviewers:
"Didn't follow the spec" Fowler dedicated the first chapter explaining his views on UML's role in the design process. It's bleedingly obvious that he sees UML as a "sketching" tool. If you want an MDA book, go buy one, and good luck.
"Condescending attitude" I didn't get that. I saw a neutral tone throughout. A 10-year fad in IT books is to get cutesy with the material (see the Dummies series). This spills out even to the more serious topics and publishers. There is no cutesy in this book, just fast paced information. Maybe that's mistaken for condescending.
"Couldn't keep up" First, Fowler seems to break his examples up between Java and C#. And his programming examples hold some finer nuances of each. Second, I think OOP and OOD jargon is rich and diverse. Students will get overwhelmed quickly. So I don't think this is the right book to learn OOP. But on the other hand, if you still can't approach this book after a year or two of real world OO programming, something is wrong.
Top international reviews
In fact the book is so useful, people are forever borrowing it form my desk. I bought this third edition to replace my second edition copy, which seems to have been permanently borrowed by someone!
My only reason for not awarding five stars is the price. It seems a bit expensive for such a slim paperback.
There's enough detail in this book to satisfy most students, developers and test engineers and a lot of stuff you'll never see outside of it's covers.
System Architects (those who are UML believers), may require more detail.
On the other hand, in a diagram more detail, means less useful.