nus-pe-bot
commented
2 years ago Team's Response
Our initial design did accept the Day of Week as Monday to Sunday. However, due to the many different ways in which to abbreviate them (TUESDAY/TUE/TUES), we decided that to not only standardize the command, but to also make it shorter for users, we would allow users to input the days of the week from 1 to 7.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: "we decided that to not only standardize the command". In this case, standardizing the commands to be integers instead of the actual values instead of supporting the very small ways of abbreviating days seems more of a decision made for simplicity of implementation. It is extremely unintuitive for the user to be counting the days as integers starting from a day that was chosen by the team. This causes any user to spend some time in calculating the days before using several of the commands. This is the same reason why dates are not integers for standardization as well.
Besides, there is only a finite number of abbreviations for the days which are well understood. These abbreviations supported can also be explicit stated in the User Guide to prevent any confusions.
"but to also make it shorter for users". I think in this case, any benefits gained from the shortening of the arguments is countered by the difficulty in calculating the value itself.
Should instead accept the actual days as it is difficult for the user to count days starting from monday for the commands.