Open sweijie24 opened 5 months ago
A for each loop is used, but there is no way to properly represent it in a UML diagram.
Team chose [response.Rejected
]
Reason for disagreement: I apologize if I was unclear in the description of the issue. To reiterate, I believe there is a better way to express the loop condition such that it is clearer to the reader.
Instead of merely stating it as numOfTasks
, you could use until max numOfTasks reached
as an example.
Attached an example provided in the CS2113 Textbook:
Loop condition not properly stated in the Next Component's Sequence Diagram