Open SharlynLui opened 2 months ago
Thanks for the bug report!
This is probably due to the limitation of PlantUML, causing some self-invocation arrows to point to the start of activation bars and some to point elsewhere...
As the self-invocation arrows still point to the correct activation bars, we accept this bug as a DocumentationBug
of severity.VeryLow
as quoted from the textbook below:
Team chose [severity.VeryLow
]
Originally [severity.Low
]
Reason for disagreement: [replace this with your explanation]
The UML diagram for processSolutionCommand on page 8 has inconsistency with some arrows starting at the start of the activation bar and some not starting at the activation bar. For example, arrows for getSizez() and getQuestionSet() does not start at the start of the activation bar according to notation of UML diagrams but e.g. getTopicOrQuestionNum() is correct.