nus-pe-bot
commented
3 years ago Team's Response
As clearly mentioned in our DG, each of these diagram only shows the connection to a specific class rather than all the connection to every single class. This is done to prevent the diagram from being too complicated. Furthermore, there is no mistake in the format being used for these diagrams as this is a architectural diagram that exist in the "Design" section to show how the different components are connected to each other. We were also careful to not call them class diagrams.
Tagging this 'bug' as a HIGH serverity is clearly overstating the issue as 1) There is no specific format for architectural diagram 2) It is clearly stated in the DG the reasons for going with such a layout.
Due to the given reasons above, the team will be rejecting the bug.
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.VeryLow]
Originally [severity.High]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
The diagram above shows that Global connects to other classes such as Apps only through the PlanNUS main class while the bottom diagram shows that Global are connected to those classes Directly, which is contractory and confusing.