- Project tools
-
-
- Using ArgoUML
-
- The ArgoUML Project
-
- Nightly builds of docs
-
- The Stats Project
-
- How do I...
-
| Category |
Featured projects |
| scm |
Subversion,
Subclipse,
TortoiseSVN,
RapidSVN
|
| issuetrack |
Scarab |
| requirements |
xmlbasedsrs |
| design |
ArgoUML |
| techcomm |
SubEtha,
eyebrowse,
midgard,
cowiki |
| construction |
antelope,
scons,
frameworx,
build-interceptor,
propel,
phing
|
| testing |
maxq,
aut
|
| deployment |
current |
| process |
ReadySET |
| libraries |
GEF,
Axion,
Style,
SSTree
|
| Over 500 more tools... |
|
The UML standard specifies eight principal diagrams, all
of which are supported by ArgoUML. Use case diagram. Used to
capture and analyse the requirements for any OOA&D
project. See Chapter 17, Use Case Diagram Model Element Reference for
details of the ArgoUML use case diagram and the model elements
it supports. 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 Model Element Reference
for details of the model elements 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 Model Element Reference for details of the
ArgoUML statechart diagram and the model elements 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 Model Element Reference for details of the
ArgoUML activity diagram and the model elements 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 Model Element Reference
for details of the ArgoUML sequence diagram and the
model elements 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 Model Element Reference for details of
the ArgoUML collaboration diagram and the model elements
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. The ArgoUML deployment diagram provides support for
both component and deployment diagrams, and additionally
for object diagrams. See Chapter 23, Deployment Diagram Model Element Reference
for details of the diagram and the model elements it
supports.
Diagrams are created using the Create
drop down menu (see Section 10.6, “The Create Menu”
), or with the tools on the toolbar (see
Section 9.4, “Create operations”),
or with the pop-up menus in the explorer. ![[Note]](images/note.png) | Note |
|---|
ArgoUML uses its deployment diagram to create the UML
1.4 component, deployment and object diagrams. |
![[Caution]](images/caution.png) | Caution |
|---|
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]](images/warning.png) | Warning |
|---|
In ArgoUML version 0.24, 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. |
16.8.1. Diagram Details TabsThe details tabs that are active for diagrams are as
follows. 16.8.2. Diagram Property Toolbar
Go upNavigate up through the package structure of the
model. 
DeleteThis deletes the diagram from the model. As a
consequence, in case of a statechart diagram or an
activity diagram, all contained elements are deleted,
too.
16.8.3. Property Fields For DiagramNameThe name of the diagram. There are no conventions
for naming diagrams. By default, ArgoUML uses the
(space separated) diagram name and a sequence number,
thus Use Case Diagram 1. ![[Tip]](images/tip.png) | Tip |
|---|
This name is used to generate a filename when
activating the “Save Graphics...”
menu-item. |
Home ModelThe Home Model of the diagram
is not something defined in the UML specification.
The Home Model is the modelelement represented by the diagram.
Hence its type depends on the type of diagram: e.g.
it is the namespace represented by a class diagram,
or the statemachine in case of a Statechart diagram.
|
