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

This article mainly introduces how to use UML nine views, with certain reference value, interested friends can refer to, I hope you have a lot of gains after reading this article, let Xiaobian take you to understand.

UML Nine Views

UML includes nine diagrams: use case diagram, class diagram, object diagram, state diagram, sequence diagram, collaboration diagram, activity diagram, component diagram, configuration diagram.

1) Use Case Diagram

It is the simplest and most complex diagram in UML. It is simple because it uses object-oriented thinking, is based on the user's perspective, drawing is very easy, simple graphical representation let a person understand at a glance. It is complex because use case diagrams are often difficult to control, either too complex or too simple.

Use case diagrams in the nine UML views represent roles and use cases and the relationships between them.

2) Class Diagram

Class diagram is one of the most commonly used diagrams, which can help us understand the architecture of a system more intuitively. Class diagrams, represented by relationships and classes, graphically depict the design aspects of a system.

3) Object diagram

Object diagrams in the nine UML views are instances of class diagrams, using almost exactly the same identity as class diagrams. They differ in that the object graph shows multiple object instances of a class rather than classes of instances. An object diagram is an instance of a class diagram. Because objects have lifecycles, object graphs can exist only for a certain period of time in the system.

4) State diagram

Describes the dynamic behavior of an entity based on events, showing how the entity reacts to different times depending on the state it is currently in. A UML state diagram is usually created for research purposes: to study the complex behavior of a class, role, subsystem, or component.

5) Timing diagram

Also known as sequence diagram, describes the dynamic interaction between objects, focusing on the time sequence of message transmission between objects.

in that nine UML view, sequence diagrams consist of a set of object, each with a vertical line, called the object's lifeline, representing the Timeline, along which time extends downward. The sequence diagram describes how these objects exchange messages with each other over time. Messages are represented by horizontal arrows pointing from a vertical object lifeline to another object lifeline. You can also add time-related notes and other comments as needed.

6) Collaboration Chart

Collaboration diagrams are used to show the spatial organization of components and their interactions without focusing on the order of interactions. Collaboration diagrams show organizational interactions between objects in an interaction and links between objects. Unlike sequence diagrams, collaboration diagrams show relationships between objects. Collaboration diagrams, on the other hand, do not have time as a separate dimension, so sequence numbers determine the order of messages and concurrent threads. A collaboration diagram in the UML Nine Views is a cross product between a symbolic diagram and a sequence diagram that depicts a particular scenario with numbered arrows to show the movement of messages throughout the scenario.

Use of collaboration diagram:

Reflect specific scenarios by depicting the movement of messages between objects.

Shows the spatial organization of objects and their interactions, not the order of interactions.

7) Activity Diagram

UML activity diagrams document the logic of a single operation or method, a single user case, or a single business process. Description of the sequence of execution of various activities in a system, usually used to describe the execution flow of activities to be performed in an operation. It is also often used to describe the processing flow of a use case, or some interaction flow.

An activity diagram consists of a number of activities and includes descriptions of those activities. When an activity is completed, control moves to the next activity along the control transfer arrow. The activity diagram can also conveniently describe the conditions of control transition and the requirements of parallel execution.

8) Component Diagram

Component diagrams are used to reflect the physical structure of code. Component diagrams provide insight into compiler and runtime dependencies between software components, such as source code files or dynamic link libraries. Component diagrams are used in the nine UML views to divide a system into cohesive components and to show the structure of the code itself.

The main purpose of component diagrams is to show the structural relationships between system components.

9) Configuration diagram

The configuration diagrams in the nine UML views describe the physical configuration of hardware and software in the system and the system architecture.

In the configuration diagram, nodes represent actual physical equipment, such as computers and various external devices, and connect the corresponding nodes according to their connection relationships, and explain their connection methods. Within a node, specify the executable components or objects assigned to run on the node, thereby indicating which software units are assigned to run on which nodes

Thank you for reading this article carefully. I hope that the article "How to Use UML Nine Views" shared by Xiaobian will be helpful to everyone. At the same time, I hope that everyone will support you more and pay attention to the industry information channel. More relevant knowledge is waiting for you to learn!

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.