A node is a run-time physical object on which components may be deployed. In the UML metamodel it is a sub-class of Classifier.
A node is represented on a class diagram as a three dimensional box, labeled with its name.
The details tabs that are active for nodes are as follows.
Standard tab.
See Section 22.2.2, “Node Property Toolbar” and Section 22.2.3, “Property Fields For Node” below.
Standard tab.
Standard tab. The Bounds: field defines the bounding box for the node on the diagram.
Warning | |
---|---|
Beware that in the 0.18 release of ArgoUML, the bounding box just refers to the front face of the cube. This means that the three dimensional top and side may be ignored, for example when determining the limits of a diagram for saving graphics. |
Standard tab, but with no contents.
Caution | |
---|---|
A node should not generate any code, so having this tab active is probably a mistake. |
Standard tab. In the UML metamodel, Node has the following standard tagged values defined.
persistence (from the superclass, Classifier). Values transitory, indicating state is destroyed when an instance is destroyed or persistent, marking state is preserved when an instance is destroyed.
semantics (from the superclass, Classifier). The value is a specification of the semantics of the node.
derived (from the superclass, ModelElement). Values true, meaning the node is redundant—it can be formally derived from other elements, or false meaning it cannot.
Note | |
---|---|
Derived nodes still have their value in analysis to introduce useful names or concepts, and in design to avoid re-computation. |
Note | |
---|---|
The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML |
Navigate up through the package structure.
This creates a new reception, navigating immediately to the properties tab for that reception.
This creates a new Stereotype (see Section 15.5, “Stereotype”) for the selected node, navigating immediately to the properties tab for that stereotype.
This deletes the node from the model
Warning | |
---|---|
This is a deletion from the model not just the diagram. To delete a node from the diagram, but keep it within the model, use the main menu Remove From Diagram (or press the Delete key). |
Text box. The name of the node. The name of a node has a leading capital letter, with words separated by “bumpy caps”.
Note | |
---|---|
ArgoUML does not enforce this naming convention. |
Drop down selector. Node is a type of classifier, and so it has the default stereotypes of a classifier as defined in the UML standard. ArgoUML provides the standard stereotypes for a classifier: metaclass, powertype, process, thread and utility.
icon. If a stereotype has been selected, this will navigate to the stereotype property panel (see Section 15.5, “Stereotype”).
Drop down selector. Allows altering the namespace for the node. This is the package hierarchy.
Check box, with entries abstract, leaf and root.
abstract is used to declare that this node cannot be instantiated, but must always be specialized. The name of an abstract node is displayed in italics on the diagram.
leaf indicates that this node cannot be further specialized.
root indicates the node can have no generalization.
Text area. Lists any node that generalizes this node.
Button 1 double click navigates to the generalization and opens its property tab.
Text box. Lists any specialized node (i.e. for which this node is a generalization.
Button 1 double click navigates to the specialization and opens its property tab.
Text box. Lists any residents (see Section 22.4, “Component”) designed to be deployed on this type of node.
Button 1 double click navigates to the selected entry.