Would you like to understand the most important elements of Class diagrams? Do you want to know what changes have been made to all versions of the UML? 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. More than , developers have benefited from past editions of UML Distilled. My proudest thing about this book is that it's under half an inch thick - which was very unusual for OO modeling books at that time. I was also pleased when it won a productivity award from Software Development magazine.
The book has chapters for all the major diagram types in the UML, together with an intro and some general guidance on software process and how it fits in with the UML. I also put in a lot of tips on how to use the UML well and introduce a number of principles and techniques for good OO development.
UML Distilled: A Brief Guide to the Standard Object Modeling Language (3rd Edition) | BibSonomy
In September , the 3rd edition of this book came out. Now I needed a quick refresher course. For this [Fowler] is great. He throws in some things in to think about. A little book doesn't mean it is easier. Aug 24, Nikolas Mavrogeneiadis rated it it was amazing. Martin Fowler knows the subject very well and describe it clearly. It can be used as a reference book cause it contains a lot of diagrams about UML. Also the small size makes the book more attractive cause it has only the necessary things.
Get A Copy
May 08, Ralph rated it liked it. Nice quick overview on UML to gain more insight into modeling the software development process. May 19, Kevin Schultz rated it liked it Shelves: It's something to skim for 10 minutes and then keep on your desk for the next time you need to sketch out a diagram. Feb 17, Steve Whiting rated it liked it. This is a fairly short page gallop through UML2.
- If You're a Student.
- Parrys Valuation and Investment Tables?
- UML Distilled: A Brief Guide to the Standard Object Modeling Language by Martin Fowler.
- Hamiltonian Field Theory in the Radiating Regime (Lecture Notes in Physics Monographs).
It's short and to the point, and mostly this gets across the gist of what you need to know. There are times where it strays a bit too far into terseness, and some of the text really needs to be broken up with specific examples closer to the descriptions. Particularly, the text sometimes ploughs on with some quite dense descriptions and no visual example, or has a reference to a diagram several pages away, neither of which make for easy readi This is a fairly short page gallop through UML2.
Particularly, the text sometimes ploughs on with some quite dense descriptions and no visual example, or has a reference to a diagram several pages away, neither of which make for easy reading. Conversely, Fowler is refreshingly pragmatic, and there's a great quote in chapter 2 that sums up the pragmatic approach: The biggest risk with using the UML in analysis is that you draw diagrams that the domain experts don't fully understand.
A diagram that isn't understood by the people who know the domain is worse than useless; all it does is breed a false sense of confidence for the development team". Contrast this with 'Domain-Driven Design: Tackling Complexity in the Heart of Software', where UML class diagrams are promoted as a communication medium with non-technical customers, mainly to ease the path towards maintenance of a single model, an approach I'm still pretty sceptical about.
Still, can't blame the book for that! All in all, a good book if you're looking to expand your familiarity with UML, but I'm not sure that I would want to learn from it as a first book. Practical Object-Oriented Analysis and Design 2nd Edition edges it, though that does have the advantage of 3x the page-count to get the information across. Mar 27, Scott Fabel rated it it was ok.
As a Business Analyst, and as a Professor of Business Analysis, I am frequently reading books about business analysis tools and techniques. I am very interested in using more UML in my work, so I thought that this would be a good book for me to read.
Unfortunately, I didn't think that this book was all that great--at least not for a business analyst. This book is probably far more useful to a systems designer or developer because most of the diagrams are described in terms of how they could be u As a Business Analyst, and as a Professor of Business Analysis, I am frequently reading books about business analysis tools and techniques. This book is probably far more useful to a systems designer or developer because most of the diagrams are described in terms of how they could be used for coding a software solution.
Even though I am more than capable of following the code, I found it to be too much for business analysis. The discussion of the diagrams that are more frequently used for business analysts e. If you're a designer or developer of software solutions, I think that this book could be a good overview for you.
UML Distilled: A Brief Guide to the Standard Object Modeling Language
If, on the other hand, you're a business analyst, this book will not help you all that much. Apr 13, Roshan Titus rated it really liked it. Got a copy of the 3rd edition which focus on UML 2. The book is excellently written, concise in a manner which provides lot of valuable information in short words.
Page discusses 3 ways to realize state diagrams including state pattern. Also author discuss various related Object oriented Got a copy of the 3rd edition which focus on UML 2. Also author discuss various related Object oriented concepts which is always under debate in the OO community and provides his strong opinions.
As author mentions in the beginning, this is an opinionated book, but I found it rather helpful as the book reflects the knowledge and long working experiences from "Martin Fowler" itself! Jan 14, Michael Mcdermott rated it liked it Shelves: A good overview of UML. UML does not seem to be a large benefit to the software development process in itself, but its value stems from the value of modeling ideas on paper before sinking time into coding. Some of the techniques in this book are good to know about to help you think about your software and how your programs interact with other components of your system.
UML formalizes the annotation, which is nice, but I think the thought process that goes into the diagrams more valuable.