Chapter 21. ArgoUML Deployment Diagram Artifact Reference

Table of Contents

21.1. Introduction
21.1.1. Limitations Concerning Deployment Diagrams in ArgoUML
21.2. Node
21.2.1. Node Details Tabs
21.2.2. Node Property Toolbar
21.2.3. Property Fields For Node
21.3. Node Instance
21.3.1. Node Instance Details Tabs
21.3.2. Node Instance Property Toolbar
21.3.3. Property Fields For Node Instance
21.4. Component
21.4.1. Component Details Tabs
21.4.2. Component Property Toolbar
21.4.3. Property Fields For Component
21.5. Component Instance
21.5.1. Component Instance Details Tabs
21.5.2. Component Instance Property Toolbar
21.5.3. Property Fields For Component Instance
21.6. Dependency
21.7. Class
21.8. Interface
21.9. Association
21.10. Object
21.11. Link

21.1. Introduction

This chapter describes each artifact that can be created within a Deployment Diagram. Note that some sub-artifacts of artifacts on the diagram may not actually themselves appear on the diagram.

There is a close relationship between this material and the Properties Tab of the Details Pane (see Section 10.4). That section covers Properties in general, in this chapter they are linked to specific artifacts.

Within ArgoUML, the deployment diagram is also used for both component diagrams (i.e. without instances, showing static dependencies of components) and deployment diagrams (showing how instances of components are handled by instances of nodes at run-time).

Caution

Deployment diagrams are not fully developed yet in ArgoUML. Some aspects are not fully implemented or may not behave as expected. Notable omissions are a correct representation for interfaces and proper stereotyping of the various dependency relationships.

Figure 21.1 shows a component diagram with all possible artifacts displayed.

Figure 21.1. Possible artifacts on a component diagram.

Figure 21.2 shows a deployment diagram with all possible artifacts displayed.

Figure 21.2. Possible artifacts on a deployment diagram.

21.1.1. Limitations Concerning Deployment Diagrams in ArgoUML

The deployment diagram is generally well drawn, but there are only a subset of the relationships that should be shown available, which restricts the ability to show dynamic behavior of deployed code.

It is an inconvenience that the alternative representation of an interface (as a small circle) is not supported.