Remember, I first learned UML in winter and snow.

Every time I start to learn a new course, I will always pick up a book called the basics of ×××. Of course, the journey of a thousand miles begins with a full step. Let's first learn the basics of UML.

In the book "UML basics and Rose modeling", the UML overview is mentioned in the second chapter. The first chapter is about object-oriented. From the very beginning, the first language VB came into contact with object-oriented systems. Here we review the concepts, features, and methodologies of object-oriented systems.

In terms of object-oriented modeling, there have been many excellent object-oriented development methods. However, in order to enable developers of different degrees and fields to communicate well in the development system, A unified modeling language has been established and becomes the standard of the modeling language, that is, the UML we use. Standardization is mentioned in information resource management, and it is difficult for information without standards to maximize its value. I believe that many things develop or establish unity to achieve standardization.

The following is a UML diagram, which mainly involves understanding UML in terms of model elements, public mechanisms, object constraint language, and objectives.

UML models the system architecture from different perspectives, forming different views of the system, including static view, Case view, InterAction view, implementation view, state machine view, activity view, deployment view, and model management view. To put it bluntly, UML is a tool. The following describes the application of UML in the software development stage.