The graphical editor dedicated to the Deployment Diagram has been specified from the UML 2.0 Superstructure Specification document. Feel free to bring your own remarks about the way UML concepts were represented in this diagram : we could discuss about that on the user mailing list .
1. Creation of the diagram
1.1. From the wizard
You can use the creation wizard to create a new deployment diagram. Select the corresponding Template to initialize the model.
The root element of the UML model is a Model and it contains a Package as its children element. The diagram is then linked with the Package.
1.2. From an existing diagram
The deployment diagram is necessarily associated with a Package model object.
Then you can create a new diagram by selecting a Package node in the Outline : "
" and select " ".2. Editing of the Diagram
2.1. Basic editing
2.1.1. Node, Device and ExecutionEnvironment
A Node is computational resource upon which artifacts may be deployed for execution. Nodes can be interconnected through communication paths to define network structures. It is associated with a Deployment of an Artifact. The Node is also depicted into two subclasses :
You can add a Node at the Package level or include a Node into another Node.
2.1.2. Artifact
An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system.
You can create an Artifact at the Package level.
2.1.3. DeploymentSpecification
A DeploymentSpecification specifies a set of properties that determine execution parameters of a component artifact that is deployed on a node.
You can temporary create a DeploymentSpecification at the Package level and then use it to parametrize a Deployment.
2.1.4. Deployment
A component deployment is the deployment of one or more artifacts or artifact instances to a deployment target, optionally parameterized by a deployment specification.
You can use the Deployment to deploy an Artifact onto a Node (see 2.2.1. for details about the creation).
2.1.5. Manifestation
A manifestation is the concrete physical rendering of one or more model elements by an artifact. A Manifestation is owned by an Artifact.
You can create a Manifestation link between an Artifact and a PackageableElement.
2.1.6. CommunicationPath
A communication path is an association between two DeploymentTargets, through which they are able to exchange signals and messages.
You can create a CommunicationPath between two Node elements
2.2. Advanced editing
2.2.1. Deploy an Artifact onto a Node
2.2.2. Parametrize a Deployment with a DeploymentSpecification
3. Diagram Example
_______________________________________
By Jacques LESCOT, Anyware Technologies
August, 31 2006