A\u00a0deployment diagram<\/b>\u00a0in the\u00a0Unified Modeling Language<\/a>\u00a0models the\u00a0physical<\/i>\u00a0deployment of\u00a0artifacts<\/a>\u00a0on\u00a0nodes<\/a>. To describe a\u00a0web site<\/a>, for example, a deployment diagram would show what hardware components (“nodes”) exist (e.g., a\u00a0web server<\/a>, an\u00a0application server<\/a>, and a\u00a0database server<\/a>), what software components (“artifacts”) run on each node (e.g.,\u00a0web application<\/a>,\u00a0database<\/a>), and how the different pieces are connected (e.g.\u00a0JDBC<\/a>,\u00a0REST<\/a>,\u00a0RMI<\/a>).<\/p>\n 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.<\/p>\n There are two types of Nodes:<\/p>\n Device nodes are physical computing resources with processing memory and services to execute software, such as typical computers or mobile phones. An execution environment node (EEN) is a software computing resource that runs within an outer node and which itself provides a service to host and execute other executable software elements.<\/p>\n A\u00a0package diagram<\/b>\u00a0in the\u00a0Unified Modeling Language<\/a>\u00a0depicts the\u00a0dependencies<\/a>\u00a0between the\u00a0packages<\/a>\u00a0that make up a model.<\/p>\n\n
Package diagram<\/h3>\n