Within the editing pane, button 2 click over an artifact will bring up a pop-up menu with a variable number of main entries, many with a sub-menu.
This sub-menu gives list of all the critics that have triggered for this artifact. Selection of a menu entry causes that entry to be highlighted in the to-do pane and its detailed explanation to be placed in the ToDoItem tab of the details pane. A solid colored line indicates the offending element.
This menu controls the ordering of overlapping artifacts on the diagram. It is equivalent to the Reorder sub-menu of the Arrange menu (see Section 9.7.3, “Reorder”). There are four entries.
Forward. The selected artifacts are
moved one step forward in the ordering hierarchy with
respect to other artifacts they overlap.
Backward. The selected artifacts are
moved one step back in the ordering hierarchy with
respect to other artifacts they overlap.
To Front. The selected artifacts are
moved to the front of any other artifacts they
overlap.
To Back. The selected artifacts are
moved to the back of any other artifacts they
overlap.
This sub-menu only appears for artifacts that can have notes attached (class, interface, object, state, pseudostate) or have operations or attributes added (class, interface). There are at most three entries.
New Attribute. Only appears where the
selected artifact is a class. Creates a new attribute on
the artifact
New Operation. Only appears where the
selected artifact is a class or interface. Creates a new
operation on the artifact
New Comment. Attaches a new comment to
the selected artifact.Add All Relations. Only appears where the selected artifact is a class or interface. Makes all relations visible that exist in the model and that are connected to the selected artifact.
Remove all Relations. Only appears where the selected artifact is a class or interface. Removes all connected relations from the diagram (without removing them from the model).
This sub-menu only appears with certain artifacts. It is completely context dependent. There are many possible entries, depending on the selected artifact and its state.
Hide Extension Point Compartment. Only appears when the extension point compartment of a use case is displayed. Hides the compartment.
Show Extension Point Compartment. Only appears when the extension point compartment of a use case is hidden. Displays the compartment.
Hide All Compartments. Only appears when both attribute and operation compartments are displayed on a class or object. Hides both compartments.
Show All Compartments. Only appears when both attribute and operation compartments are hidden on a class or object. Displays both compartments.
Hide Attribute Compartment. Only appears when the attribute compartment of a class or object is displayed. Hides the compartment.
Show Attribute Compartment. Only appears when the attribute compartment of a class or object is hidden. Displays the compartment.
Hide Operation Compartment. Only appears when the operation compartment of a class or object is displayed. Hides the compartment.
Show Operation Compartment. Only appears when the operation compartment of a class or object is hidden. Displays the compartment.
Show All Edges. Only appears on a class. Displays all associations (to shown artifacts) that are not shown yet. This is the same function as the "add to Diagram" on the asociation in the explorer context menu. currently.
Hide All Edges. Only appears on a class. Hides all associations. This is the same function as “Remove from Diagram” on all the associations of this class.
Hide Stereotype. Only appears when the Stereotype of a package is displayed. Hides the stereotype.
Show Stereotype. Only appears when the Stereotype of a package is hidden. Displays the stereotype.
Hide Visibility. Only appears when the visibility of a package is displayed. Hides the visibility.
Show Visibility. Only appears when the visibility of a package is hidden. Displays the visibility.
This sub-menu only appears with class, interface, package and use case artifacts. It is used to set or clear the values of the various modifiers available.
Abstract. Set for an abstract artifact.
Leaf. Set for a final artifact, i.e. one with no subartifacts.
Root. Set for a root artifact, i.e. one with no superartifacts.
Active. Set for a artifact with dynamic behavior.
![[Note]](images/note.png)
Note This really ought to be set automatically for artifacts with state machines or activity diagrams.
This sub-menu only appears with association artifacts, when clicking at one end of the association. It is used to control the multiplicity at the end of the association nearest the mouse click point. There are only four entries, a sub-set of the range of multiplicities that are available through the property sheet of a association end (see Section 16.6, “Association End”).
1
0..1
1..*
0..*
This sub-menu only appears with association artifacts, when clicking at one end of the association. It is used to control the aggregation at the end of the association nearest the mouse click point. There are three entries.
none. Remove any aggregation.
aggregate. Make this end a shared aggregation (loosely known as an “aggregation”).
composite. Make this end a composite aggregation (loosely known as a “composition”).
![[Caution]](images/caution.png) | Caution |
|---|---|
UML requires that an end with a composition relationship must have a multiplicity of 1 (the default). | |
This sub-menu only appears with association artifacts, when clicking at one end of the association. It is used to control the navigability of the association. There are three entries.
bidirectional. Make the association navigable in both directions.
<class1> to <class2>. Make the association navigable only from <class1> to <class2>. In other words <class1> can reference <class2> but not the other way round.
<class2> to <class1>. Make the association navigable only from <class2> to <class1>. In other words <class2> can reference <class1> but not the other way round.
| Note |
|---|---|
UML does permit an association to be non-navigable in both directions. ArgoUML will allow this, but you will have to set each of the association ends navigation property, reached from the property tab of the association - and the diagram does not show any arrows in this case. This is considered bad design practice (it will trigger a critic in ArgoUML), so is only of theoretical interest. | |
| Note |
|---|---|
UML does not permit navigability from an interface to a class. ArgoUML does not prevent this. | |