[UML journey] UML diagram Definition

Not many computer players have not learned much, but with the continuous development of the project, those who have never seen before, and those who have never used them are all about to start learning. Although I have heard of UML for a long time, I have never read this book and have never used this tool. The class diagrams of UML are also unknown. Basically, I don't know how to understand it. I haven't used UML for projects I 've encountered before. I don't know if it's too late to learn them now. You have to learn it if you don't know it. What about it? Work hard, fighting!

UML consists of nine different types of graphs, each of which focuses on analyzing and defining systems using different methods. These figures are briefly summarized as follows: the use case diagram shows the system's external visual behavior; the activity diagram shows the detailed description of the system behavior; and the component diagram shows the system architecture; the sequence diagram shows the interaction of objects over time. The collaboration diagram shows the interaction of objects, emphasizing the relationship between objects. The class diagram shows the class definition and relationship; the status chart shows the status change of the response event, the deployment chart shows the physical architecture of the system, and the package chart shows the hierarchical structure of the design.

The use case diagram describes the actions of people and systems outside the system and the responses of the system. This type of diagram can be used to describe the functional requirements of the system.

The activity diagram describes the detailed behavior within a single functional requirement, including basic scenarios and optional scenarios. This diagram can be used to ensure a thorough understanding of a given function.

The component diagram describes the deployable units of the system (executable files, components, data storage and other content) and some interfaces through which the deployable units interact. This figure can be used to study the system architecture.

A sequence diagram describes the path of a function requirement or detailed behavior of relative time in a scenario. This figure can be used to understand the message flows between system elements.

A class diagram describes the classes and interfaces in the system design and their relationships. This graph can be used to define internal, object-orientedCodeStructure.

The status chart describes how the system changes its status to respond to internal and external events. This graph can be used to ensure that each event is properly handled, regardless of the current state of the system.

The deployment diagram describes how the system's deployable units (applications, components, data storage, etc.) are assigned to different nodes, how these nodes communicate with each other, and how these nodes communicate with devices. This figure can be used for system ing or for studying system loads.

The package diagram describes how elements of the design are combined by group and how these groups depend on each other. This diagram can be used to divide complex designs into smaller designs that are easier to manage.

Today, I got to know the basic concepts of Several UML diagrams, but I think the most important thing for our developers is class diagrams. This is just my guess, I have seen class diagrams before, and can also see class diagrams in.