Pages: 208 Format: Paperback Amazon Availability: Usually dispatched within 24 hours Customer Rating:
Also Shop International: (Not all items available internationally)
UML Distilled: A Brief Guide to the Standard Object Modeling Language (Addison-Wesley Object Technology Series) Editorial Review: The second edition of Martin Fowler's bestselling UML Distilled provides updates to the Unified Modeling Language (UML) without changing its basic formula for success. It is still arguably the best resource for quick, no- nonsense explanations to using UML.
The major strength of UML Distilled is its short, concise presentation of the essentials of UML and where it fits within today's software development process. The book describes all the major UML diagram types, what they're for and the basic notation involved creating and deciphering them. These diagrams include use cases, class and interaction diagrams, followed by collaborations, state, activity and physical diagrams. The examples are always clear and the explanations cut to the fundamental design logic.
For the second edition, the material has been reworked for use cases and activity diagrams, plus there are numerous small tweaks throughout, including the latest UML v. 1.3 standard. An appendix even traces the evolution of UML versions.
Working developers often don't have time to keep up with new innovations in software engineering. This new edition lets you get acquainted with some of the best thinking about efficient object-oriented software design using UML in a convenient format that will be essential to anyone who designs software professionally. --Richard Dragan, amazon.com
Topics covered: UML basics, analysis and design, outline development (software development process), inception, elaboration, managing risks, construction, transition, use case diagrams, class diagrams, interaction diagrams, collaborations, state diagrams, activity diagrams, physical diagrams, patterns, refactoring basics.
Customer Reviews: Easy to read, follow, and comprehend summary of all the relevant parts of UML The second edition of this book is based on UML 1.4 standard and therefore is quite outdated. Third edition already uses UML 2.0 and is much, MUCH better.
In the newer version the author has re-written majority of the book and re-organised the chapters in a much better fashion. Therefore, the second edition does not deserve full five stars, but still is a great book. I bought it because I could get it cheap and it is still a good reference and a guide to understanding the basic principles of OO analysis and design. However I kind of regret going cheap on the purchase and would suggest you go for the latest version, although it's a little more costly. (I read the 3rd edition cover-to-cover and it is in my opinion the best book on the topic).
The author does a great job concisely summarising in an engaging, easy-to-read-follow-and-comprehend style all the relevant parts of UML.
All you need to know in one book If you are a Business Analyst or Systems Analyst, then all you are likely to need to know is in this book. It is readable, understandable and comprehensive. It's a must for your bookshelf, but don't leave it there - it's practical and usable in the field.
An Excellent Overview This book was exactly what i wanted - a good summary introduction to UML diagrams and a good reference book.
Highly reccomended.
Excellent for starters I am quite new to UML and needed to learn basic ideas of UML for a project. In many places, not only hows but also whys of UML notations are explained, and I believe this makes all the reading more enjoyable. This is not perhaps the correct book for those who are new to object oriented programming. If you know the concepts like abstract classes, polymorphism etc then you should have no problem in following the book.
Good Enough UML is a bit of a bandwagon, however, I found this book useful at university. Sequence diagrams turn up in test-specs and standard docs, so I guess you need an overview of UML.
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.