You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When class A inherits, extends or includes class B we currently draw a dependency X from A to B.
A----->B
X (inheritance/extension/inclusion)
We show a dependency Y from class B to class A when class B calls some method of class A (like in the template method pattern).
A<-----B
Y
So in this cases the relationship between class A and B becomes bidirectional.
A<---->B
X+Y
The diagram would be clearer if we remove dependency Y and just leave X, given that we somehow indicate that dependency X is based on inheritance/extension/inclusion.
When class A inherits, extends or includes class B we currently draw a dependency X from A to B.
We show a dependency Y from class B to class A when class B calls some method of class A (like in the template method pattern).
So in this cases the relationship between class A and B becomes bidirectional.
The diagram would be clearer if we remove dependency Y and just leave X, given that we somehow indicate that dependency X is based on inheritance/extension/inclusion.
So this feature will be done after issue #3
The text was updated successfully, but these errors were encountered: