Shulou(Shulou.com)06/01 Report--

This article introduces the relevant knowledge of "what are the UML diagrams?". In the operation of actual cases, many people will encounter such a dilemma. Then let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

1) use case diagram

It is the simplest and most complex graph in UML. It is simple because it adopts the object-oriented idea and is based on the user's perspective, so it is very easy to draw and the simple graphical representation is easy for people to understand. It is complex because use case diagrams are often not easy to control, either too complex or too simple.

Use case diagrams represent roles and use cases and the relationship between them.

2) Class diagram

Class diagram is the most commonly used one in UML diagram, which can help us to understand the architecture of a system more intuitively. Through the class diagram represented by relationships and classes, the design part of a system can be described graphically.

3) object graph

An object diagram is an instance of a class diagram, using almost the same identity as the class diagram. The difference between them is that the object graph shows multiple object instances of the class, not the instance class. An object diagram is an instance of a class diagram. Because the object has a life cycle, the object graph can only exist for a certain period of time in the system.

4) State diagram

Describes the dynamic behavior of an entity based on event response, showing how the entity reacts to different times according to its current state. A UML state diagram is usually created for the following research purposes: to study the complex behavior of classes, roles, subsystems, or components.

5) timing diagram

The sequence diagram in the UML diagram, also known as the sequence diagram, describes the dynamic interaction between objects, focusing on the time sequence of message transmission between objects.

The sequence diagram consists of a group of objects, each with a vertical line, called the lifeline of the object, which represents the timeline, and time extends downward along the vertical line. The sequence diagram describes how these objects exchange messages with each other over time. Messages are represented by horizontal arrows that point from the vertical lifeline of one object to the lifeline of another object. You can also add a description of the time and other notes as needed.

6) collaboration diagram

Collaboration diagrams are used to show the spatial organization of components and their interactions, and it does not focus on the order of interactions. The collaboration diagram shows the organizational interactions between the objects in the interaction and the links between the objects. Unlike sequence diagrams, collaboration diagrams show the relationships between objects. On the other hand, the collaboration diagram does not treat time as a separate dimension, so the sequence number determines the order of messages and concurrent threads. A collaboration diagram is a cross product between a symbol diagram and a sequence diagram, which uses numbered arrows to describe a specific scheme to show the movement of messages throughout the scheme.

The purpose of the collaboration diagram in the UML diagram:

The specific scheme is reflected by depicting the movement of messages between objects.

Displays the spatial organization of objects and their interactions, rather than the order of interactions.

7) activity diagram

UML activity diagrams record the logic of a single action or method, a single user case, or the logic of a single business process. Describes the execution order of various activities in the system, usually used to describe the execution flow of the activities to be carried out in an operation. At the same time, it is often used to describe the processing flow of a use case, or some kind of interaction flow.

The activity diagram consists of a number of activities, and a description of these activities is included in the diagram. When an activity is completed, the control moves to the next activity along the control transfer arrow. The conditions of control transfer and the requirements of parallel execution can also be easily described in the activity diagram.

8) component diagram

The component diagram in the UML diagram is used to reflect the physical structure of the code. From the component diagram, you can understand the compiler and runtime dependencies between software components, such as source code files or dynamic link libraries. Using component diagrams, you can divide the system into cohesive components and show the structure of the code itself.

The main purpose of component diagram is to show the structural relationship between system components.

9) configuration diagram

The configuration diagram describes the physical configuration and system architecture of the hardware and software in the system.

In the configuration diagram, the actual physical devices, such as computers and various external devices, are represented by nodes, and the corresponding nodes are connected according to the connection relationship between them, and the connection mode is explained. In the node, describe the executable components or objects assigned to run on the node, thus indicating which software units are assigned to run on which nodes

This is the end of the content of "what are the UML diagrams"? thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.