Table of contents
Overview:
The view of UML is composed of nine views, namely use case diagram, class diagram, object diagram, state diagram, activity diagram, sequence diagram, collaboration diagram, component diagram, and implementation diagram. We can divide these 9 types of diagrams into two categories: static diagrams and dynamic diagrams according to their functions and purposes.
1. Use case diagram
-Use case diagrams: Used to describe user needs, describe the functions of the system from the user's perspective, and point out the performers of each function, emphasizing who is using the system, and what functions the system completes for the performers.
2.Static image
-Class diagrams: used to define classes in the system, including describing the internal structure of the class and the relationship between classes. Class diagrams are mainly used to describe the static structure of the system.
-Object diagrams: Object diagrams are relationships between various objects in a class diagram.
3. Behavior chart:
Use to describe the dynamic model of the system and the interaction between objects, including:
-Statechart diagrams: used to describe all possible states of objects of a class and transition diagrams of states when events occur
-Activity diagrams: used to describe the activities to be performed to meet the requirements of use cases and the constraint relationships between activities. The use of activity diagrams is helpful to identify parallel activities of the system
4. Interaction diagram:
Used to describe the interaction between objects, including:
·Sequence diagrams: describe the interaction sequence between objects, focus on the time sequence of message transmission between objects, emphasize the sending sequence of messages between objects, and also show the interaction process between objects.
·Collaboration diagrams: describe the cooperative relationships between objects, focusing more on explaining the message passing between those objects
·Sequence diagrams and collaboration diagrams can be converted into each other
5. Implementation diagram:
Used to describe implementation information, including:
-Component diagrams: Component diagrams are used to describe the physical structure of code construction and the dependencies between building components. A component can be a resource file, a binary file, or an executable file
-Deployment diagrams: Deployment diagrams define the physical architecture of the hardware in the system and are used to describe the actual physical devices and the connection relationships between them.