UML Notes
UML (Unified Modeling Language), Unified Modeling Language. It is a language for specifying, visualizing, and documenting the products of an object-oriented development system. Simply put, it's the product description.
UML diagrams are roughly divided into static diagrams and dynamic diagrams
- use case diagram
【Concept】Describe user needs, describe the function of the system from the user's point of view
[Description method] The ellipse represents a use case; the human-shaped symbol represents the role
[Objective] To help the development team to understand the functional requirements of the system in a visual way
- Class Diagram
[Concept] Shows the static structure of the system, showing how different entities are related
【Description】Three rectangles
[Purpose] Represents a logic class or implementation class. The logic class is usually the things involved in the user's business; the implementation class is the entity handled by the programmer.
- Object graph
[Concept] An instance of a class diagram, describing the objects contained in the system at a specific point in time and the relationship between each object
- Interaction diagram
- Sequence diagram
[Concept] Describe the interaction sequence between objects, emphasizing the time sequence of message passing between objects
[Description method] Across the top of the figure, each box represents an instance or object of each class; the class instance name and class name are separated by colons
[Purpose] To display the calling relationship between different objects in the process, and also display different calls of different objects.
- - Collaboration diagram
[Concept] Describe the cooperative relationship between objects, focusing on message passing between objects
Behavior diagram
== describes the dynamic model of the system and the interaction between objects ==- State diagram
[Concept] Describe all states of an object and transitions between states caused by events
[Description method]
Starting point: solid
circle Transition between states: line segment using open arrows
State: rounded rectangle
Judgment point: hollow circle
One or more end points: a circle containing a solid circle inside[Purpose] Indicates the different states of a class and the transition process of the class in these states
- activity diagram
[Concept] Describe the activities to be performed to meet the requirements of the use case and the constraints of the activity time
[Description method]
Start point: solid circle
Activity : rounded rectangle
End point: circle with solid circle inside
Swim lane : the object that actually executes the activity[Purpose] Represents the process control flow between two or more objects when processing an activity
Difference between activity diagram and state diagram
Implementation diagram
- component diagram
[Concept] Describe the physical structure of code components and the dependencies between components
【Description】Component
[Objective] Provide a physical view of the system, and display the entire physical structure of the system code according to the code components of the system
- Deployment diagram
[Concept] The physical architecture of the hardware in the system
[Description method] The
three-dimensional cube represents the component, and the
node name is located in the upper part of the cube【Objective】Display the physical structure of the hardware and software of the system
