Series: A Pragmatic Introduction to UML
Paperback: 290 pages
Publisher: O'Reilly Media; 1 edition (May 5, 2006)
Product Dimensions: 7 x 0.6 x 9.2 inches
Shipping Weight: 1.1 pounds (View shipping rates and policies)
Average Customer Review: 4.2 out of 5 stars See all reviews (30 customer reviews)
Best Sellers Rank: #457,508 in Books (See Top 100 in Books) #28 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > UML #37 in Books > Computers & Technology > Programming > Languages & Tools > Assembly Language Programming #225 in Books > Computers & Technology > Computer Science > Systems Analysis & Design
Based on a recent project at work, I realized I needed a better understanding of UML. To that end, I decided to review the book Learning UML 2.0 by Russ Miles and Kim Hamilton. While there's still a lot to learn there, I think I have a much better grasp on what's going on...Contents: Introduction; Modeling Requirements - Use Cases; Modeling System Workflows - Activity Diagrams; Modeling a System's Logical Structure - Introducing Classes and Class Diagrams; Modeling a System's Logical Structure - Advanced Class Diagrams; Bringing Your Classes to Life - Object Diagrams; Modeling Ordered Interactions - Sequence Diagrams; Focusing on Interaction Links - Communication Diagrams; Focusing on Interaction Timing - Timing Diagrams; Completing the Interaction Picture - Interaction Overview Diagrams; Modeling a Class's Internal Structure - Composite Structures; Managing and Reusing Your System's Parts - Component Diagrams; Organizing Your Model - Packages; Modeling an Object's State - State Machine Diagrams; Modeling Your Deployed System - Deployment Diagrams; Object Constraint Language; Adapting UML - Profiles; A History of UML; IndexMiles and Hamilton use a conversational approach to introduce the reader to UML 2.0, and they build on a model that makes sense. The Use Case view drives nearly everything, as that's the "what" of what the system is supposed to be able to do. Then they cover the logical, process, physical, and development views that support the system and show different perspectives of what the system will look like depending on which angle you view it from. All too often, it seems like UML diagrams are just thrown at the reader one after another, and there's no real explanation as to how it all fits together.