UML 2.0 in a Nutshell

321 Pages·2005·15.182 MB·English

by  Dan Pilone, Neil Pitman

www.it-ebooks.info
UML 2.0 in a Nutshell
By Dan Pilone, Neil Pitman
...............................................
Publisher:O 'Reilly
Pub Date: June 2005
ISBN: 0-596-00795-7
Pages: 234

Table of Contents | Index
System developers have used modeling languages for decades to specify, visualize,
construct, and document systems. The Unified Modeling Language (UML) is one of those
languages. UML makes it possible for team members to collaborate by providing a common
language that applies to a multitude of different systems. Essentially, it enables you to
communicate solutions in a consistent, tool-supported language.
Today, UML has become the standard method for modeling software systems, which means
you're probably confronting this rich and expressive language more than ever before. And
even though you may not write UML diagrams yourself, you'll still need to interpret
diagrams written by others.
UML 2.0 in a Nutshell from O'Reilly feels your pain. It's been crafted for professionals like
you who must read, create, and understand system artifacts expressed using UML.
Furthermore, it's been fully revised to cover version 2.0 of the language.
This comprehensive new edition not only provides a quick-reference to all UML 2.0 diagram
types, it also explains key concepts in a way that appeals to readers already familiar with
UML or object-oriented programming concepts.
Topics include:
The role and value of UML in projects
The object-oriented paradigm and its relation to the UML
An integrated approach to UML diagrams
Class and Object, Use Case, Sequence, Collaboration, Statechart, Activity, Component,
and Deployment Diagrams
Extension Mechanisms
The Object Constraint Language (OCL)
If you're new to UML, a tutorial with realistic examples has even been included to help you
quickly familiarize yourself with the system.
www.it-ebooks.info
UUMMLL 22..00 iinn aa NNuuttsshheellll
BByy DDaann PPiilloonnee,, NNeeiill PPiittmmaann
..............................................................................................
PPuubblliisshheerr::OO ''RReeiillllyy
PPuubb DDaattee:: JJuunnee 22000055
IISSBBNN:: 00--559966--0000779955--77
PPaaggeess:: 223344

