Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.
In this particular class diagram, each arrow is dashed, while in the notes it is mentioned that dashed lines are use for interfaces/abstract classes. There is also a dashed arrow where XYZ command implements an abstract command class. This may confuse the reader as he or she may infer that all of these classes are abstract or are interfaces, despite the different arrowheads.
The dashed line with arrow head represents dependency between classes. This is true for the relationship between these classes and you can confirm this through our source code.
Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.
In this particular class diagram, each arrow is dashed, while in the notes it is mentioned that dashed lines are use for interfaces/abstract classes. There is also a dashed arrow where XYZ command implements an abstract command class. This may confuse the reader as he or she may infer that all of these classes are abstract or are interfaces, despite the different arrowheads.
[original: nus-cs2103-AY2223S1/pe-interim#4754] [original labels: type.DocumentationBug severity.Low]