SA Depot

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 [...]

Responsibility and Collaboration
We could put the implementation of a single Use Case inside a single method in a single class, but it would be an object oriented design which means that the single class is the whole system itself. To make a Use Case happen, we need to realize the Use Case with a group [...]

This entry is part of, Sequence Diagram Introduction» Example:
A sequence diagram has two dimensions: the vertical dimension and the horizontal dimension, respectively representing the passage of time and the objects involved in the interaction. Object icons are placed horizontally at the top of the sequence diagram, and messages are passed between them. Figure 1 shows [...]

This entry is part of, Sequence Diagram Introduction»
A Sequence diagram is two-dimensional in nature. On the horizontal axis, it shows the life of the object instances that it represents, each having a vertical life span. On the vertical axis, it shows the sequence of the creation or invocation of these objects which are drawn [...]