In the current system, some functions / use cases may require several steps to complete their entire procedure. The examples are similar to user registration, which can contain two steps: inserting a user record into the database and activating email. Or to transfer money to netbank, this requires the stage of filling in the transfer information and checking the SMS before the actual transaction. I want to know how to draw a sequence diagram for such functions / use cases.
To be more specific, I drew a sequence diagram for an example of user registration using the MVC template shown below. In this diagram, the two steps are separated by a red line. I will also skip logic that handles errors or exceptions, such as invalid input or a username already existing in the database, to simplify it. It looks like there are so many objects on this diagram, should I draw a sequence diagram this way? Or is it better to use 2 sequence diagrams for each step?
source
share