nus-pe-bot
commented
2 years ago Team's Response
We feel that putting in images to show how the Classes tab is not necessary, as it does not value add information, and we do not want to clutter the UG. When the user opens our app, he/she can already see the 3 tabs. Even if this is accepted, we feel that this should only be very low.
A flaw that is unlikely to affect normal operations of the product. Appears only in very rare situations and causes a minor inconvenience only. - Definition of Low.
We feel that this does not affect normal operations of the product.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: This issue arises from not enough use of visuals, especially in a case where they are important (introducing a new tab with a different layout):
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.Low]
- [x] I disagree
Reason for disagreement: "A flaw that is unlikely to affect normal operations of the product. Appears only in very rare situations and causes a minor inconvenience only. - Definition of Low".
Based on the description you provided, the severity falls under severity.Low, not severity.VeryLow.
Furthermore, the inclusion of this diagram is important since the user is not familiar with the classes tab, which is different from the students tab since it consists of both classes and students in different panes.
The user has no visual reference of how the Classes tab looks or how class commands affect the display.