A component type represents a distributable piece of implementation of a system, including software code (source, binary, or executable) but also including business documents, etc., in a human system. Components may be used to show dependencies, such as compiler and run-time dependencies or information dependencies in a human organization. In the UML metamodel it is a sub-class of Classifier.
A component is represented on a class diagram as a box with two small rectangles protruding from its left side, labeled with its name.
The details tabs that are active for components are as follows.
Standard tab.
See Section 22.4.2, “Component Property Toolbar” and Section 22.4.3, “Property Fields For Component” below.
Standard tab.
Standard tab. The Bounds: field defines the bounding box for the component on the diagram.
Standard tab, but with no contents.
![]() | Caution |
---|---|
A component should not generate any code, so having this tab active is probably a mistake. |
Standard tab.
![]() | 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 component, navigating immediately to the properties tab for that stereotype.
This deletes the component from the model
![]() | Warning |
---|---|
This is a deletion from the model not just the diagram. To delete a component 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 component. The name of a component has a leading capital letter, with words separated by “bumpy caps”.
![]() | Note |
---|---|
ArgoUML does not enforce this naming convention. |
Drop down selector. Component is provided by default with the UML standard stereotypes document, executable, file, library and table. ArgoUML also provides the standard Classifier stereotypes, 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. Records and allows altering the namespace for the component. This is the package hierarchy.
Check box, with entries abstract, leaf and root.
Abstract is used to declare that this component cannot be instantiated, but must always be specialized.
Leaf indicates that this component cannot be further specialized.
Root indicates the node can have no generalization.
Text box. Lists any component that generalizes this component.
Text area. Lists any derived components, i.e those for which this component is a generalization.
Text area. Lists outgoing dependencies. Button 1 double click navigates to the dependency.
Text area. Lists incoming dependencies. Button 1 double click navigates to the dependency.
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.