nus-se-bot
commented
1 week ago Team's Response
Dear Tester, we would like to reject this issue.
There is no mention anywhere in the project requirements that states that we must include an object diagram. It asks for a variety of diagrams and we do so via the inclusion of the architecture diagram, class diagrams and sequence diagrams. Hence the lack of an object diagram should not be an issue.
We strongly believe that the wide assortment of diagrams we have included offer a good mix between being comprehensive while not being repetitive or redundant. Particularly the sequence diagrams, which already clearly and in detail elaborate on how key systems in our code work (such as parsing user inputs, and saving/loading data from the save files). Thus, we strongly object to your claim that our analysis and evaluation of the classes are "less comprehensive".
Furthermore, we would like to seek clarification on how this would even constitute a DocumentationBug. Is the user or tester greatly misled or lied to or left confused by our current DG, due to a lack of object diagrams? We don't think so, hence would like to reject your issue.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
Your DG does not seem to have any object diagram, which makes the analysis and evaluation of the classes less comprehensive.