TTaabbllee ooff CCoonntteennttss || IInnddeexx
SSyysstteemm ddeevveellooppeerrss hhaavvee uusseedd mmooddeelliinngg llaanngguuaaggeess ffoorr ddeeccaaddeess ttoo ssppeecciiffyy,, vviissuuaalliizzee,,
ccoonnssttrruucctt,, aanndd ddooccuummeenntt ssyysstteemmss.. TThhee UUnniiffiieedd MMooddeelliinngg LLaanngguuaaggee ((UUMMLL)) iiss oonnee ooff tthhoossee
llaanngguuaaggeess.. UUMMLL mmaakkeess iitt ppoossssiibbllee ffoorr tteeaamm mmeemmbbeerrss ttoo ccoollllaabboorraattee bbyy pprroovviiddiinngg aa ccoommmmoonn
llaanngguuaaggee tthhaatt aapppplliieess ttoo aa mmuullttiittuuddee ooff ddiiffffeerreenntt ssyysstteemmss.. EEsssseennttiiaallllyy,, iitt eennaabblleess yyoouu ttoo
ccoommmmuunniiccaattee ssoolluuttiioonnss iinn aa ccoonnssiisstteenntt,, ttooooll--ssuuppppoorrtteedd llaanngguuaaggee..
TTooddaayy,, UUMMLL hhaass bbeeccoommee tthhee ssttaannddaarrdd mmeetthhoodd ffoorr mmooddeelliinngg ssooffttwwaarree ssyysstteemmss,, wwhhiicchh mmeeaannss
yyoouu''rree pprroobbaabbllyy ccoonnffrroonnttiinngg tthhiiss rriicchh aanndd eexxpprreessssiivvee llaanngguuaaggee mmoorree tthhaann eevveerr bbeeffoorree.. AAnndd
eevveenn tthhoouugghh yyoouu mmaayy nnoott wwrriittee UUMMLL ddiiaaggrraammss yyoouurrsseellff,, yyoouu''llll ssttiillll nneeeedd ttoo iinntteerrpprreett
ddiiaaggrraammss wwrriitttteenn bbyy ootthheerrss..
UUMMLL 22..00 iinn aa NNuuttsshheellll ffrroomm OO''RReeiillllyy ffeeeellss yyoouurr ppaaiinn.. IItt''ss bbeeeenn ccrraafftteedd ffoorr pprrooffeessssiioonnaallss lliikkee
yyoouu wwhhoo mmuusstt rreeaadd,, ccrreeaattee,, aanndd uunnddeerrssttaanndd ssyysstteemm aarrttiiffaaccttss eexxpprreesssseedd uussiinngg UUMMLL..
FFuurrtthheerrmmoorree,, iitt''ss bbeeeenn ffuullllyy rreevviisseedd ttoo ccoovveerr vveerrssiioonn 22..00 ooff tthhee llaanngguuaaggee..
TThhiiss ccoommpprreehheennssiivvee nneeww eeddiittiioonn nnoott oonnllyy pprroovviiddeess aa qquuiicckk--rreeffeerreennccee ttoo aallll UUMMLL 22..00 ddiiaaggrraamm
ttyyppeess,, iitt aallssoo eexxppllaaiinnss kkeeyy ccoonncceeppttss iinn aa wwaayy tthhaatt aappppeeaallss ttoo rreeaaddeerrss aallrreeaaddyy ffaammiilliiaarr wwiitthh
UUMMLL oorr oobbjjeecctt--oorriieenntteedd pprrooggrraammmmiinngg ccoonncceeppttss..
TTooppiiccss iinncclluuddee::
TThhee rroollee aanndd vvaalluuee ooff UUMMLL iinn pprroojjeeccttss
TThhee oobbjjeecctt--oorriieenntteedd ppaarraaddiiggmm aanndd iittss rreellaattiioonn ttoo tthhee UUMMLL
AAnn iinntteeggrraatteedd aapppprrooaacchh ttoo UUMMLL ddiiaaggrraammss
CCllaassss aanndd OObbjjeecctt,, UUssee CCaassee,, SSeeqquueennccee,, CCoollllaabboorraattiioonn,, SSttaatteecchhaarrtt,, AAccttiivviittyy,, CCoommppoonneenntt,,
aanndd DDeeppllooyymmeenntt DDiiaaggrraammss
EExxtteennssiioonn MMeecchhaanniissmmss
TThhee OObbjjeecctt CCoonnssttrraaiinntt LLaanngguuaaggee ((OOCCLL))
IIff yyoouu''rree nneeww ttoo UUMMLL,, aa ttuuttoorriiaall wwiitthh rreeaalliissttiicc eexxaammpplleess hhaass eevveenn bbeeeenn iinncclluuddeedd ttoo hheellpp yyoouu
qquuiicckkllyy ffaammiilliiaarriizzee yyoouurrsseellff wwiitthh tthhee ssyysstteemm..
www.it-ebooks.info
UML 2.0 in a Nutshell
UML 2.0 in a Nutshell
By Dan Pilone, Neil Pitman
...............................................
by Dan Pilone with Neil Pitman
Publisher:O 'Reilly
Pub Date: June 2005
Copyright © 2005 O'Reilly Media, Inc. All rights reserved.
ISBN: 0-596-00795-7
Pages: 234
Printed in the United States of America.

