soc-pe-bot
commented
1 week ago Team's Response
No details provided by team.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Untestable and not well-defined NFRs
A user with above average typing speed for regular English text (i.e. not code, not system admin commands) should be able to accomplish most of the tasks faster using commands than using the mouse.is not clear as it does not indicate the quantifiable word per minute metrics for 'average typing speed' and difficult to verify what are called 'most of the tasks faster', i.e. 80% of the commands, rendering this NFR not testable.
[original: nus-cs2103-AY2425S1/pe-interim#170] [original labels: severity.Medium type.DocumentationBug]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
Thank you for the suggestion!
Above average typing speed is easily understood by future developers, and such values can be retrieved from other sources should they really want an exact number on it.
According to the course website, we believe the NFR fall in the Quality Requirement category.
As seen in the example the website gives, it has a similar level of "unquantifiability" as what we have. It states the system should be usable by a novice who has never carried out an online purchase.
How "fast" can one complete a task using our command. These are mere indicators, and in real scenarios, we can always find these user groups to test our application and check if they feel the NFRs are met.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
- [x] I disagree
Reason for disagreement: According to the course website, bugs only constitute as duplicates if they are the exact same bug, OR they cannot be fixed independently.
In this case, the two bug reports are not the exact same bug, since they cited different NFRs as the issue (the 3rd and the 5th respectively). They also touch on different types of NFR bug, one is regarding "not well-defined NFR" while the other is more about "not reasonably achievable NFR".
I think these two bug could also be fixed independently, since they are 2 independent lines in a document.
Extract:
## :question: Issue response Team chose [`response.Rejected`] - [x] I disagree **Reason for disagreement:** In the developer's response, it does not seems to have addressed the specific issue this bug report brought up.
## :question: Issue severity Team chose [`severity.Medium`] Originally [`severity.Low`] - [x] I disagree **Reason for disagreement:** This line of NFR would not cause that much harm to the user, since even if the app is terminated via other means, it would not cause any lost of data. Furthermore, I think this line of NFR rarely causes users any inconvenience. My stance was that this is strictly a false NFR (as of testing) and I do not think it is reasonably achievable, therefore a DG bug.
Greetings,
Elaboration: Particularly, I am referring to the fifth NFR. I presume the exit command refers here is the
exitcommand. In windows OS, when use the hotkey Alt+F4, I managed to terminate the app without using theexitcommand. Perhaps this NFR is not reasonably achievable as there are too many things to consider.