UML Bible

Features

• Cover Type: Paperback with 984 pages
• Published by: Wiley
• Edition: 1st Edition June 2, 2003
• Written in: English
• ISBN 10 Number: 0764526049
• ISBN 13 Number: 978-0764526046
• Book Dimensions: 9.2 x 7.4 x 2.1 inches
• Weighs: 3.3 pounds

Reader Reviews
If you are at all involved with the use of UML in your programming or analysis activities, you'll most likely be interested in seeing the UML Bible by Tom Pender (Wiley). Like all 'Bible' titles from Wiley, this book covers a wide range of topics that should give you most any answer you need to find. The chapter breakout is in seven parts: Part 1 - An Introduction to UML - What Is UML?; UML Architecture; UML Diagrams and Extension Mechanisms; Object-Oriented Concepts Part 2 - Modeling Object Structure - Capturing Rules about Objects in a Class Diagram; How to Capture Rules about Object Relationships; Testing With Objects Part 3 - Modeling Object Interactions - Modeling Interactions in UML 1.4; Modeling Interactions in UML 2.0; Modeling an Object's Lifecycle in UML 1.4; Modeling an Object's Lifecycle in UML 2.0 Part 4 - Modeling Object Behavior - Modeling the Use of a System with the Use Case Diagram; Modeling Behavior Using an Activity Diagram Part 5 - Modeling the Application Architecture - Using Packages; Modeling Software Using the Component Diagram; Using Deployment Diagrams in UML 1.4; Using Deployment Diagrams in UML 2.0 Part 6 - Bringing Rigor to the Model - Applying Constraints to the UML Diagrams; Action Semantics Part 7 - Automating the UML Modeling Process - Using a Modeling Tool; Customizing UML Using Profiles; XML Metadata Interchange Appendices - UML 1.4 Notation Guide; UML 2.0 Notation Guide; Standard Elements; Glossary; Index Now, I'm not a UML expert by any stretch of the imagination. But based on what I have read and studied to date, this book covers everything. Taking the Use Case chapter as an example, I can see that there is an abundance of technical detail and diagramming to explain the topic completely. Couple this chapter with the notation guide in the back, and you have a reference guide that is hard to beat. At the time this book was written, UML 2.0 wasn't yet released. But the author takes the specs that should be part of the final release and explains how those features are different than UML 1.4. As a result, you shouldn't outgrow this book anytime soon. The only quibble I have with the book is the audience that the author says he is targeting. Readers new to object-oriented analysis are expected to be able to get an in-depth understanding of UML and be able to become a productive member of a team by reading this book. In my opinion, that may be a bit of a reach. If I had no UML experience, I'd find this book very daunting in both the size and complexity of the material. My recommendation would be to find an entry level UML book, and work through it before tackling this book. With the UML fundamentals fresh in your mind, you'll be able to come at this book from a much better position and benefit much more quickly. Overall, a good book to have around... Comment | | (Report this)