Most of the models in UML describe the logic and design information:
Use Case chart to understand expectations
Class diagrams can understand the Vocabulary (class and object) of the problem domain)
The status chart, InterAction diagram, and activity diagram can be used to understand how the words in the class diagram are written (logical structure)
An Implementation diagram is used to describe implementation information.
It describes the composition and layout of hardware at the system level, software system division, and function implementation. These two aspects are implemented through the deployment diagram and component diagram respectively:
Component diagram: displays the organization and dependency between a group of components. It describes the main functions of a system from the perspective of software architecture, such as subsystems, classes, packages, and components. The most important thing to use components is reuse.
Deployment diagram: Describes the physical topology of the system hardware and the software running on this structure.
We can compare the class to understand the component:
Class |
Component |
Logical Abstraction |
Physical Abstraction |
You can directly own properties and operations |
Generally, you only have operations that can be queried through the interface. |
To sum up, components have the following features:
The component is physical.
Component is replaceable
Components are part of the system
The component follows a group of interfaces and provides implementation for a group of interfaces.
Compared with the component diagram, it is easier to understand the deployment diagram. In short, it is a system software architecture and a system hardware architecture. For details, refer:
Component diagram: There are four relationships between components and components that describe the relationship between source code and runnable programs and the relationship between components and interfaces, but there is no relationship between the description and hardware.
Deployment diagram: Only dependency and association are involved in the composition. Describes the relationship and Topology between the ing with hardware.
Despite a lot of comparisons, I do not have a good grasp of the implementation map because I am better than the Sichuan cuisine. Below are two interactive diagrams drawn for the data center charging system, there must be some very bad information. Please criticize and point out the following:
For the final improvement, please refer to the highlights of UML diagram acceptance questions.
UML sequence implementation Diagram