Understanding of nine kinds of graphs in UML

1, use case diagram.

Use case diagrams are used to describe the user's needs , describe the functions of the system from the user's perspective, and point out the individual performers. emphasize who is in use and who is the executor of the system .

2, Class diagram.

Used to define classes in a system, including describing the structure of a class and the relationships between classes. The main function of the class diagram is to describe the static structure of the system.

3, Object graph.

An object graph is an instance of a class diagram that describes the objects that the system contains at a specific point in time and the relationships between the objects.

4, the state diagram.

A state diagram illustrates the sequence of states that an object undergoes in response to events during its life cycle, and how they respond to those events.

5, Component diagram.

Component diagrams are used to describe the physical structure of code components and the dependencies between components. A component can be a resource file, a binary file, or an executable file.

6, Implementation diagram (deployment diagram).

Used to define the physical architecture of the hardware in the system to describe the actual physical device and the connection between them.

7, Sequence diagram (sequence diagram).

Describes the order of interactions between objects, focusing on the chronological order of message delivery between objects, emphasizing the order in which messages are sent between objects, and also showing the interaction between objects.

8, collaboration diagram.

A collaboration diagram is an interaction diagram that emphasizes the organizational structure between the objects that send and receive messages.

Collaboration diagrams primarily describe the interactions and links of collaboration objects.

Displays connections between objects and how messages are sent between objects.

A collaboration diagram can represent an implementation of a class operation.

9, activity diagram.

Summarizes the dynamic behavior of the system, including the active state, which refers to an execution step or an action of the business use case , not the state of the normal object. The activity diagram is suitable for describing the logic execution process inside the system without external event triggering , otherwise it is easier to describe the flowchart in a similar and traditional sense . Business modeling is used to describe the process of operations when detailing business use cases and describing the execution process design of a business.

The following figure feels summed up quite well, so it sticks over and facilitates the understanding of UML again.

From for notes (Wiz)

Understanding of nine kinds of graphs in UML