Published by O'Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472.
Table of Contents | Index
O'Reilly books may be purchased for educational, business, or sales promotional use. Online
editions are also available for most titles (safari.oreilly.com). For more information, contact
oSuyrs ctoermp odreavtee/loinpsetritsu htiaovnea lu ssaelde sm doedpealrintmg elanntg: u(a8g0e0s) f9o9r8 d-e9c9a3d8e so rt oc osrppeocriafyte, @viosureaillilzye.c,om.
construct, and document systems. The Unified Modeling Language (UML) is one of those
languages. UML makes it possible for team members to collaborate by providing a common
lEadnigtuoarg:e that applies to a multitude of difJfoenreantht asny sGteemnnsi.c kEssentially, it enables you to
communicate solutions in a consistent, tool-supported language.
Production Editor: Mary Anne Weeks Mayo
Today, UML has become the standard method for modeling software systems, which means
Cover Designer: Ellie Volckhausen
you're probably confronting this rich and expressive language more than ever before. And
eIvnetne rtihooru Dgeh syiogun emra:y not write UML diagrDaamvsid y Fouutrasetolf, you'll still need to interpret
diagrams written by others.
Printing History:
UML 2.0 in a Nutshell from O'Reilly feels your pain. It's been crafted for professionals like
June 2005: First Edition.
you who must read, create, and understand system artifacts expressed using UML.
Furthermore, it's been fully revised to cover version 2.0 of the language.
NTuhtissh ceollm Hparnedhbeonoskiv,e t hnee wN uetdsihtieolnl Hnaont dobnolyo kp lroogvoid, easn ad qthueic kO-'rReefiellrye nlocgeo t oa rael lr eUgMisLt e2r.e0d diagram
ttryapdeesm, aitr kasls oof eOx'pRleaiilnlys Mkeeyd icao, nIcnecp. tTsh ien Ian wa aNyu tthshaet lla pspeeraielss tdoe sriegandaetrios nasl,r eUaMdLy 2fa.0m iinli aar with
NUuMtsLh eolrl ,o tbhjee citm-oargieen otef da pcrhoimgrpaamnmzeien,g acnodn creeplattse.d trade dress are trademarks of O'Reilly
Media, Inc.
Topics include:
Unified Modeling Language, UML, Model Driven Architecture, MDA, Common Object Request
Broker Architecture, and CORBA are all trademarks of Object Management Group.
The role and value of UML in projects
Many of the designations used by manufacturers and sellers to distinguish their products are
claimeTdh aes o tbrjaedcetm-oarireknst.e Wd hpearrea dthigomse a dneds iitgsn aretiloantiso na ptop etahre inU MthLis book, and O'Reilly Media,
Inc. was aware of a trademark claim, the designations have been printed in caps or initial
caps. An integrated approach to UML diagrams
While Cevlaesrsy apnrde cOaubtjeiocnt, hUasse b Ceaesne t, aSkeeqnu ienn tchee, Cproellpaabroartaiotino no,f Sthtaist ebcohoakr,t ,t hAec tpivuitbyli,s Cheorm apnodnent,
authorasn ads sDuempleo ynmo ernets pDoinagsirbaimlitsy for errors or omissions, or for damages resulting from the
use of the information contained herein.
Extension Mechanisms
ISBN: 0-596-00795-7
The Object Constraint Language (OCL)
[M]
If you're new to UML, a tutorial with realistic examples has even been included to help you
quickly familiarize yourself with the system.
www.it-ebooks.info
UML 2.0 in a Nutshell
DedicaBtyi Daon Pnilone, Neil Pitman
...............................................
Publisher:O 'Reilly
Pub Date: June 2005
For my family: the reason I wrote this book and the reason I was able to .
ISBN: 0-596-00795-7
Pages: 234
Dan Pilone

