Understanding the thirteen diagrams
of UML 2.x is an important part of understanding OO
development. Although there is
far more to modeling than just the UML the reality
is the UML defines the standard modeling artifacts when
it comes to object technology.
There are three classifications of UML diagrams:
Behavior diagrams. A type of diagram that
depicts behavioral features of a system or business
process. This includes activity, state machine, and
use case diagrams as well as the four interaction
Interaction diagrams. A subset of behavior
diagrams which emphasize object interactions. This
includes communication, interaction overview,
sequence, and timing diagrams.
Structure diagrams. A type of diagram that
depicts the elements of a specification that are
irrespective of time. This includes class, composite
structure, component, deployment, object, and package
summarizes the thirteen, up from nine in UML 1.x,
diagram types of UML 2.x. In the diagram column
the links will take you to description pages for the
artifact. The learning priority column indicates
how important it is for a business application developer
to learn the artifact (IMHO).
Shows instances of classes,
their interrelationships, and the message flow
between them. Communication diagrams typically focus
on the structural organization of objects that send
and receive messages. Formerly called a
Collaboration Diagram. See
UML Collaboration diagram guidelines.
Depicts the components that
compose an application, system, or enterprise. The
components, their interrelationships, interactions,
and their public interfaces are depicted. See
UML Component diagram guidelines.
Describes the states an object
or interaction may be in, as well as the transitions
between states. Formerly referred to as a state
diagram, state chart diagram, or a state-transition
UML State chart diagram guidelines.