.1 Overview
Most of the system model reflects information about the logic and design of the system, and is independent of the final implementation unit. However, information on system implementation is also important for the purpose of reusability and operability. UML uses two views to represent implementation units: implementation views and deployment views. Implementing views The reusable blocks in the system have alternative physical units, which are referred to as components. Implement the interface and dependencies between the view components and components to represent the specific implementation of design elements (eg, classes). The component is a reusable component of the system high layer. The deployment view represents the physical arrangement of computing resources (such as computers and connections between them). These run resources are called nodes. At runtime, the node contains components and objects. The allocation of components and objects can be static, and they can also be migrated between nodes. If a component instance containing a dependency is placed on a different node, the deployment view can show the bottleneck during the execution process. 9.2 The component member is a physical implementation unit that defines a good interface, which is an alternative portion in the system. Each component reflects the implementation of specific classes in system design. A well-defined component does not directly depend on other components, depending on the interface supported by the component. In this case, one of the components in the system can be replaced by other components of the correct interface. The component has interfaces supported and the interface that requires from other components. The interface is an operation set supported by software or hardware. By using a named interface, you can avoid direct dependencies between the components in the system, which is conducive to the replacement of new components. The component view shows the inter-component interdependence network structure. The component view can be represented in two forms, one is a collection of available components (component libraries) containing dependencies, which is a physical tissue unit of the construction system. It can also be represented as a configured system that is used to build its components have been selected. In this form, each component is coupled to other components that provide services to it, which must be in line with the interface requirements of the member. The component is used as one of two small rectangles, which can be connected to a circle representing a member interface with a solid line (as shown in Figure 9-1). The component diagram represents the dependencies between members (as shown in Figure 9-2). Each component is implemented (supported) some interfaces and uses other interfaces. If the dependency between the members is related to the interface, the component can be replaced by other components having the same interface. Figure 9-1 Figure 9-2 Membrane Figure 9.3 Node Node is a physical object that represents the runtime of calculating resources, typically has memory and processing capabilities. The node may have a structure of a variety of resources, such as CPUs, devices, and memory, and more. The node can contain objects and components instances. Figure 9-3 Deployment diagram nod represents a cube named node name, can have classification (optional) (as shown in Figure 9-3). The association between the node represents the communication path. Association is used to distinguish between different paths. The node also has an extensive relationship, and the general description of the node is associated with a specific example case. The presence of the object in the node is indicated by the object symbols nested within the node symbol. If this is inconvenient, the object symbol can contain a Location tag that represents the name of its node. The migration of the object or component instance of the node can also be expressed.
