soc-se-bot
commented
1 year ago [IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]
Team's Response
Firstly, it is not very clear what "broad definitions of the requirement" has not been achieved.
Consider the case where your group of friends spent $30 (pre-GST and Service Charge) on a group buy that is meant to split equally. With PayMeLah, you can split this debt in one command splitdebt 1 2 3 m/30++ d/arbitrary description.
On a GUI interface, you will have to click at least 3 buttons for the 3 friends, 1-2 ticks for checking GST and service charge, click the box to type 30 for the money amount, click the box to type the description, and click a button to split debt. We truly believe it is faster with our implementation.
This is testable against GUI competitors such as Splitwise.
More context on this NFR: This was adapted from 2103 tP constraints.
"most" is used here as per its base definition, i.e. more than 50%
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
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.How will this be tested? Is there a GUI equivalent that can be compared against? What percentage of tasks will be needed to be considered as most of the tasks?
Moreover, if we take a broad definition of the requirement, I would argue that this NFR has not been achieved.