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

This article will explain in detail how to apply the UML deployment map. The editor thinks it is very practical, so I share it with you as a reference. I hope you can get something after reading this article.

UML deployment diagram

The deployment diagram (deploymentdiagram, configuration diagram) is used to show the physical architecture of the software and hardware in the system. From the deployment diagram, you can learn about the physical relationship between software and hardware components and the component distribution of processing nodes. Use deployment diagrams to show the structure of the run-time system, while also communicating how the hardware and software elements that make up the application are configured and deployed.

A UML deployment diagram (object Governance Organization 2001) depicts a runtime hardware node and a static view of the software components running on those nodes. The deployment diagram shows the hardware of the system, the software installed on the hardware, and the middleware used to connect heterogeneous machines. The purpose of creating a deployment model includes ∶

Explore the problems related to the commissioning of the system.

Explore the dependencies between your system and other systems in the production environment that may already exist or will be introduced.

Describe the main deployment structure of a business application.

Design a hardware and software structure of the embedded system.

Describe an organization's hardware / network infrastructure.

Guide General guidelines for ∶

Indicate software components on specific project diagrams; nodes and communication associations focused on enterprise diagrams

Nodes and components: naming nodes in descriptive terms; modeling only important software components; applying consistent layouts to components; applying visual layouts to nodes

Dependency and communication association: use version to indicate communication protocols; only model critical dependencies between components

I. General guidelines

1. Indicate software components on a specific project diagram

Figure 1 is a description of the UML deployment diagram of a university governance system. The diagram describes how the major software components containing a single application are configured into the production environment, which enables the project team to determine their deployment strategy.

Figure 1. A UML deployment diagram for a specific project.

(click to view the original picture)

two。 Nodes and communication associations focused on enterprise-level graphs

The UML deployment diagram is often thought of as a network diagram or technical architecture diagram, and figure 2 is an example of this style, which describes the technical infrastructure of a simple organization. Note that figure 2 is a very simple example. In a diagram like this, many organizations will have dozens or even hundreds of nodes.

Although it is useful to indicate the deployment of components within the limited scope of the diagram, such as figure 1, the diagram quickly becomes clumsy. Figure 2 focuses on the high-level deployments of the enterprise, so the fine details of the software components configured on top of the hardware nodes do not need to be displayed. You can process this information in your CASE tool, but that doesn't mean you need to show them on the diagram.

Figure 2. UML deployment diagram of an organization

(click to view the original picture)

II. Nodes and components

A node, usually described as a three-dimensional box, represents a computing device, usually a single hardware device, such as a computer, network router, host, sensor, or personal digital assistant (PDA). The component, described as a rectangle, with two smaller rectangles protruding from the left side, is the same symbol used on the UML component diagram, which represents an intermediate product of the software, such as a file, framework, or domain component.

1. Naming nodes in descriptive terms

In figure 1, you can see that nodes have names, such as client, ApplicationServer, DatabaseServer, and Mainframe. All of these terms need to be immediately recognized by developers in the organization because these terms are used on a daily basis. Keep it simple.

two。 Model only important software components

Although figure 1 contains software components, it does not describe each software component. For example, there are probably other software components, such as operating systems and applications, installed on the client, but those components are not shown because they are beside the point. The fact is that each node may have dozens or even hundreds of software components configured on it, your goal is not to describe all the software components, but only to describe those components that are critical to the column sections of the system. If you need to explore the relationships between software components, you should create a UML component diagram instead, following the "appropriate Artifact" practice of the application of sensitive AM (Ambler2002).

3. Apply a consistent layout to a component

Apply the same layout to the component on the UML deployment diagram as in the UML component diagram.

4. Apply the visual layout to the node

Figure 2 uses a visual layout to describe the node description node. For example, mobilePC is displayed as a notebook, while databases is represented by a traditional database cylinder symbol. It is impossible to set standards for visual layouts on UML deployment maps, and the general rule of thumb is to use appropriate clip art as you can see.

This is the end of this article on "how to apply UML deployment diagrams". 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, please 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.