UML includes nine types of diagrams

From: 51testing software testing Forum

UML includes nine types of diagrams: use case diagram, class diagram, object diagram, state diagram, sequence diagram, collaboration diagram, activity diagram, component diagram, and configuration diagram. 1) use case diagram is the simplest and most complex diagram in UML. Simply put, it is because it adopts the object-oriented idea and is based on the user's perspective. It is very easy to draw. simple graphical representation makes people understand it at a glance. It is complicated because the use case diagram is often not easy to control, either too complicated or too simple. The use case diagram shows the roles and use cases and their relationships. 2) Class digraphs are the most commonly used graphs. Class Diagrams help us better understand the system architecture. Class Diagrams expressed by links and classes can graphically describe the design part of a system. 3) object graph () an object graph is an instance of a class graph and uses almost the same ID as a class graph. They differ in that the object graph shows multiple object instances of the class, rather than the class of the instance. An object graph is an instance of a class graph. Because the object has a lifecycle, the object graph can only exist in a certain period of time in the system. 4) The status chart describes the dynamic behavior of an Object Based on Event Response and shows how the object reacts to different times based on the current state. A uml state chart is usually created to study the complex behavior of classes, roles, subsystems, or components for the following purposes. 5) The sequence diagram, also known as the sequence diagram, describes the dynamic interaction between objects and focuses on the time sequence of message passing between objects. A Sequence Chart consists of a group of objects. Each object has a vertical line, called the lifeline of an object. It represents the timeline and the time is stretched down along the vertical line. The sequence diagram describes the process of exchanging messages between these objects over time. A message is represented by a horizontal arrow that points from a vertical object lifeline to another object lifeline. You can also add time descriptions and other notes as needed. 6) The collaboration diagram is used to display the organizational structure of the space of the component and Its Interaction relationship. It does not focus on the interaction sequence. The collaboration diagram shows the organizational interaction between objects and the links between objects in the interaction. Unlike a sequence diagram, a collaboration diagram shows the relationship between objects. On the other hand, the collaboration diagram does not take time as a separate dimension, so the serial number determines the order of messages and concurrent threads. A collaboration diagram is a cross product between a symbolic diagram and a sequence diagram. It uses a numbered arrow to describe a specific scheme to show the movement of messages throughout the scheme. Purpose of a collaboration diagram: describes a specific scheme by describing the movement of messages between objects. Displays the organizational structure of the object and its interaction relationships, rather than the interaction sequence. 7) activity diagram UML activity diagram records the logic of a single operation or method, a single user case, or a single business flow. Describes the execution sequence of various activities in the system. It is generally used to describe the execution process of each activity in an operation. At the same time, it is often used to describe the processing process of a case or an interactive process. An activity diagram consists of activities that are described at the same time. After an activity is executed, the control moves along the Control Transfer arrow to the next activity. In the activity diagram, the transfer control conditions and parallel execution requirements can also be easily described. (8) The component diagram is used to reflect the physical structure of the Code. From the component diagram, you can understand the compiler and runtime dependencies between various software components (such as source code files or dynamic link libraries. You can use a component diagram to divide the system into cohesion components and display the code structure. The main purpose of a component diagram is to display the structural relationship between system components. 9) The configuration diagram describes the physical configuration and system architecture of hardware and software in the system. In the configuration diagram, nodes are used to represent the actual physical devices, such as computers and various external devices, and the corresponding nodes are connected according to the connection relationship between them, and describes the connection method. In the node, describe the executable components or objects allocated to the node, and describe which software units are allocated to which nodes to run.