Shulou(Shulou.com)06/02 Report--

This article is about the elements and drawing methods of UML deployment diagrams. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

UML deployment diagram elements

Main elements of the UML deployment diagram

Node: it represents a runtime computing resource (a physical device), such as a computer, a workstation, and other devices

The concept of node and component have a lot in common, for example, both have multiple names, both can participate in dependency, generalization and association, both can be nested, both can have instances, and both can participate in interaction.

However, there are obvious differences between them: components are things that participate in the execution of the system, while nodes are things that execute components; components represent the physical packaging of logical elements, while nodes represent the physical deployment of components.

In this figure, four nodes are modeled: the Bhand S client, the Cbig S client, the IIS server, and the database server.

Connection: the most common relationship between nodes is the association relationship (represented by a solid line). In order to better represent the relationship between two nodes, we can describe the connection through "constraints".

Supplementary elements of UML deployment diagrams

Processor ("process"): a node with processing power, that is, a component that can execute

Device ("device"): a node that has no processing power, or at least a node that does not care about its processing power. For example, printers and IC card readers can be modeled as devices if our system does not consider their internal chips.

Node attributes and operations: you can provide a node with attributes such as processor speed, memory capacity, number of network cards, startup, shutdown, etc.

Custom stereotype icon

How to draw UML deployment Diagram

Determine the desired node and the connection between nodes

IC card reader: provided for employees to swipe the card, it will collect the time information of swiping the card, transmit it to the application system, and store it in the database

Application server: responsible for collecting information from IC card reader, and providing managers with functions such as employee settings, attendance inquiries, etc.

Database server: used to store attendance data, because the system is relatively small, so it can be physically merged with the application server

Client software: provide for managers to use, connect to the application server, complete the corresponding operation

Describe the node according to the implementation

Client: need to use Windows operating system, install client software (assumed as KaoQing.exe)

Server: contains a server-side software developed in Delphi (set to KqServer.exe) that needs to interact with the Access database (set to KaoQing.mdb) and communicates with the IC card reader through the driver of the IC card reader (assumed to be called cardReader.dll)

IC card reader: for this system, it is a device that does not execute components, but three have been installed for the convenience of employees.

Application description of UML deployment diagram

The deployment diagram is evolved in two phases. The initial deployment diagram is created at design time as part of the process of determining the final hardware architecture, and then refined step by step to obtain a deployment diagram in the form of one or more instances

Design phase: focus on nodes or node instances and the connections between them

Implementation phase: focus on assigning physical components to nodes

Embedded system modeling

Identify devices and nodes for your system; focus on modeling the relationship between processors and devices; consider using more intuitive icons for servers and devices

Client / server and distributed system modeling

When the software you develop is to run on multiple computers, you must decide how to deploy the software components on each node in a reasonable manner. Among them, the client / server architecture is a typical distributed system model, which includes three-tier Bax S structure and two-tier Cmax S structure.

In addition to the client / server model, large distributed systems may also include deployment structures such as load balancing and clusters, which can be well described by the introduction of UML deployment diagrams.

Thank you for reading! This is the end of this article on "what are the constituent elements and drawing methods of the UML deployment diagram?". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.