UML Five class diagram __uml graph classification

UML defines the following 5 categories, 10 model diagrams.

The first class is the use case diagram, the use case diagram describes the function of the system from the user's point of view, and points out the operator of each function.

The second category is static diagrams, including class diagrams, Object diagrams, and package diagrams. The class diagram is used to define the classes in the system, including describing the relationships between the classes (such as associations, dependencies, aggregations, and so on) and the internal structure of the class, that is, the properties and operations of the class. So the class diagram describes the static structure of the class in the system, which describes a static relationship that is valid throughout the life cycle of the system. The object graph uses a representation symbol that is almost identical to a class diagram, where the object graph shows only the object instances of the class, not the actual class. An object graph is an instance of a class diagram. Because the object has a lifecycle, the object graph is valid only for a certain period of time in the system. A package diagram consists of a package or class that represents the relationship between a package and a package or a package and a class, which is used to describe the hierarchical structure of a system.

The third category is behavioral graph, which describes the dynamic model of the system and the interaction between objects. One is the state diagram, which describes the possible state of a class of objects and the conditions for State migration when an event occurs. Usually a statechart diagram is a supplement to a class diagram, and we do not need to draw a statechart diagram for all classes, but to paint a state diagram for classes that have multiple states and whose behavior is affected by the outside world. Another is called an activity diagram, which describes the constraints on the activities and activities that are required to satisfy the use-case requirements, and the activity diagram makes it easy to express and perform activities.

The fourth class is the interaction diagram, which describes the interaction between objects. A sequential graph, which describes the dynamic partnership between objects, emphasizes the order in which messages are sent between objects, and also shows the interaction between objects. The other is a collaboration diagram, which focuses on the collaboration between objects. collaboration diagrams and sequence diagrams are similar, showing the dynamic partnership between objects. In addition to displaying information exchange, the collaboration diagram shows the relationships between objects and objects. If you emphasize time and order, you should use sequence diagrams, and if you emphasize communication relationships, you can select a collaboration diagram, which is called an interaction diagram.

The fifth class is the implementation diagram, including the component diagram and the configuration diagram. The component diagram describes the physical structure of the code part and the dependencies between the parts. A part can be a resource code part, a binary part, or an executable part that contains information about the logical class and the implementation class. Component diagrams help to analyze and understand the degree of interaction between components. A configuration diagram defines the physical architecture of hardware and software in a system that displays the actual computers and devices (represented by nodes) and the connection between them, as well as the type of connection and dependencies between parts or parts. Within the node, place the executable parts and objects to show the correspondence between the node and the executable unit.