This menu provides for creating the various types of UML diagrams supported by ArgoUML.
This menu entry creates a blank class diagram, and selects that diagram in the editing pane. If a package is currently selected, the class diagram will be created within that package, it will be shown within the package on the explorer hierarchy (under Package-centric view) and artifacts created on the diagram will be created within the namespace of the package. This does not only apply to a package, but also to a class, interface, use case, etc.
![]() | Tip |
---|---|
This does not prevent artifacts from other namespaces/packages
appearing on the diagram. They can be added from the explorer
using |
This menu entry creates a blank use case diagram, and selects that diagram in the editing pane. If a package is currently selected, the use case diagram will be created within that package, it will be shown within the package on the explorer hierarchy (under Package-centric view) and artifacts created on the diagram will be created within the namespace of the package. This does not only apply to a package, but also to a class, interface, use case, etc.
![]() | Tip |
---|---|
This does not prevent artifacts from other namespaces/packages
appearing on the diagram. They can be added from the explorer
using |
This menu entry creates a blank statechart diagram associated with the currently selected class, and selects that diagram in the editing pane. Artifacts created on the diagram will be created within the namespace of the owning class.
![]() | Tip |
---|---|
Statechart diagrams must be associated
with a model element capable of dynamic behavior, such as classifier or
a behavioral feature, which provides the context for
the state machine it represents.
Suitable model elements are e.g. a class, an operation, and a use case.
The |
This menu entry creates a blank activity diagram associated with the currently selected class, and selects that diagram in the editing pane. Artifacts created on the diagram will be created within the namespace of the owning class.
![]() | Tip |
---|---|
Activity diagrams must be associated
to packages, classifiers (including use cases) and behavioral features.
Suitable model elements are e.g. a class, a use case, an operation,
and a package.
The |
This menu entry creates a blank collaboration diagram, and selects
that. Within the package hierarchy, collaboration diagrams are always
created within a Collaboration
, within the package
or model, rather than within the package or model directly itself. If a
package is currently selected, the collaboration diagram will be
created within a collaboration within that package, it will be shown
within the collaboration within the package on the explorer
hierarchy (under Package-centric view) and artifacts created on the
diagram will be created within the namespace of the collaboration
within the package.
![]() | Tip |
---|---|
This does not prevent artifacts from other
namespaces/packages appearing on the diagram. They can added from the
explorer using |
This menu entry creates a blank deployment diagram, and selects that diagram in the editing pane. If a package is currently selected, the deployment diagram will be created within that package, it will be shown within the package on the explorer hierarchy (under Package-centric view) and artifacts created on the diagram will be created within the namespace of the package.
![]() | Tip |
---|---|
This does not prevent artifacts from other
namespaces/packages appearing on the diagram. They can added from the
explorer using |