Key Points of various diagrams in UML -bokee.net

 

Key Points of various diagrams in UML

Font size: large | medium | small:-read: 141-Comment: 0

Key Points of various diagrams in UML

Class diagram: class diagram shows a group of classes, interfaces, and collaboration and their relationships. The most common graph created in modeling is class diagram. Use a class diagram to describe the Static Design view of the system, including the class diagram of the active class-focusing on the static process view of the system. The system can have multiple class diagrams. A single class diagram only expresses one aspect of the system. The primary responsibilities of the class should be given at the high-level level, and the attributes and operations of the class should be given at the lower level.
Object graph: an object graph shows a group of objects and their relationships. The object graph is used to describe the data structure and static snapshot of the transaction instance in the class graph. An object chart has a static design view or a static process view of the system. It serves the same role as a class chart except for the reality and prototype.
Use case diagram: the use case diagram shows a group of use cases, participants, and their relationships. You can use an example to describe the static usage of the system. In terms of system behavior organization and modeling, the use case diagram is very important.
Interaction diagram: an interaction diagram shows a type of interaction for a certain purpose. It consists of a group of objects in a context and the information of interaction between them. An interaction diagram can also be used to describe the behavior of a use case. The sequence diagram and the cooperative plot are Interactive graphs, and the sequence diagram and the cooperative plot can be converted to each other.
Sequence diagram: displays a group of objects and messages sent and received by these objects. It is used to model the control flow in chronological order. The sequence diagram is used to describe the dynamic view of the system.
Collaboration diagram: displays a group of objects, the connections between these objects, and the messages sent and received by these objects. It emphasizes the structure of the message receiving and sending objects and models the control flow based on the organizational structure.
Status chart: shows all possible states of a specific object and the transition between States caused by various events. A state chart describes a state machine and uses a state chart to describe the dynamic view of the system. It is particularly important for modeling interfaces, classes, or collaborative behavior. It can be used to describe the lifecycle of the use case instance.
Activity diagram: An activity diagram is a special state chart that describes the activities to be performed, the order in which these activities are executed (mostly parallel), and the workflow (steps required to complete the work ). It is particularly important for system function modeling, emphasizing the control process between objects.
A high-level activity diagram is used to show the tasks to be completed, that is, to analyze the use cases, to understand the workflows, multithreading, and parallelism involving multiple use cases, and to display the overall interaction behavior, it can also be used to model enterprise processes and system functions. The low-level activity diagram is used to represent the class method. However, the activity diagram does not apply to describing the relationship between actions and objects, displaying the cooperation between objects and the running status of objects within the lifecycle.
Component diagram: A component diagram shows the organization and dependency between a group of components for modeling of the original code, executable releases, physical databases, and adjustable systems.
Deployment diagram: the deployment diagram shows the configuration of the processing nodes and components in the runtime. It describes the physical topology of the system hardware (including the network layout and the position of components on the network ), and the software executed in this structure (that is, the distribution of software components in the node during the runtime ). A deployment diagram is used to describe the static deployment view of the system structure, that is, the physical system for distribution, delivery, and installation.

Key Points of various diagrams in UML -bokee.net