Talking about the concept and model of UML nine kinds of UML diagrams

content:

       1. UML的视图
       2. UML的九种图
       3. UML中类间的关系

We have introduced above, the view of UML, in each kind of view contains one or more kinds of diagrams. In this article, we focus on the details of each UML diagram:

1. Use case diagrams
   [Concept] Describe user requirements and describe system functions from the user's point of view
   [Description method] An ellipse represents a use case; a human-shaped symbol represents a role
   [Purpose] Help the development team to understand in a visual way Functional requirements of the system
   [use case diagram]
   

2. static image

   1. Class diagrams
      [Concept] Shows the static structure of the system, showing how different entities are related
      
      [Description] Three rectangles
      [Purpose] Represents a logical class or implementation class, and the logical class is usually the user's business The things involved; the implementation class is the entity handled by the programmer
      [class diagram]
      
      2. object diagrams
      [concept] An instance of a class diagram that describes the objects contained in the system at a specific point in time and the relationship between each object
      [ Object diagram]
      

3. Interaction diagram
   Used to describe the interaction between objects Each box represents the instance or object of each class; the class instance name and the class name are separated by colons [Purpose] To display the calling relationship between different objects in the process, and also to display different calls of different objects. [Sequence diagram] 2. Collaboration diagrams [Concept] Describe the cooperative relationship between objects, focusing on message passing between objects
   
   
   
   
   
   
   
   

4. 
   Behavior diagram : describe the dynamic model of the system and the interaction between
   objects
   

   1. Starting point: filled circle
   2. Transitions between states: line segments using open arrows
   3. Status: Rounded Rectangle
   4. Judgment point: hollow circle
   5. 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
   2. Activity diagrams
   [Concept] Describes the activities to be performed to meet the requirements of the use case and the constraints of the activity time
   [Description method] 】

   1. Starting point: filled circle
   2. Activity: Rounded Rectangle
   3. End point: a circle containing a solid circle inside
   4. Swimlane: The object that actually performs the activity

   [Purpose] Indicates the process control flow between two or more objects when processing an activity
   [Activity diagram]
   
   The difference between an activity diagram and a state diagram:
   

5. Implementation Figure
   1. Component diagrams
   [Concept] Describe the physical structure of code components and the dependencies between
   components [Description method] Component
   [Purpose] Provide a physical view of the system, and display the system code according to the system's code components The entire physical structure
   [architecture diagram]
   
   2. Deployment diagrams
   [Concept] The physical architecture of the hardware in the system
   [Description method]

   1. 3D cube representation part
   2. The node name is in the upper part of the cube

   【Purpose】Display the physical structure of the hardware and software of the system
   【Deployment diagram】
   

The detailed explanation of the nine UML diagrams ends here. The next article is dedicated to explaining the relationship between classes in UML. Thank you for your visit.