Details:
The class diagram in page 16 of the DG contains too many unnecessary methods in it, making the diagram hard to follow and understand. You could maybe consider omitting much of the methods from classes such as Ui and SpendingList, as their inclusion hinders the reader more than helps them in understanding the class diagram.
The team has discussed and decided to reject the bug. The following are the justifications:
We have already omitted many methods and attributes in these classes. We feel that the remaining ones are significant and should be shown to a developer who is reading the guide to avoid confusion.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
[ ] I disagree
Reason for disagreement: [replace this with your explanation]
Details: The class diagram in page 16 of the DG contains too many unnecessary methods in it, making the diagram hard to follow and understand. You could maybe consider omitting much of the methods from classes such as Ui and SpendingList, as their inclusion hinders the reader more than helps them in understanding the class diagram.
Screenshot: