Class diagram. This diagram
captures the static structure of the system being designed,
showing the classes, interfaces and datatypes and how they
are related. Variants of this diagram are used to show
package structures within a system (the package
diagram) and the relationships between
particular instances (the object
diagram).

The ArgoUML class diagram provides support for class
and package diagrams. See Chapter 18, Class Diagram Artifact Reference
for details of the artifacts it supports. The object
diagram is suported on the Deployment diagram.

Behavior diagrams. There are
four such diagrams (or strictly speaking, five, since the
use case diagram is a type of behavior diagram), which show
the dynamic behavior of the system at all levels.

Statechart diagram. Used to
show the dynamic behavior of a single object (class
instance). This diagram is of particular use in systems
using complex communication protocols, such as in
telecommunications. See
Chapter 20, Statechart Diagram Artifact Reference for details of the
ArgoUML statechart diagram and the artifacts it
supports.

Activity diagram. Used to
show the dynamic behavior of groups of objects (class
instance). This diagram is an alternative to the
statechart diagram, and is better suited to systems
with a great deal of user interaction. See
Chapter 22, Activity Diagram Artifact Reference for details of the
ArgoUML activity diagram and the artifacts it
supports.

Interaction diagrams. There
are two diagrams in this category, used to show the
dynamic interaction between objects (class instances)
in the system.

Sequence diagram. Shows
the interactions (typically messages or procedure
calls) between instances of classes (objects) and
actors against a timeline. Particularly useful
where the timing relationships between interactions
are important. See Chapter 19, Sequence Diagram Artifact Reference
for details of the ArgoUML sequence diagram and the
artifacts it supports.

Collaboration diagram.
Shows the interactions (typically messages or
procedure calls) between instances of classes
(objects) and actors against the structural
relationships between those instances. Particularly
suitable where it is useful to relate interactions
to the static structure of the system. See
Chapter 21, Collaboration Diagram Artifact Reference for details of
the ArgoUML collaboration diagram and the artifacts
it supports.

Implementation diagrams. UML
defines two implementation diagrams to show the
relationship between the software components that make up a
system (the component diagram) and the
relationship between the software and the hardware on which
it is deployed at run-time (the deployment
diagram.

Statechart and activity diagrams are associated with a
particular class or operation (or the latter also with a
package), and can only be created when this modelelement has
been selected.

Warning

In ArgoUML version 0.20, the UML 1.4 object diagram as
a variant of the class diagram is not directly supported.
However, it is possible to create simple object diagrams
within the ArgoUML deployment diagram.