UML (iii) -- Sort nine types of diagrams

The knowledge of UML has been learned for a while, and the understanding of the nine types of diagrams has changed a lot since I did not understand it before. The viewpoint on pure theoretical knowledge of software engineering has also changed, it tastes a little bit better.

In my opinion, the nine diagrams of UML are different understandings of a system at different stages or from different angles. In fact, they are all about one thing. Just like a computer, some people have a computer. In our opinion, it is a learning tool. In the opinion of the maintenance personnel, it may be a pair of parts. They have different understandings from different angles. The nine diagrams of UML are always accompanied by the project process. In what order should we draw a picture for a project?

Let's talk about my knowledge. When we get a project, we only face users. We need to analyze and abstract the functions described by the project according to the user's needs. Therefore, the first figure is an example diagram; after the use case diagram is drawn, we abstract the famous words based on the description information, and then abstract the class. The second is the class diagram, which establishes a static relationship; the third is the use case in the tool use case diagram to analyze each use case and draw the corresponding sequence diagram. Because the sequence and Coordination diagram are the same, the fourth is the collaboration diagram; fifth, we will analyze and draw an object chart for the class. Sixth, we will draw a state chart based on the different states of the class in each stage. The seventh is the activity diagram, because the activity diagram corresponds to the state chart; the last step is the component diagram, which describes the relationship between the components in the system. The ninth step is the deployment diagram.