What is the difference between UML deployment diagrams and component diagrams
This article is about the difference between UML deployment diagrams and component diagrams. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.
The deployment diagram (deploymentdiagram, configuration diagram) is used to show the physical architecture of the software and hardware in the system. The UML component diagram provides a physical view of the system, and its purpose is to show the dependencies of the software in the system with other software components (for example, library functions).
UML deployment diagram
The deployment diagram shows how the software system is deployed to the hardware environment. Its purpose is to show where the different components of the system will run physically and how they will communicate with each other. Because the deployment diagram is to model the physical operation, the production personnel of the system can make good use of it.
The symbols in the UML deployment diagram include the symbol elements used in the component diagram, as well as several additional symbols, including the concept of nodes. A node can represent a physical machine or a virtual machine node (for example, a mainframe node). The node is represented by a three-dimensional cube, and the name of the node is at the top of the cube. The naming convention used is the same as in the sequence diagram: [instance name]: [instance type] (for example, "w3.reporting.myco.com:ApplicationServer").
The UML deployment diagram in the following figure shows that the user accesses the ReportingTool using a browser running on the local machine and connects to the ReportingTool component through the HTTP protocol on the corporate intranet. This tool actually runs on a server called w3.reporting.myco.com. ReportingTool is connected to the database through ADO.NET. In addition to communicating with the reporting database, the ReportTool component communicates with BillboardService through SOAP on HTTPS.
UML component diagram
The UML deployment diagram (deploymentdiagram, configuration diagram) is used to show the physical architecture of the software and hardware in the system, while the component diagram provides a physical view of the system, and its purpose is to show the dependencies of the software in the system with other software components (for example, library functions). Component diagrams can be displayed at a very high level so that only coarse-grained components can be displayed, or at the package level.
The component diagram in the following figure shows four components: ReportingTool, BillboardService, ASP.NET, and ADO.NET. The arrowhead segment from the ReportingTool component to the BillboardService, ASP.NETAPI, and ADO.NET components indicates that ReportingTool depends on those three components.
Thank you for reading! This is the end of the article on "what's the difference between UML deployment diagram and component 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!
