nus-pe-bot
commented
2 years ago Team's Response
Caps letters require more key presses than non caps letters.
Furthermore, the mentioned NFR is relevant to every team project, as being typing-friendly is a constraint of the entire tP component. The AB3 project itself is billed by the teaching staff as satisfying this constraint, and it has case-sensitive commands. If changing AB3 commands to be case-insensitive were a requirement to meet this constraint, then every single team would have to implement this feature in their project. To require every team to implement this somewhat major feature and never mention it once would be a deliberate act of sabotage by the module teaching staff, which is counter-productive to their goals. Hence, we believe it reasonable to claim that the constraint has been met, and Trace2Gather is sufficiently typing-friendly.
QED.
This is a good suggestion, however, and will be considered for future versions beyond the scope of this module. Thank you.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: This is a good suggestion, however, and will be considered for future versions beyond the scope of this module. Thank you.
From the developer response, this should be classified under response.NotInScope instead.
Furthermore, there may be much more reasons for having Cap letters typed into the CLI (e.g. CapsLock is engaged).
There would be a much better optimisation for individuals who are typing, if the commands are made case insensitive instead. (Does not fulfil NFR requirement)