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

This article will explain in detail what are the main points of the ten kinds of UML diagrams. The editor thinks it is very practical, so I share it with you as a reference. I hope you can get something after reading this article.

Class diagram:

A class diagram shows a set of classes, interfaces, and collaborations and the relationships between them. The most common diagram established in modeling is a class diagram. Use the class diagram to illustrate the static design view of the system, including the class diagram of the active class-the static process view that focuses on the system. The system can have multiple class diagrams, and a single class diagram represents only one aspect of the system. The main responsibilities of the class should be given at the high level, and the properties and operations of the class should be given at the lower level.

Object graph:

The object graph in the ten diagrams of UML shows a set of objects and their relationships. The object diagram is used to illustrate the data structure and static snapshot of the instances of things reflected in the class diagram. The object diagram expresses the static design view or static process view of the system, which is the same as the class diagram except for the factors of reality and prototype.

Use case diagram:

A use case diagram shows a set of use cases, actors, and the relationships between them. Use case diagrams can be used to describe the static usage of the system. Use case diagrams are very important in organizing and modeling system behavior.

Interaction diagram:

Among the ten diagrams of UML, the interaction diagram shows an interaction for a certain purpose, which consists of a set of objects in a context and the information that they interact with. Interaction diagrams can also be used to describe the behavior of a use case. Sequence diagrams and collaboration diagrams are interaction diagrams, and sequence diagrams and collaboration diagrams can be transformed into each other.

Sequence diagram:

Presents a set of objects and messages sent and received by this set of objects for modeling the control flow in chronological order. A sequence diagram is used to illustrate the dynamic view of the system.

Collaboration diagram:

Shows a set of objects, the connections between them, and the messages sent and received by this group of objects. It emphasizes the structural organization of the objects that send and receive messages, and models the control flow according to the organizational structure.

State diagram:

Shows all possible states of a particular object and the transition between states caused by the occurrence of various events. One of the ten diagrams of UML describes a state machine and uses it to illustrate the dynamic view of the system. It is particularly important for behavioral modeling of interfaces, classes, or collaborations, and can be used to describe the lifecycle of use case instances.

Activity diagram:

An activity diagram is a special state diagram that describes the activities that need to be done, the order in which they are performed (often in parallel), and the workflow (the steps required to get the job done). It is especially important for the functional modeling of the system, emphasizing the control flow between objects.

High-level activity diagrams are used to represent some tasks that need to be completed, that is, to analyze use cases, to understand workflows, multithreading and parallelism involving multiple use cases, to show interrelated behavior as a whole, and to model enterprise processes and the functions of the system. The low-level activity diagram is used to represent the method of the class. However, the activity diagram is not suitable to describe the relationship between actions and objects, to show the cooperation between objects and to show the operation of objects in the life cycle.

Component diagram:

Component diagrams in the ten diagrams of UML show the organization and dependencies of a set of components for modeling original code, executable releases, physical databases, and adjustable systems.

Deployment diagram:

The deployment diagram shows the deployment of the runtime processing node and its components. It describes the physical topology of the system hardware (including the network layout and the location of components on the network), as well as the software executed on this structure (that is, the distribution of runtime software components in the nodes). Use the deployment diagram to illustrate the static deployment view of the system structure, that is, the physical system that is distributed, delivered, and installed.

This is the end of this article on "what are the main points of the ten UML diagrams?". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

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.