nus-pe-bot
commented
1 year ago Team's Response
When taken into consideration with the full target user profile and value proposition, our definition of "bulk purchase" should be quite clear. Furthermore, the DG is meant to be used in conjunction with the UG, where our target users are stated very clearly on the first page.
Even if we assume the definition of "bulk purchase" to be the purchase of large quantities of items for events, businesses or organisations, our target user profile is accurate, as a student who makes many bulk purchases, and also has a need to track his debtors, is indeed someone who organizes many group buys.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: > When taken into consideration with the full target user profile and value proposition, our definition of "bulk purchase" should be quite clear. Furthermore, the DG is meant to be used in conjunction with the UG, where our target users are stated very clearly on the first page.
In the context of both the UG and the DG, it is evident that the developer team intends for the app to target university students who want an efficient way to split up their everyday expenses among groups of 3 - 5 people. The phrase "bulk purchases" is therefore most accurate, especially in the context of the numerous command examples given in the UG (e.g. splitdebt 0 2 5 d/KFC chicken bucket n/30+ date 2022-10-12). When writing a value proposition, the most immediate and relevant value proposition (i.e., everyday group expenses) should be identified. Most people's understanding of bulk purchases will follow the screenshot below.
Even if we assume the definition of "bulk purchase" to be the purchase of large quantities of items for events, businesses or organisations, our target user profile is accurate, as a student who makes many bulk purchases, and also has a need to track his debtors, is indeed someone who organizes many group buys.
If we follow the definition of "bulk purchase", then the app may not be optimised for said value proposition as it will typically involve adding many more debtors. For example the average group buy size is 40 to 60. In the CLI app, there is no efficient way to split debt among 50 people without specifying each person's index.
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.Medium]
- [x] I disagree
Reason for disagreement: severity.VeryLow is purely for cosmetic reasons.
Accept as severity.Low since the geist of the value proposition that the developer team wants to drive across is understandable through the examples given in the commands.
In the context of the application and the examples given, it seems that the application is best suited for tracking every day, group expenses like dining with friends or sharing a taxi.
The use of the phrase "bulk purchase" is rather misleading because it usually refers to the purchase of large quantities of items for events, businesses or organisations (i.e., more logistically intensive, less for leisure).