Multi-threading is not a static concept, it can only be reflected at runtime, so if you want to visualize it, you have to use a graphic to represent it, which itself has entered a misunderstanding
That’s it: the score and parts of a symphony performance
Think of each instrument as a thread. How can many instruments cooperate to play a complete and beautiful symphony? It is to arrange a certain instrument to play the right note at the right time. The score is a multi-thread timing schedule diagram. Beat is a timer. The conductor is the scheduler.
Sequence diagram?
Multi-threading is not a static concept, it can only be reflected at runtime, so if you want to visualize it, you have to use a graphic to represent it, which itself has entered a misunderstanding
This has long been solved in the music industry,
That’s it: the score and parts of a symphony performance
Think of each instrument as a thread. How can many instruments cooperate to play a complete and beautiful symphony?
It is to arrange a certain instrument to play the right note at the right time.
The score is a multi-thread timing schedule diagram.
Beat is a timer.
The conductor is the scheduler.
uml activity diagram https://en.wikipedia.org/wiki...