UML Diagrams

1. The concept of UML

    Unified Modeling Language (UML) is a unified modeling language, also known as a standard modeling language. It is a language used to visually model software-intensive systems. The definition of UML includes two elements: UML semantics and UML notation.

2. The effect of UML

    The goal of UML is to describe any type of system in an object-oriented diagram, which has a wide range of applications. The most commonly used model is to build software systems, but it can also be used to describe systems in non-software fields, such as mechanical systems, corporate institutions, or business processes, as well as information systems that process complex data, industrial systems or industries with real-time requirements Process etc. In short, UML is a general standard modeling language that can model any system with static structure and dynamic behavior, and is suitable for different stages of system development, from the description of requirements to the completion of the system's testing and maintenance.

3. The main model of UML

    There are three main models in UML system development:
        3.1 Functional model. Show the functions of the system from the user's perspective, including use case diagrams.
        3.2 Object model. Use concepts such as objects, attributes, operations, and associations to show the structure and foundation of the system, including class diagrams, object diagrams, and package diagrams.
        3.3. Dynamic model. Show the internal behavior of the system. Including sequence diagram, activity diagram, state diagram.

4. Types of UML diagrams (based on UML2.0)

        4.1 Use case diagram: describe system functions from the user's perspective.
        4.2 Class diagram: describe the static structure of the classes in the system.
        4.3 Object diagram: the state of multiple objects in the system at a certain moment.
        4.4 State diagram: describes the state-to-state control flow, often used for dynamic characteristic modeling.
        4.5 Activity diagram: describes the workflow of the business realization use case.
        4.6 Sequence diagram: dynamic cooperative relationship between objects, emphasizing the order in which objects send messages, and showing the interaction between objects.
        4.7 Collaboration diagram: describe the assisting relationship between objects.
        4.8 Component diagram: a special UML diagram to describe the static realization view of the system.
        4.9 Deployment diagram: Define the physical architecture of the software and hardware in the system.
        4.10 Package diagram: a diagram for grouping and sorting the model elements that constitute the system.
        4.11 Combined structure diagram: a diagram representing a class or building an internal structure.
        4.12 Interaction overview diagram: Use an activity diagram to represent the control relationship between multiple interactions.

5. Drawing software

        Drawing software: StarUML, etc.