UML Time series diagram

A time series diagram is a diagram that shows interactions between objects. It shows dynamic collaboration between multiple objects by describing the chronological order in which the messages interact between objects.

Time series diagrams are used to denote the order of behavior in a use case, and when a routine is performed, each message in the sequence diagram corresponds to a class operation or event that causes a transition in the state machine; time series diagrams show the interactions between objects that occur in the event stream of a scene or use case, and the sequence diagram focuses on the message Describes how messages are sent and received between objects, and time series diagrams can be used to describe use cases and find operations for classes.

The modeling elements included in the time series diagram are: Objects, lifelines, activations, messages, etc.

The timing diagram of Kingdoms's Battle of Chibi:

First, the role

The villain in the picture shows a role, which can be human, or other system or subsystem.

　　

Second, the object

An object is a class or class object. Named by: Object Name: Class name, you can omit any one of them.

The left and right order of the objects is not important, but in order to make the picture clear and tidy, you should usually follow the two principles:

(1) Move the objects with frequent interactions as close as possible.

(2) The object that initializes the entire interaction (sometimes a participant) is placed on the leftmost side.

　　

Third, the lifeline

A lifeline is a dashed line that extends downward from the object's icon, indicating the object's time to live.

　　

Iv. activation (Control focus)

The control focus is the symbol representing the time period in the sequence diagram, during which the object performs the appropriate action. Represented by a small rectangle on each lifeline.

When an object is not activated, the object is dormant and nothing is done, but it still exists and waits for a new message to activate it. When a message is passed to an object, it triggers a behavior of that object, which means that the object is activated. When an object is in the active period, it indicates that the object is in the execution of an action.

The height of the rectangle indicates the time period during which an object performs an operation, and the top of the rectangle represents the beginning of the action, and the bottom represents the end of the action.

An object can be completed by one of its own actions after receiving a message, or by another object's operation.

　　

V. News

A message is a mechanism of communication between objects. The operation by which the sending object sends a signal to another or several receiving objects, or an object invokes another object.

The interaction between objects is accomplished by sending messages to each other. An object can request or require another object to do an event.

The message points from the source object to the target object. In time series diagrams, the reading order of messages is strictly top-down.

　　

Messages are generally divided into synchronous messages (synchronous message), asynchronous messages (asynchronous message), and return messages.

Synchronous message (Call message): The sender of the message passes control to the recipient of the message, and then stops the activity, waiting for the recipient of the message to discard or return control. Used to indicate the meaning of synchronization.

Asynchronous message: The sender of the message passes the message to the recipient of the message and then resumes its activity without waiting for the recipient to return the message or control. The recipient and sender of an asynchronous message are working concurrently.

Return message: The return message represents a return from a procedure call

Self-correlating message: Represents the method's own invocation and one method within an object that calls another method.

　　

Some places also divide the message into ordinary messages, synchronous messages, asynchronous messages, and return messages.

　　

Liu, Combined fragments

Represents a message sent with some specific criteria.

　　

For example, the loop sends the GetProperty message to get the property. When you draw a sequence diagram, after you select a combined fragments, you can change the corresponding send condition in its corresponding properties panel. For example:
1.Alternative fragment (denoted "alt") corresponds to If...then...else
2.Option fragment (denoted "opt") corresponds to switch
3.Parallel fragment (denoted "par") indicates simultaneous occurrence
4.Loop fragment (denoted "Loop") corresponds to for or foreach

Vii. Other

Performer, indicating who the object is to be manipulated by.

Enter the window and the code starts here.

Interface that represents an interface that interacts with other applications

Missing message

UML Time series diagram