Implementation diagram (component diagram and deployment diagram)

Realization diagram: describe the realization information (hardware composition and layout, software system division and function realization)

1. Component drawing

There are four types of relationships between interfaces and relationships from the perspective of software architecture

Component: Comply with the same set of interfaces and provide physical, replaceable parts of the implementation. Provide interfaces for other components to facilitate software reuse.

Well-defined interface implementation unit.

Type of component: source code component, binary component, executable component, data file or document

Features of components: ①Physical ②Replaceable ③Part of the system ④Comply with a set of interfaces and provide the realization of a set of interfaces

The composition of component diagrams: components, interfaces, relationships

The difference between components and classes:

①Class represents logical abstraction, and component represents physical abstraction

② Component is the physical realization of other elements

③Classes can directly have attributes and operations. In general, components only have operations that are intelligently accessed through its interfaces.

2. Deployment diagram

Also called implementation diagram: nodes and relationships / only dependencies, association relationships

The system is composed of nodes, and each node is represented by a cube. The line between the nodes represents the link between the two cubes.

Node: A physical element that exists at runtime, represents a computable resource, occupies memory and has processing capabilities.

The implementation diagram can contain components, but the components must be on nodes.

Three scenarios for using deployment diagrams:

① Embedded system modeling (the only device node, relationship, and device deployment)

②Client server CS modeling (decision problem, how to communicate, deal with failure noise problem)

③Distributed system modeling

UML diagram classification:

Static structure: class diagram, object diagram, component diagram, deployment diagram

Dynamic structure: use case diagram, state diagram, sequence diagram, collaboration diagram, activity diagram

Guess you like

Origin blog.csdn.net/weixin_44690047/article/details/108511006