Summary of UML basics and application series articles

Unified Modeling Language(UML is the abbreviation of unified modeling language.) Is a language used to visually model software-intensive systems. UML is a standard language used to describe, visualize, and document products of object-oriented development systems.

　　

The Unified Modeling Language (UML) is a non-patented third-generation modeling and Protocol language. UML is an open method for describing, visualizing, constructing, and writing products of an object-oriented software-intensive system in the development stage. UML presents a series of best engineering practices that have been validated for effective modeling of large-scale, complex systems, especially at the software architecture level.

UML can run through every stage of the software development cycle. Adopted by OMG as the industry standard.

UML is most suitable for data modeling, business modeling, object modeling, and component modeling.

　　

As a model language, UML enables developers to focus on building product models and structures, rather than selecting program languages and Algorithms for implementation. After the model is created, the model can be converted to the specified program language code by the UML tool.

1. Grasp UML as a whole. For details, refer to "What Is UML (UML summary)".

Http://blog.csdn.net/shan9liang/article/details/6723230

2. Grasp UML from the structure. For details, refer to "basic structure of UML".

Http://blog.csdn.net/shan9liang/article/details/6704851

Iii. Understanding the differences and links between classes in UML

Http://blog.csdn.net/shan9liang/article/details/6705728

4. 9 types of UML diagrams:

1. use case diagram (Use Case digoal): a diagram describing what roles can do through a certain system. use case diagram focuses on the external performance of the system.
Interaction with people, interaction between systems and other systems.

Http://blog.csdn.net/shan9liang/article/details/6706814

2. Class digraphs: Describes classes, interfaces, collaboration, and relationships between them to visualize the system's structured model.

Http://blog.csdn.net/shan9liang/article/details/6709614

3. Object digraphs: displays the relationship between objects and objects at a certain time point, reflecting the static process of the system. Object graphs are also seen as examples of class diagrams.

Http://blog.csdn.net/shan9liang/article/details/6712867

4. Activity diagram (Activity
Digoal): displays business or software processes in the form of workflows through a series of operations.

Http://blog.csdn.net/shan9liang/article/details/6713085

5. status chart
Digoal): Describes all possible states of a specific object and the transfer between States caused by various events.

Http://blog.csdn.net/shan9liang/article/details/6716242

6. Sequence
Digoal): Describes the order of information interaction between the objects involved in interaction and their objects. It can be converted to a collaboration chart.

Http://blog.csdn.net/shan9liang/article/details/6718412

7. Collaboration
Digoal): describes the relationship between a series of objects and those objects, as well as the send and receive messages between objects. Also known as "Cooperation diagram"

Http://blog.csdn.net/shan9liang/article/details/6719736

8. Component diagram: consists of components such as source code files, binary code files, executable files, or dynamic link libraries.
The dependency is connected.

Http://blog.csdn.net/shan9liang/article/details/6719701

9. Deployment diagram: displays the physical architecture of software and hardware in the system. From the deployment diagram, you can learn about
Physical relationships between nodes and component distribution of processing nodes.

Http://blog.csdn.net/shan9liang/article/details/6719721

5. Understand the RUP

Rational Unified Process (RUP) is an object-oriented and network-based programming methodology.

Http://blog.csdn.net/shan9liang/article/details/6723229

Summary: The above is a summary of the UML basics and application series. These articles refer to the notes and UML books of the UML video course and some blogs from the industry, related content on some websites. I hope these articles can bring you and help yourself. If there are any mistakes, I hope you can point out and make progress together.

Finally, for example, the process of learning UML is like a chicken nest (or even a chicken nest won't be built, only bricks are stacked and tiles are placed: hitting the Code) construction workers begin to learn how to design and build high-rise buildings. A successful software engineer must build high-rise buildings like a building master, rather than building bricks like construction workers. Learning UML is a necessary stage for successful software engineers.