Let's take a look at the theory:
The sequence diagram is an interactive diagram (interaction digram ). an interactive chart is used to describe how object instances work together and transfer information between objects in usecase. the interaction diagram includes a sequence diagram and a collaboration diagram ).
The sequence chart highlights the chronological order. The abstract level (granularity) is divided into the specification level and the instnace level ).
In together, you can easily generate a sequence chart for an existing method and convert the Sequence Chart into a co-occurrence diagram. (The Coordination diagram does not seem to be of great significance ).
Together can also be generated for sequenceCodeThis function is useful and should be suitable for overview/Detailed Design:
1. Automatic Generation Method
2. automatically generate code
3. Change the method/parameter on the graph to refactor the code.
4. The sequence of the called method can be drawn together to generate code together.
5. can represent the general try/catcht/If else/while/for Logic
6. The comments are distributed to the generated code.
Disadvantages:
Some codes that are not shown in the diagram are often critical and cannot be displayed.
The reverse-generated sequence diagram shows the relevant objects at a glance, which is easier to understand.
The Calling sequence can be easily expressed during the outline design.
In turn, will it be tiring to design a sequence diagram for each method in detail?
Ask experienced friends to talk about sequence usage at work.