UML Guide v2.1
Author: Rajinder Yadav
Date: Oct 9, 2007
UML Deployment Diagram
A deployment diagram is used to show physical layout of hardware and the software that is found on that hardware. A UML node is used to denote the hardware and the software that is mapped onto a node. The UML Node element looks like a cube, and represent a processing units that typically has memory. UML components and class elements can be contained inside a node.
Diagram 1 - Deployment Node
A node can have one or more instances, each instance will have a unique name that proceeds the name of the node that is separated by a ":" colon sign. For a node instance, the names will be underline. A unnamed node instance will not have a name before the colon. A Node can have a stereotypes to further classify it.
Node Artifact
An artifact is drawn as a box with the stereotype "artifact". It is used to convey something belonging to or produced by another UML element such as a node, component or another artiface. An example of an artifact would be a logfile that belongs(resides) on a storage device.
Diagram 2 - UML Artifact
The diagram above shows an error-events artifact which could reside in a system's memory(node) producing a logfile that might get deployed to a file system(node).
Node Diagrams
Nodes can have various associations with other nodes, components or node artifacts. An artifact can be deployed or manifested by a node, component or another artifact. In the diagram that follows, the Drive node stores and deploys the database file, but it is the database file that is used to produce the result-set of a "SQL SELECT" command (search operation).
Diagram 3 - Deployment Diagram
The Server node is where the Socket component is found, and it is with this TCP/IP Socket that the software running on the Server node is able to communicate with the Route node to send and receive UDP packet. The "UDP" stereotype between the Router Node and the Server Node described the type of protocol used in the association, and not actual data which could be shown using an artifact. In this case, the data packet artifact is understood and does not need to be included in the diagram.
Copyright © 2007 Rajinder Yadav, All rights reserved
UML logo are trademarks or registered trademarks of the Object Management Group, Inc. in the United States and other countries
|
