TrungBui32 / pe

0 stars 0 forks source link

Budget update command #2

Open TrungBui32 opened 1 week ago

TrungBui32 commented 1 week ago

The budget can be updated by the command "budget". This means that if user type wrong month, the previous is not recorded. The team should add update command instead.

image.png

nus-se-script commented 1 week ago

Team's Response

Thank you for pointing out the "bug". Unfortunately, I don't really see the issue with this for the following reason:

  1. budget does update the budget. So it's working as intended
  2. If i set the budget for the month again, then it is an update. It doesn't make sense to have 2 budgets in a month, hence there is no need for 2 values in this case.
  3. If you wanted a feature in which i record all the "positive" gains and "negative" cost, then its a different feature as compared to budget. budget is how much the user can spend in the month, if you wanted something like an income, then it would be out of scope of v2.1 since fundamentally, it is a different functionality as compared to what a budget is.
  4. If you are scared of the user typing in wrongly, I think then its not right to blame the program for the flaw. However, if this is what you wanted to point out, I can agree to the fact that our application could have an additional prompt to ask if he user wants to override the existing data. Then again, this would be out of the current scope of v2.1 since I would require a setting the enables/disables this function. If not, if we brute force this function, then another user would just say that the additional prompts are annoying

Initially, our team tagged this as an IssueUnclear tag. However, based on the tester's last line "The team should add update command instead", we decided to go with the thinking that the tester wanted this to be a feature implemented instead of a manual override of budget data. Hence, the decision by the dev team is to put this flaw as a "not in scope", based on points 2,3 and 4.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: [replace this with your explanation]