Open aweijun opened 2 years ago
Internally, we use an empty link object to represent no links rather than using null so that we can avoid NullPointerException
s. So, it is correct that our UML diagram reflects 0..1
Team chose [response.Rejected
]
Reason for disagreement: ## Explanation
I understand your rational of using an empty link object. However, this doesn't change the problem of that labelling the multiplicity as 0, would no doubt implies that it is possible for the Task class to not be assigned to a Link object at all.
However considering this was never mention within the DG nor was there any disclaimer made in advance, as such this would no doubt lead to misunderstandings, which was why I flagged it out as an issue in the first place.
You informing me of your rationale, that this issue would lead to misunderstanding when developers first look at your UML diagram.
Team chose [severity.VeryLow
]
Originally [severity.Low
]
Reason for disagreement: This would affect the understanding of developers and hence, it would be labelled under severity.Low.
Current
Suggestion
Unlike what is stated in the DG, a empty link object its created if the field is left empty. Therefore, should the multiplicity show 1 instead?