22.2. Node

22.2. Node
Prev	Chapter 22. Deployment Diagram Artifact Reference	Next

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.

22.2.1. Node Details Tabs

The details tabs that are active for nodes are as follows.

ToDoItem

Standard tab.

Properties

See Section 22.2.2, “Node Property Toolbar” and Section 22.2.3, “Property Fields For Node” below.

Documentation

Standard tab.

Style

Standard tab. The Bounds: field defines the bounding box for the node on the diagram.

Warning

	Warning
Beware that in the 0.14 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. Altering the `Shadow` entry has no effect.

Beware that in the 0.14 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.

Altering the Shadow entry has no effect.

Source

Standard tab, but with no contents.

	Caution
	A node should not generate any code, so having this tab active is probably a mistake.

Constraints

Standard tab. ArgoUML only supports constraints on Classes and Features (Attributes, Operations, Receptions, and Methods), so this tab is grayed out.

Tagged Values

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
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

22.2.2. Node Property Toolbar

Go up

Navigate up through the package structure.

Delete

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).

22.2.3. Property Fields For Node

Name

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.

Generalizations

Text area. Lists any node that generalizes this node.

Button 1 double click navigates to the generalization and opens its property tab.

Stereotype

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.

Navigate Stereotype

icon. If a stereotype has been selected, this will navigate to the stereotype property panel (see Section 15.4, “Stereotype”).

Modifiers

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.

Namespace

Drop down selector. Allows altering the namespace for the node. This is the package hierarchy.

Specializations

Text box. Lists any specialized node (i.e. for which this node is a generalization.

Components

Text box. Lists any components (see Section 22.4, “Component”) designed to be deployed on this type of node.

Button 1 click navigates to the selected entry, button 2 gives a pop up menu with three entries.

Open. Navigate to the selected component.
Move Up. Only available where there are two or more components, and the component selected is not at the top. It is moved up one.
Move Down. Only available where there are two or more components listed, and the component selected is not at the bottom. It is moved down one.