When you want to describe a process, use the activity diagram to represent it.
Add a folder called "Shopping" in your project.
Drag and drop the "Orders Model" UML class diagram into the shopping folder.
Create an activity diagram for shopping first.
Under the shopping folder, create a UML activity diagram called "Browse Toys."
Drag an initial node to the main interface, which indicates where the activity started.
Drag a number of actions to the interface.
Drag the end node to the interface.
Add a connection between the start point, the action, and the end point.
If there is one more possibility between the "put the toy in the cart" and the "checkout" operation, it is possible to checkout, possibly to return to the "Select a category" action, how to do it?
You need to add a decision node between the two.
Add a connection line between the action and decision nodes.
If you want to give the link a note name, set it in the Guard property.
Then put the grain size smaller, the activity chart about the checkout.
Add an activity diagram called "Checkout".
Now, we hope that in the "Browse Toys" activity map, click "Checkout" to link to "Checkout" this activity diagram.
Remove the "checkout" action from the "Browse Toys" activity diagram and add a "Call behavior action" instead and add the connector by setting the value of the "Checkout" property in its Behavior property.
Note:
Consider using the activity diagram when designing the process
An activity diagram can be understood as a sequential concatenation of use cases
Activity diagrams try to describe only one activity
Activity diagram can be based on different granularity, such as above, when involved in shopping, the checkout operation is a part of the shopping activity diagram, when it comes to checkout, you can put the shopping activity diagram of the checkout operation to expand, and to two activity diagram to add a link
Reference: https://channel9.msdn.com/Blogs/clinted
Using activity diagrams in Visual Studio to describe business processes