For Laurie Ann:
Table of Contents | Index
Giorraíonn beirt bóthar/Two people shorten the road .
NSeyils tPeitmm daenvelopers have used modeling languages for decades to specify, visualize,
construct, and document systems. The Unified Modeling Language (UML) is one of those
languages. UML makes it possible for team members to collaborate by providing a common
language that applies to a multitude of different systems. Essentially, it enables you to
communicate solutions in a consistent, tool-supported language.
Today, UML has become the standard method for modeling software systems, which means
you're probably confronting this rich and expressive language more than ever before. And
even though you may not write UML diagrams yourself, you'll still need to interpret
diagrams written by others.
UML 2.0 in a Nutshell from O'Reilly feels your pain. It's been crafted for professionals like
you who must read, create, and understand system artifacts expressed using UML.
Furthermore, it's been fully revised to cover version 2.0 of the language.
This comprehensive new edition not only provides a quick-reference to all UML 2.0 diagram
types, it also explains key concepts in a way that appeals to readers already familiar with
UML or object-oriented programming concepts.
Topics include:
The role and value of UML in projects
The object-oriented paradigm and its relation to the UML
An integrated approach to UML diagrams
Class and Object, Use Case, Sequence, Collaboration, Statechart, Activity, Component,
and Deployment Diagrams
Extension Mechanisms
The Object Constraint Language (OCL)
If you're new to UML, a tutorial with realistic examples has even been included to help you
quickly familiarize yourself with the system.
www.it-ebooks.info
UML 2.0 in a Nutshell
PrefaceBy Dan Pilone, Neil Pitman
...............................................
Publisher:O 'Reilly
Pub Date: June 2005
About This Book
ISBN: 0-596-00795-7
Pages: 234
How to Use This Book

Typographic Conventions
Table of Contents | Index
Safari Enabled
SysteCmom dmeveenltosp earnsd hQauvees utisoends modeling languages for decades to specify, visualize,
construct, and document systems. The Unified Modeling Language (UML) is one of those
languAacgkenso.w UleMdLg mmeanktess it possible for team members to collaborate by providing a common
language that applies to a multitude of different systems. Essentially, it enables you to
communicate solutions in a consistent, tool-supported language.
Today, UML has become the standard method for modeling software systems, which means
you're probably confronting this rich and expressive language more than ever before. And
even though you may not write UML diagrams yourself, you'll still need to interpret
diagrams written by others.
UML 2.0 in a Nutshell from O'Reilly feels your pain. It's been crafted for professionals like
you who must read, create, and understand system artifacts expressed using UML.
Furthermore, it's been fully revised to cover version 2.0 of the language.
This comprehensive new edition not only provides a quick-reference to all UML 2.0 diagram
types, it also explains key concepts in a way that appeals to readers already familiar with
UML or object-oriented programming concepts.
Topics include:
The role and value of UML in projects
The object-oriented paradigm and its relation to the UML
An integrated approach to UML diagrams
Class and Object, Use Case, Sequence, Collaboration, Statechart, Activity, Component,
and Deployment Diagrams
Extension Mechanisms
The Object Constraint Language (OCL)
If you're new to UML, a tutorial with realistic examples has even been included to help you
quickly familiarize yourself with the system.
www.it-ebooks.info
UML 2.0 in a Nutshell
About ThBiys Da nB Pilooneo, Nkeil Pitman
...............................................
Publisher:O 'Reilly
Pub Date: June 2005
Welcome to UMLIS 2B.N0: 0in- 5a9 N6-u0t0sh7e9l5l-.7 The Unified Modeling Language (UML) has expanded quite
a bit since its inPcaegpetsio: 2n3 a4nd can be applied to many different domains, however it still has its
roots in software development. We have trie d to make this book applicable to as broad an
audience as possible, but it's helpful to have at least a cursory knowledge of Object Oriented
PTarboleg orfa Cmonmtenintsg | (InOdOexP) because UML draws much of its terminology from that domain.
Before going any further we'd like to clarify how this book refers to the Unified Modeling
LSaynsgtueamg ed.e Gveralompmerast hicaavlley usspeeda kminogd,e "ltinhge lUaMngLu" aisg ecso rfroerc dt.e Hcaodweesv teor ,s ipt escoifuyn, dvsi swueailrizde., This book
ucsoenss tthruec mt, oarned c doollcouqmuieanl t" UsyMsLt"e.ms. The Unified Modeling Language (UML) is one of those
languages. UML makes it possible for team members to collaborate by providing a common
UML 2.0 in a Nutshell is a detailed reference for the UML 2.0 Superstructure, from a user's
language that applies to a multitude of different systems. Essentially, it enables you to
perspective. Whenever it would be helpful to clarify a UML concept with a concrete example,
communicate solutions in a consistent, tool-supported language.
we will present Java code.
Today, UML has become the standard method for modeling software systems, which means
In general we assume that you are familiar with OOP and the type of constructs that go with
you're probably confronting this rich and expressive language more than ever before. And
it (classes, methods, inheritance, etc.). However, we make no assumptions about what you
even though you may not write UML diagrams yourself, you'll still need to interpret
know about UML. Each chapter starts with a top-to-bottom discussion of the chapter's topic.
diagrams written by others.
This will be fast paced and thorough, meant for those who understand the basics and want to
know the "nitty-gritty" of a piece of UML. Subsequent sections are kinder, gentler discussions
UML 2.0 in a Nutshell from O'Reilly feels your pain. It's been crafted for professionals like
of the topic. This includes examples that show how the topic may be applied to typical
you who must read, create, and understand system artifacts expressed using UML.
problems, help you further refine your models to eliminate ambiguity, capture details that
Furthermore, it's been fully revised to cover version 2.0 of the language.
might otherwise be lost, or add information to your model that aids in tool-based
development.
This comprehensive new edition not only provides a quick-reference to all UML 2.0 diagram
types, it also explains key concepts in a way that appeals to readers already familiar with
A brief word of warning: UML has a strict terminology for just about every aspect of modeling.
UML or object-oriented programming concepts.
This is necessary to reduce ambiguity and confusion as much as possible. However, in
everyday use some terms are used interchangeably with others that have completely different
Topics include:
meanings in UML. A classic example of this is operation and method. These are frequently
treated as being synonymous in a software development environment but have different
meanings when used in the context of UML. We will make a point to use the correct UML term
The role and value of UML in projects
even if it may not be the most colloquial name.
The object-oriented paradigm and its relation to the UML
An integrated approach to UML diagrams
Class and Object, Use Case, Sequence, Collaboration, Statechart, Activity, Component,
and Deployment Diagrams
Extension Mechanisms
The Object Constraint Language (OCL)
If you're new to UML, a tutorial with realistic examples has even been included to help you
quickly familiarize yourself with the system.
www.it-ebooks.info
UML 2.0 in a Nutshell
How to UBsy Dean TPilohnei, Nse il BPitmoanok
...............................................
Publisher:O 'Reilly
Pub Date: June 2005
This book is diviIdSeBdN :b 0a-5s9ed6- o0n07 U9M5-L7 diagram type. Obviously there is some crossover, as some
diagrams build oPnag ceos:n 2c3e4pts from others. Chapter 1, Fundamentals of UML, covers the basics
of UML and presents some background infor mation that will help you understand the context
for the rest of the book. If you are familiar with previous versions of UML, you can probably
sTakbilme o ft Choinst ecnhtsa p| Itnedre.x If you don't have a strong background in UML, you should definitely start
here.
TShyes tneemxt dseevt eolof pcehrasp htearvse c uosveedr wmhoadte ilsin cga llalendg ustaagteics mfoord deelicnagd iens UtoM Lsp. eSctiafyti,c vmisoudaelilzineg, captures
tchoen pshtryuscict,a la nstdr udcotcuurem oefn ta spyisetceem osf. sTohftew Uanreif i(eads Mmoudcehli nags Lsoafntgwuaargee h (aUsM aL ")p ihs yosnicea ol"f stthrousceture).
Floarn geuxaagmepsl.e U: MwLh amt aokpeesr aitt iopnoss saibnlde afottrr itbeuatmes m ae cmlabsesr sc otnot acoinllsa,b worhaatte i nbtye rpfraocveisd ian gc laa scso rmeamlioznes,
olra nwghuaatg pea tchkaatg aeps pcloienst atoin aa lml tuhltisit umdees so.f Tdhifefe sretantti cs ymsotedmelsin. gE scsheanpttiearllsy ,in ict leundaeb:les you to
communicate solutions in a consistent, tool-supported language.
Today, UML has become the standard method for modeling software systems, which means
Chapter 2, Class Diagrams
you're probably confronting this rich and expressive language more than ever before. And
even though you may not write UML diagrams yourself, you'll still need to interpret
This chapter introduces the class diagram. It discusses the various elements that can be
diagrams written by others.
used on a class diagram, what they represent, and how to extend them. Because class
diagrams are often a centerpiece of a UML model, you should know this chapter inside
UML 2.0 in a Nutshell from O'Reilly feels your pain. It's been crafted for professionals like
and out. The last part of the chapter discusses how class diagrams fit into the overall
you who must read, create, and understand system artifacts expressed using UML.
UML model and how the diagrams are typically mapped to code.
Furthermore, it's been fully revised to cover version 2.0 of the language.
This comprehensive new edition not only provides a quick-reference to all UML 2.0 diagram
Chapter 3, Package Diagrams
types, it also explains key concepts in a way that appeals to readers already familiar with
UML oTrh oisb cjehcatp-oterrie inntterdod purcoegsr apmacmkaingge sc oanncde pgtrso.uping within a UML model.
Topics include:
Chapter 4, Composite Structures
TThhies rcohlea patnedr ivnatrluoed uocfe Us MthLe i nn epwro jUeMctLs 2.0 concept of composite structures. Composite
structures are specifically designed to represent patterns and are a major new
The object-oriented paradigm and its relation to the UML
component to the modeling language.
An integrated approach to UML diagrams
Chapter 5, Component Diagrams
Class and Object, Use Case, Sequence, Collaboration, Statechart, Activity, Component,
and Deployment Diagrams
This chapter introduces components and the component diagram. Topics such as the
stereotypes used in component diagrams, relationships between components, and
Extension Mechanisms
component metainformation are discussed. The latter part of this chapter discusses how
components are typically realized in a programming language.
The Object Constraint Language (OCL)
Chapter 6, Deployment Diagrams
If you're new to UML, a tutorial with realistic examples has even been included to help you
This chapter introduces the concept of capturing system deployment using deployment
quickly familiarize yourself with the system.
diagrams. Deployment fundamentals such as nodes, node stereotypes, and
relationships to components are explained. This chapter also includes a discussion on
modeling a distributed system using deployment diagrams.
The next set of chapters cover the second half of UMLbehavioral modeling. Behavioral
modeling captures how the various elements of a system interact during execution. Diagrams
www.it-ebooks.info
such as the use case diagram can capture requirements from an external actor's perspective,
and sequence diagrams can show how objects interact to implement a particular use case.
The behavioral modeling chapters include:
UML 2.0 in a Nutshell
By Dan Pilone, Neil Pitman
...............................................
Chapter 7, Use Case Diagrams
Publisher:O 'Reilly
Pub Date: June 2005
This chapter introduces use cases, actors, and system boundaries. It goes slightly
ISBN: 0-596-00795-7
beyond puPraeg eUs:M 2L3 4in that the chapter touches on common practices regarding use cases,
such as use case scoping, use case do cuments, and use case realizations.
Table of Contents | Index
Chapter 8, Statechart Diagrams
This chapter introduces state machine modeling using states, actions, and transitions.
System developers have used modeling languages for decades to specify, visualize,
Statecharts can be used to model a simple algorithm all the way up to a complex
construct, and document systems. The Unified Modeling Language (UML) is one of those
system.
languages. UML makes it possible for team members to collaborate by providing a common
language that applies to a multitude of different systems. Essentially, it enables you to
communicate solutions in a consistent, tool-supported language.
Chapter 9, Activity Diagrams
TodayT,h UisM cLh ahpatse br eincotrmodeu tchees sat acnlodsaer dr emlaetitvheo dto f otrh em sotdaetelicnhga srot fdtwiaagrrea msy, sttheem asc, twivhitiyc hd imageraanms.
you'reA cptriovbitayb dlyia cgoranmfrosn rteinsgem thbilse roicldh- ascnhdo eoxl pflroewsscihvaer tlsa nagnuda agree m tyopriec athllya nu seevde rt ob emfoordee. l Aannd
even athlgoourgithh myo uor m uasey cnaost ew rreitaeli zUaMtiLo nd.iagrams yourself, you'll still need to interpret
diagrams written by others.
CUhMaLp t2e.r0 1in0 ,a I Nntuetrsahcetlilo nf rDomiag Ora'Rmesilly feels your pain. It's been crafted for professionals like
you who must read, create, and understand system artifacts expressed using UML.
FurtheTrhmiso crhea, pitt'esr b ienetrno dfuulclye sr etvhies eladr tgoe csoevte orf vinertesiroanc t2io.0n odfia tghrea mlasn gsuuapgpeo.rted by UML 2.0. The
two best-known diagrams are sequence and collaboration diagrams. This chapter also
This cdoimscpursesheesn tshivee n neeww t iemdiintigo-nc ennottr iocn ilnyt eprraocvtiidoens daia qguraicmk-.reference to all UML 2.0 diagram
types, it also explains key concepts in a way that appeals to readers already familiar with
TUhMe Lf inoar lo pbajertc to-fo trhieen tbeodo kp rcoogvrearms mexintegn csoionnc eapntds .applications of UML 2.0:
Topics include:
Chapter 11, Tagged Values, Stereotypes, and UML Profiles
The role and value of UML in projects
This chapter discusses how UML 2.0 may be extended and refined.
The object-oriented paradigm and its relation to the UML
ChapteArn 1 i2n,t eEgfrfeactetidv ea pDpiarogarachm mtoi nUgML diagrams
TChlaiss sc haanpdt eOrb djeecpta, rUtss ef rComas eth, eS esqpueecinficcea,t iCoonl lsaibdoer aotfi oUnM, LS 2ta.0te achnadr ot,f fAecrsti vrietayl,- wCoomrldp oandevnicte,
oannd m Doedpelloinygm, ewnht aDt iapgarratsm osf UML 2.0 to use when, and how to effectively convey the
right information.
Extension Mechanisms
AppenTdhixe AO, bMjeDcAt :C Monosdteral-iDntr ivLaenn gAuracgheit e(OctCuLre)
This appendix introduces the Model-Driven Architecture (MDA). While MDA isn't a new
idea, UML 2.0 has MDA in mind in several places, and next-generation tools may be
If youa'rbele n teow m toa kUeM MLD, aA tau troerailaitl yw.ith realistic examples has even been included to help you
quickly familiarize yourself with the system.
Appendix B, The Object Constraint Language
This appendix describes the Object Constraint Language (OCL), a simple language
defined to express constraints on UML diagrams. It can be applied in countless ways
www.it-ebooks.info
and is introduced here in its basic form.
If you're familiar with the fundamental UML concepts, you can read this book's chapters in
nearly any orderU.M HL o2w.0 einv ae rN,u ttshheerlle is always a certain amount of overlap between chapters
because some eBley Dmaen nPtilso ncea, Nne ial Ppitpmeaanr on many diagrams. Instead of repeating the information
in each chapter,. .w...e.. .f.u..l.l.y.. .d..e..f.i.n..e.. .e..l.e..m...e..n..t..s. .(..a..nd their associated stereotypes, attributes, etc.)
the first time thPeuyb laisrhee re:nO c'Roueinlltyered, and in subsequent chapters, we provide detailed cross
references backP tuob tDhaete o: rJiugninea 2l 0d0e5finition, when needed.
ISBN: 0-596-00795-7
Pages: 234

Table of Contents | Index
System developers have used modeling languages for decades to specify, visualize,
construct, and document systems. The Unified Modeling Language (UML) is one of those
languages. UML makes it possible for team members to collaborate by providing a common
language that applies to a multitude of different systems. Essentially, it enables you to
communicate solutions in a consistent, tool-supported language.
Today, UML has become the standard method for modeling software systems, which means
you're probably confronting this rich and expressive language more than ever before. And
even though you may not write UML diagrams yourself, you'll still need to interpret
diagrams written by others.
UML 2.0 in a Nutshell from O'Reilly feels your pain. It's been crafted for professionals like
you who must read, create, and understand system artifacts expressed using UML.
Furthermore, it's been fully revised to cover version 2.0 of the language.
This comprehensive new edition not only provides a quick-reference to all UML 2.0 diagram
types, it also explains key concepts in a way that appeals to readers already familiar with
UML or object-oriented programming concepts.
Topics include:
The role and value of UML in projects
The object-oriented paradigm and its relation to the UML
An integrated approach to UML diagrams
Class and Object, Use Case, Sequence, Collaboration, Statechart, Activity, Component,
and Deployment Diagrams
Extension Mechanisms
The Object Constraint Language (OCL)
If you're new to UML, a tutorial with realistic examples has even been included to help you
quickly familiarize yourself with the system.
www.it-ebooks.info
UML 2.0 in a Nutshell
TypograpBhy Dainc P ilConeo, Nenil Pvitmeanntions
...............................................
Publisher:O 'Reilly
The following tyPpuobg Draapteh:i cJu cnoen 2v0e0n5tions are used in this book:
ISBN: 0-596-00795-7
Pages: 234

Constant width
Table of Contents | Index
Used in the text to refer to class names, stereotypes, and other elements taken from
UML diagrams.
System developers have used modeling languages for decades to specify, visualize,
construct, and document systems. The Unified Modeling Language (UML) is one of those
Constant width italic
languages. UML makes it possible for team members to collaborate by providing a common
language that applies to a multitude of different systems. Essentially, it enables you to
Used in UML diagrams to indicate text that would be replaced by the user.
communicate solutions in a consistent, tool-supported language.
Today, UML has become the standard method for modeling software systems, which means
Italic
you're probably confronting this rich and expressive language more than ever before. And
even Uthsoeudg wh hyeonu nmeway t neromt ws rairtee UinMtrLo dduiacgerda,m asn dy ofourr sUeRlfL, sy oaun'dll fsitleil l rneefeerde ntoc eisn.terpret
diagrams written by others.
..U.ML 2.0 in a Nutshell from O'Reilly feels your pain. It's been crafted for professionals like
you who must read, create, and understand system artifacts expressed using UML.
FurtheErllmiposrees, iintd'si cbaeteen n founlleys sreevnitsiaeld m toa tceorviaelr t vhearts hioans 2b.e0e no fo tmheit tleadn gfuroamge a. diagram for the
sake of readability.
This comprehensive new edition not only provides a quick-reference to all UML 2.0 diagram
types, it also explains key concepts in a way that appeals to readers already familiar with
UML or object-Ionrdieicnatteeds par otigpr,a smumgginegst icoonn,c oerp tgse.neral note.
Topics include:
The role and value of UML in projects
The object-oriented paradigm and its relation to the UML
Indicates an aspect of UML that you must be particularly careful about
An integrautseindg a.pproach to UML diagrams
Class and Object, Use Case, Sequence, Collaboration, Statechart, Activity, Component,
and Deployment Diagrams
Note that UML makes frequent use of curly braces ({}) and guillemots («»). When these are
used inE xat esnysnitoanx Mdeecfihnaitnioisnm, sthey are required by UML.
NearlyT ehvee Orybtjheicntg C inon UsMtrLa innto tLaatniognu aisg eo p(tOioCnLa)l, so there is no specific notation to indicate an
optional field. If a particular piece of syntax is required, it is noted in the text.
If you're new to UML, a tutorial with realistic examples has even been included to help you
quickly familiarize yourself with the system.