The relationship between nine diagrams of UML

In UML, nine kinds of graphs are especially important. After understanding nine kinds of graphs, what is the relationship between the nine diagrams, who first who, who leads who will become the next big problem to consider.

First of all, I summarized a picture, in this picture I combined the development cycle of the software, each phase corresponds to the corresponding UML name, so that the order between them is basically determined.

As shown in the figure above, the nine charts leading is the use case diagram, use case diagram from the user's perspective to describe the function of the system, and pointed out the operators of each function, that is, the clear system of division of labor. The developer can then design the system based on the analysis of the basic requirements of the use case diagram, which is the outline design (where the object graph is an instantiation of the class diagram). When a system has a developed model and framework, the next step is to design the details of the system, that is, the structure of the system based on the static graph of the Mo I system, which is used to describe the system behavior of three types of diagrams: interaction diagram, behavior diagram, implementation diagram. (summarized below)

1. Interaction diagram

Describes the interactions between objects, including time series diagrams and collaboration diagrams. The time series diagram shows the dynamic partnership between objects, emphasizing the order in which messages are sent between objects, displaying the interaction between objects, and collaborating diagrams that describe the collaborative relationships between objects, which are similar to sequence diagrams and show the dynamic relationships between objects. In addition to displaying information exchange, collaboration diagrams display objects and their relationships. If the time and order are emphasized, the timing diagram is used, and the collaboration diagram is selected if the subordinate relationship is emphasized.

2. Implementation diagram:

Includes component diagrams and deployment diagrams. The component diagram describes the physical structure of the code part and the dependencies between the parts, and the component diagram helps to analyze and understand the degree of interaction between the parts; The deployment diagram defines the physical architecture of the software and hardware in the system.

3. Behavior diagram:

A state diagram describes all possible states of an object of a class and the transition condition of the state when the event occurs, which is a supplement to the class diagram, which describes the activities that are required to meet the use case requirements and the constraints between activities, and facilitates identification and activity.

In this way, combined with the last blog "UML Summary of the nine models," UML used in the nine kinds of diagrams have a further understanding, with this step of understanding, the process of drawing more clearly.

You are welcome to correct me.