The "diagram" set in UML

first, the basic concept

UML as a unified Modeling language, is a model of language, then the model is mainly used to represent, this time naturally generated UML diagram. UML mainly consists of basic building blocks, rules and public mechanisms, in which the basic building blocks consist of things, relationships and graphs. II. Basic Structure

Diagram is an important part of UML, then there are nine kinds of UML diagram, can be divided into package diagrams, use case diagram, class diagram, behavior diagram, implementation diagram, the main classification as follows:

ii. functions of UML diagrams 1. Package Diagram

Package diagrams is a hierarchical structure used to describe a system, consisting mainly of packages or classes, representing the relationship between packages and packages 2, use case diagrams

Use case diagrams are used to describe the connection between roles and use cases. It explains who wants to use the system and what they can do with the system. A use case diagram contains several model elements, such as systems, actors, and use cases, and shows the various relationships between these elements, such as generalization, association, and dependency. 3. Class Diagram

A class diagram is a static view that describes a class in a system and the relationships between classes. Allows us to have a comprehensive understanding of the system before writing the code correctly. A class diagram is a model type, rather, a static model type. Class diagrams represent classes, interfaces, and collaborative relationships between them. 4. Object Graph

An object graph is similar to a class diagram, an instance of a class diagram that shows multiple object instances of a class rather than the actual class. It does not describe relationships between classes, but relationships between objects. 5. Behavior Diagram (1) state diagram

A state diagram is a condition that describes all possible states of an object of a class, as well as the state of the event when it occurs. You can capture the life cycle of objects, subsystems, and systems. They can tell the state that an object can have, and how the event will affect those states over time. A state diagram should be connected to all classes that have a clear, identifiable state and complex behavior, which determines the behavior of the class, how the behavior changes depending on the current state, or what events will change the state of the object of the class. A state diagram is a complement to a class diagram. (2) activity diagram

Activity diagrams are activities that describe the requirements of use cases, as well as constraints between activities, which facilitates the identification of parallel activities. The ability to demonstrate where features exist in the system and how these functions and the capabilities of other components of the system work together to meet the requirements of using use case diagram modeling earlier. (3) Interactive diagram ① sequence Diagram

Sequence diagrams are also called sequence diagrams, which are models that show how your participants interact with the system's objects in a series of sequential steps. Used to show how objects interact with each other. Focus the display on the message sequence, emphasizing how the message is sent and received between objects ② collaboration diagram

Also known as the collaboration diagram, showing the dynamic relationship between objects. Can be seen as the intersection of a class diagram and a sequence diagram. 6. Realization Diagram (1) Component Diagram

Called component diagrams, which describe the physical structure of code artifacts and the dependencies between the various constructs. Component graphs are composed of component markers which conform to the relationship between components. Component enables a file, product, executable, and script (2) deployment diagram

The physical deployment used to model the system. such as computers and devices, and how they are connected. It is used to represent a set of physical nodes and the relationship between nodes, thus establishing a model of the system physical level.

Iv. Application

1. Demand Phase

Use case diagrams to describe requirements (roles, functions, external interactions) 2, analysis phase in order to clarify the details of the problem, the class diagram is used to describe the static structure, the behavior diagram to describe the dynamic behavior, of course, the behavior diagram includes the state diagram, activity diagram, interaction diagram, The interaction diagram includes the sequence diagram and the collaboration Diagram 3, the design phase in order to give the solution, the class diagram and the package diagrams to the class interface design 4, implementation phase to implement the class in an object-oriented language implementation of 5, Integration and delivery phase package and implementation diagrams, where implementation diagrams include component and deployment diagrams 6, test phase using class diagrams and class specifications in unit tests use class diagrams, Package diagrams, component diagrams, and collaboration diagrams in integration testing Use use case diagrams to test system functionality in system tests