Open javinchua opened 9 months ago
Thanks for raising this up!
Since it is obvious that the object that was just created is being returned, the omission of explicitly stating it is allowed. It is clear since the object was just initialized by the method calling it.
You can refer to this diagram from the textbook:
We feel that the severity should be VeryLow, since this is just a slight cosmetic issue, unimportant to user understanding.
Team chose [response.Rejected
]
Reason for disagreement: While it is true that the return object is optional, your current diagram is still inconsistent with the rest of the sequence diagrams in the DG, which can cause some confusion as to why the return object is indicated in some cases but omitted in this one. To ensure clearer understanding, it is vital that sequence diagrams have consistency. I have attached below some screenshots of sequence diagrams from other parts of your DG.
c
andresult
should have been returned respectively in the immediate return arrow but it is omitted and only shown in the following return arrow.