A sample deployment diagram
A deployment diagram in the Unified Modeling Language models the physical deployment of artifacts on nodes.[1] To describe a web site, for example, a deployment diagram would show what hardware components ("nodes") exist (e.g., a web server, an application server, and a database server), what software components ("artifacts") run on each node (e.g., web application, database), and how the different pieces are connected (e.g. JDBC, REST, RMI).
The nodes appear as boxes, and the artifacts allocated to each node appear as rectangles within the boxes. Nodes may have subnodes, which appear as nested boxes. A single node in a deployment diagram may conceptually represent multiple physical nodes, such as a cluster of database servers.
There are two types of Nodes .
- Device Node
- Execution Environment Node
Device nodes are physically computing resources with processing memory and services to execute software,such as typical computer or mobile phones. EEN node is software computing resource that runs within an outer node and which itself provides a service to host and execute other executable software elements.
[edit] References
[edit] External links
|
|
|
| Actors |
|
|
|
| Concepts |
| Object oriented |
|
|
| Structure |
|
|
| Behavior |
|
|
| Relationships |
|
|
| Extensibility |
|
|
| Other |
|
|
|
| Diagrams |
| Structure |
|
|
| Behaviour |
|
|
| Interaction |
|
|
|
| Derived languages |
|
|
| Other topics |
|
|
