Understanding of UML modeling and graphic organization in software development (3)

Labels: UML modeling software development OOAD graphics

Next, let's continue with the content in the previous section to learn about several types of static modeling and Dynamic Modeling in UML.

3. object graph: Displays the features of multiple objects and interactions between objects. Take traveling and traveling using transportation as an example,

Note: An object graph exists only for a certain period of time in the system and can be considered as an instance of a class graph at this time point. It is mainly used to describe the behavior between objects.

Iv. Component DiagramThe component diagram is used to describe the relationship between components in the software. It is also a modular element of the system design. A component is a physical part that can be replaced in the system. It encapsulates the implementation of classes and provides a set of interfaces for objects. During software development, components meeting the same interface can be freely replaced. Take the library as an example:

5. Deployment Diagram: Displays the information of the physical device used to deploy the software application. It describes the hardware node when the system is running. A deployment diagram consists of two important elements: the connection between a physical node (processor/device) and a physical node (which can be added with a connection name/constructor ).

Vi. Timeline chartThe sequence diagram and sequence diagram are mainly used to capture the interaction between multiple objects within a period of time and emphasize the time sequence of message interaction.

Note: The Sequence Chart consists of an optional, object (actor), lifeline, focus of control, and message.
System role: it can be a person or another subsystem.
Object: the object includes three naming methods: the first method includes the Object Name and class name; the second method only displays the class name but not the object name, indicating that it is an anonymous object; in the third method, only the object name is displayed, but the class name is not displayed.
Lifeline: Also known as a timeline, it indicates a dotted line extending down from the object icon, which indicates the time when the object exists.
Control focus: indicates the time period symbol (represented by a small rectangle located on the Life Line). During this time period, the object will perform corresponding operations.

Messages: mainly include the following types
① The sender of the synchronous (CALL) message transfers the control to the receiver of the message, and then stops the activity, waiting for the receiver to give up or return the control.
② Asynchronous message (asynchronous message) The message sender transmits the signal to the receiver of the message and continues his/her own activities without waiting for the receiver to return the message or control it. The receiver and sender of asynchronous messages work concurrently.

③ Return message is returned from the process call.

VII. status chartThe state transition diagram emphasizes the internal state transition process of an object when it is triggered by different events. Here is a simple picture:

8. activity diagram: Describes the activity process. It is a technology that expresses the process basics, business processes, and workflows. Here is a simple picture:

IX. Collaboration DiagramA collaboration diagram is used to represent the collaboration information between objects within a certain range, emphasizing the organizational structure between objects involved in information exchange. A collaboration diagram shows the relationship between a series of objects and those objects, as well as the messages sent and received between objects. It is a variant of the sequence diagram.

For more information, see networks.

Summary
In the past two days, nine types of core UML diagrams in UML static and dynamic modeling were reviewed and summarized, which were not mature. To better use and use UML modeling ideas, we need to apply and strengthen them in the project.

Understanding of UML modeling and graphic organization in software development (3)