UML Distilled Third Edition A Brief Guide to the Standard Object Modeling Language Martin Fowler ¥ Addison-Wesley ‘ork © Toronto * } Madrid + Tokyo * Singapore * Mexico Citya.k.a. Scenario Diagram Use Case Diagram p90 oa |S System KR [oe ame « includes »» « triggers » Sequence Diagram p23 Toop ara tings) 2s co Teanaiony (a (endiond other condtiony ~~ oo aaj eee) [mt rane of neracton ire synetenoue p.61 Instance Specification 2 67 ‘synetronous [UML >= 14) a ration mes5806 0 ny 1 p 55 seynotronous (UML | ee <7 UML 2} Constraint Keyword (named clon) p a9 Koyword p65 Navigabitty p42 Dependency 47 cont == o[ Supoter | Qualified Associstion p74 cess | quater ia clase a7Package Name Package Diagram p29 Composite Structure | p 195 + Public ~ Private # Protected ~ Package part: Ciase Class lass name |p. 3s lass Name aribteypel0..1) = avatue operaontarg fet etn ype | averactOperatn Deployment Diagram 97 ie tea BD —_,—_ ‘artes. atiag + p38 g) ‘component template clase P27 ound element Setarase Li}srt Actnay tort \ [eonationy /\,_ Ieee} ranch co) Atwy ‘atvty Th Activity Diagram. p.117 ty {iass:method) ‘ibdiagam enc urlacton ‘afaction | eivacton || evenvaction argues) torent pier x = pit ‘ne gna! Expansion Region p 127 Dispatcher (Arrocare fesourees ==) rn >( isctss, ) (snc fen Fiesofficer Figure2-44 An example of svinlanes na UML activity diagram, ( Bruegge & DuToit ) State Diagram p. 107 | everitargumensiconton/ction State NameContents List of Figures o...cceseeeeeeereees mersnentneonepectrmn ts Foreword to the Third Edition. eax Foreword to the First Edition... 60+ eae! eet Preface .. She eepeocods xxv ‘Why Bother with the UML? xvi Seructure of the Book . . aowii Changes for the Third Edition «0.2... 2 VEE ‘Acknowledgments wei Chapter 1: Introduction .. 1 ‘What Is the UML? 1 ‘Ways of Using the UML 2 How We Got to the UML 7 Notations and Meta-Models 9 UML Diagrams .. 10 What Is Legal UML? 13 ‘The Meaning of UML 44 UML is Not Enough...» 14 Where co Start with the UML 16 ‘Where to Find Out More - 16 Chapter 2: Development Process «++ ++ 19 Iterative and Waterfall Processes 19 Predictive and Adaptive Planning 23 Agile Processes 24 Rational Unified Process 25 Fitting ¢ Process to a Project ....+.0. ++ oe. 26 Fitting the UML into @ Process . Sere ee 29 Requirements Analysis... 0.00000 00000 sete DD Design . 30 Documentation ........6.065 31 Understanding Legacy Code... .. 32 Choosing a Development Process . 33 ‘Where to Find Out More .....Chapter 3: Class Diagrams: The Essentials 6.0. 0.00 .csccceeeseeeees BS Properties .. - 2 35 Attributes .. 36 Associations . . Se gua 37. Multiplicity .. . 38 Programming Interpretation of Properties... -.+. +s. +. 39 Bidirectional Associations 4.0... Nea eal Operations . 5h : . we AB Generalization re 45 Notes and Comments ee BABES 46 Dependency! iss 5ssscccs: oPPRTERY. PONS OPE OL ORE 47 Constraint Rules... ve AB ‘When to Use Class Diagrams ........ 0. 51 ‘Where to Find Out More . soneic etre PARONOUE 52 Chapter 4: Sequence Diagrams ........ Creating and Deleting Participants Loops, Conditionals, and the Like veces . Synchronous and Asynchronous Calls... ....006 sess 6 ‘When to Use Sequence Diagrams ..... + : 61 Chapter 5: Class Diagrams: Advanced Concepts Keywords Responsibilities . Static Operations and Attributes Aggregation and Composition Derived Properties Interfaces and Abstract Classes ‘Read-Only and Frozen . Reference Objects and Value Objects Qualified Associations Classification and Generalization ofa oe Multiple and Dynamic Classification abies +76 Association Class ee . 78 Template (Parameterized) Class oe BL Enumerations its 82 Active Class . , Wr 83 Visibility ee vee BB Messages ...eccceeeeees ; ; 84 Chapter 6: Object Diagrams ......66eee eee pura CLs “When to Use Object Diagrams 87 Chapter 7: Package Diagrams... ..+eeeeeeeere+ : we 89 Packages and Dependencies ........000000 a Package Aspects 3 ri er] Implementing Packages . a 94 ‘When to Use Package Diagrams .....++0s0eeeeree 95 Where to Find Out More 95Chapter 8: Deployment Diagrams ...... oben Paaenn A ‘When to Use Deployment Diagrams Chapter 9: Use Cases boc : . 199 Content of a Use Case... 100 Use Case Diagrams... ...-..... sevens 02 Levels of Use Cases _ veveeee es OB Use Cases and Features (or Stories} ve d04 When to Use Use Cases Pei ene 104 Where to Find Out More ire: -105 Chapter 10: State Machine Diagrams... baer f.-. 107 Internal Activities veces ee 08 Activity States... e109 Superstates .... 210 Concurrent States m1 Implementing State Diagrams 5 ai ‘When to Use State Diagrams 14 Where to Find Our More 115 Chapter 11: Activity Diagrams api 17 Decomposing an Action pease ag Partitions +120 Signals ae ee ees Tokens - ce EAs <4 Flows and Edges 24 Pins and Transformations e Back 212s Expansion Regions . a 26 Flow Final ede viteeeee DDT Join Specifications 5 : 2128 ‘And There's More an 129 ‘When to Use Activity Diagrams ...... 29 Where to Find Out More ss esssse+5 Pe 130 Chapter 12: Communication Diagrams .. i ‘When to Use Communication Diagrams... ese eceeee BB Chapter 13: Composite Structures . 135 ‘When to Use Composite Structures 137 Chapter 14: Component Diagrams ee ‘When to Use Component Diagrams... 14 Chapter 15: Collaborations .........-++ ceteeteseeeees 143 * When to Use Collaborations oe 146 ‘Chapter 16: Interaction Overview Diagrams ...-.6..csccseesecreeee 147 When ro Use Interaction Overview Diagrams . 447 (Chapter 17: Timing Diagrams 149 ‘When to Use Timing Diagrams... 150Appendix: Changes between UML Versions 181 Revisions to the UML... . . 151 Changes in UML Distilled 7 : +152 Changes from UML 1.00 1.1.2... 153 ‘Type and Implementation Class .......- y 153 Complete and Incomplete Discriminator Constraints 154 Composition holt mts. a9a oF LSA Immutability and Frozen 3 5 154 Returns on Sequence Diagrams ...... ‘ s4 Use of the Term “Role” hs 155 Changes from UML 1.2 (and 1.1) 0 1.3 (and 1.5)... =. 155 Use Cases... eT es 8 FASS Activity Diagrams . : 156 ‘Changes from UML 1.3 to 1.4. RACIST Changes from UML 14. to 1.5 i opie From UML 1.x to UML 2.0 - ey Class Diagrams: The Essentials (Chapter 3) wee SB Sequence Diagrams (Chapter 4) .......60.064 ned 88 Class Diagrams: Concepts (Chapter 5) eee State Machine Diagrams (Chapter 10) 159 Activity Diagrams (Chapter 11) Ye. a5) Bibliography 161 Andesite setenv ty 167Object Technology/UML «Would you lke to understand the most important elements of Class diagrams? (Gee 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? (Gee page 151.) +* Do you want a quick reference to the most useful parts of the UML notation? (Gee the inside covers.) + Do you went 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 beth of these promises in a short, concise, and focused presentation. “This book desoribes all the major UML diagram types, what they’te used for, and the basic rotation Involved in ereating and deciphering them. These diagrams include class, sequence, Sbject, package, deployment, use case, stata machine, activity, communication, composite structure, component, interaction overview, and timing diagrams. The examples are clear and the explanations cut to the fundamental design logic. it you are lke most developers, you don't have ime to Keep up with al the new innovations ihsoftware engineering, This new edition of Fowler's classic work gets you acquainted with somo of the best thinking about efficient object-oriented software design using the UML-— fra convenient format that will be essential to anyone who designs software professionally. Martin Fowler is the Chief Scientist of ThoughtWorks, an enterprise-application development and delivery company. He's been applying object-oriented techniques to enterprise software development for over a decade. He Is notorious for his work on patterns, the UME, refactoring, fand aglle methods. Martin lives in Melrose, Massachusetts, wit his wife, Cindy, and a very Oat Mm www.awprofessional.comlotseries 9 "7803: vesley $34.99 US rAddison- : Pearson Education $5299 CANADA