1. Determine the domain model. Clear the general business logic
2. Determine the use case, divide the activity diagram according to the user, and add the sequence diagram under the activity diagram
The general activity diagram is the call between systems or modules, and the central idea in the process will be studied.
Sequence diagrams are method-level calls
ps: The activity diagram can be added again as a flowchart under the sequence diagram
At this point, the calling relationship between systems can be synchronously defined (output system dependency graph and deployment graph)
3. Convert the concepts in the domain sequence diagram into physical design and establish a class diagram