nus-pe-script
commented
1 week ago Team's Response
Using underscores instead of spaces is a common convention, and is consistent within the subject list. Even if the user were to use space at first, the error will inform them that an underscore should be used instead, correcting them and ensuring the convenience of using the app.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** I believe that it should be severity.Medium. According to the course website, "A flaw that causes occasional inconvenience to some users, but they can continue to use the product" will get severity.Medium. While underscores might be a convention in programming or certain technical contexts, they might not be intuitive and user-friendly for general app users (tuition teachers). In my opinion, most people naturally type using spaces, so requiring underscores in the subject title could create unnecessary inconveniences. Situations I faced: - While testing the application, it was quite common for me to miss out the underscore, using a space instead, needing me to go back and edit it, which is quite inconvenient. And I believe that this finding could be generalise to the general target audience. - While the error message does provide guidance, relying on it might not be ideal. If the subject the user typed is at the end of a long error message, they will need to scroll through the long message just to realise that the issue was a missing underscore. --- For reference, this is the potential error message I can get "Subjects should be in list: [MATH, A_MATH, E_MATH, SCIENCE, PHYSICS, CHEMISTRY, BIOLOGY, COMBINED_SCIENCE, ACCOUNTING, LITERATURE, HISTORY, GEOGRAPHY, SOCIAL_STUDIES, MUSIC, ART, ENGLISH, CHINESE, HIGHER_CHINESE, MALAY, HIGHER_MALAY, TAMIL, HIGHER_TAMIL, HINDI]". Scrolling through this long message just to find "HIGHER_TAMIL" and realise the missing underscore caused the error can lead to frustration. Hence, I feel that these situations could result in avoidable inconveniences and disruptions for the users, justifying a severity.Medium.
Currently, the subject names are good and specific. But with the use of underscores, it might hinder the convenience and efficiency of the app as it might not be intuitive for users to include them when they are inputting the command.