In order to describe the information of system implementation and make the system reusable and operable, the component diagram and deployment diagram are used to represent the implementation unit.
1. Components
The reusable modules in the system are encapsulated into substitutable physical units called components.
Features of the component:
1. Code features: Contains and encapsulates classes that implement system functions, implementation codes of other elements, and some instance objects that constitute system state
2. Identity features: Component has identity and state, used to locate physical objects on it
2. Component diagram
Component diagram is used to represent the relationship between components and components, classes or interfaces and components in the system
2.1 Dependencies between components
The same as the dependencies between classes in the class diagram, they are represented by dashed arrows
2.2 Dependencies between components and interfaces
A component uses the interface of other elements, dependencies can be represented by dashed arrows pointing to interface symbols
3. Deployment diagram
A deployment diagram depicts a static view of the hardware nodes at which a system is running, where the software components running on those nodes will physically run, and how they will communicate with each other
The composition of the deployment diagram:
The role of the deployment diagram:
1. Describe the main deployment structure of a specific application
2. Balance the distribution of computing resources when the system is running
Deployment diagram of supermarket information management system: