-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Class Diagram: Default value for unmentioned multiplicity #196
Comments
must be associated means there should be a |
Does unmentioned default to If not, what does it default to, if any? |
It does not default to anything. It is unknown. |
Am I correct in saying this: If the arrow is like this Container → Lid it means that only Container knows about Lid. ie Container is associated with Lid. But Lid is NOT associated with container But Lid definitely does not know about Container right? ie Lid is NOT associated with Container Because if it does, then it would be: Container — Lid without the arrow head (navigability) |
Don't confuse navigability with association. If A is associated with B, B is automatically associated with A, irrespective of the navigability.
|
Thank you, that clears things up! |
I have a question regarding unmentioned multiplicities in class diagrams. From the sample paper, I assumed that unmentioned multiplicities meant that it holds a default value to 1, but I’m not sure whether that assumption affects my answer for the following questions. Could I clarify whether my assumption is true in the module and whether it affects the explanation of my answers?
A13. A Lid must be associated to a Container but it is optional for a Container to have a Lid.
The stated answer is (B). This is because the association label could be a Lid#close(Container) method, hence this is a dependency from Lid to Container instead of an association. This possibility also counters the given code scenario in A17.
The text was updated successfully, but these errors were encountered: