Download UML 2.0 In A Nutshell

UML 2.0 in a Nutshell
ByDan Pilone,Neil Pitman
...............................................
Publisher:O'Reilly
Pub Date: June 2005
ISBN:0-596-00795-7
Pages:234
Table of Contents | Index
When
reading
the diagram
left to
right, you
can usefor
thedecades
length of
timeline
to indicate how
System
developers
have used
modeling
languages
tothe
specify,
visualize,
long
the
object
remains
in
a
particular
state.
To
associate
time
measurements,
show tick
construct, and document systems. The Unified Modeling Language (UML) is oneyou
of those
marks
alongUML
the bottom
part
of thefor
frame,
shown intoFigure
10-41.by providing a common
languages.
makes it
possible
teamas
members
collaborate
language that applies to a multitude of different systems. Essentially, it enables you to
communicate solutions in a consistent, tool-supported language.
Timing
diagram
with
tick systems,
marks which means
Today, UML hasFigure
become 10-41.
the standard
method
for modeling
software
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
FigureClass
10-41and
shows
thatUse
the Case,
Login Sequence,
event is received
three time
units after
the start
of the
Object,
Collaboration,
Statechart,
Activity,
Component,
sequence.
To show relative
times, you can mark a specific instance in time using a variable
and Deployment
Diagrams
name.Figure 10-41 marks the time the sendMail event is received as time t. You can use
Extension
Mechanisms
relative
time marks
in constraints to indicate that a message must be received within a
specified amount of time. Figure 10-42 shows the Disconnect message must be received
Object
Constraint
Language
(OCL)
within The
10 time
units
of the sendMail
event.
You can show multiple objects involved in a timing diagram by stacking the lifelines. You show
messages between objects using an arrow from one timeline to another. The start and end of
If you're
to UML,to
a when
tutorial
with
realistic
has even This
beennotation
includedshows
to help
you
the
arrow new
correspond
the
message
is examples
sent and received.
the
quickly
familiarize
yourself
with
the
system.
triggers that cause a transition; however it
Figure 10-42. Timing diagram with time constraints