Representing Scenario with Behavior Diagrams
Suppose we have such a lower level detailed design related to a member registration process:
- register new member
- fill in information
- create a member
- update personal information member
- insert new member object to the database
We can used different behavior diagrams to represent the above scenario. Now let’s use a MVC architectural pattern to represent the scenario using interaction diagrams and a swinlaned activity diagram:
1. Using Communication Diagram
2. Using Sequence Diagram
3. Using Activity Swinlane
