nus-pe-bot
commented
2 years ago Team's Response
Once the hotel manager keys in the satisfaction, that satisfaction has already been finalized with the customer. Therefore, there is no need to edit or delete that satisfaction, as doing so could unfairly bump up the hotel's ratings. As this bug only happens rarely and is not likely to majorly inconvenience a hotel manager under normal circumstances, the severity of the bug should be low.
Items for the Tester to Verify
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [x] I disagree
Reason for disagreement: I think not being to update or delete satisfaction can be a major inconvenience in cases of a typo. In a real life scenario, the hotel manager might have to key in hundreds of satisfaction, chances are the hotel manager might make some mistakes occassionally. Considering that one typo (which might not be that uncommon in a real-life scenario) will render the satisfaction feature useless as there is no way to correct the mistake, and touching the data file is forbidden as per UG, that one mistake can have a huge impact on the usability of the app overall.
Consider another scenario where a customer returns for another visit. He has a great time in his first visit, giving a satisfaction of 5. On his second visit, he had a terrible experience, but the hotel manager is unable to change the satisfaction as the customer name is the same and there cannot have duplicate names in the record. This scenario is also not uncommon as there are usually repeat customers in a real life scenario. The inability to update the satisfaction will also render the satisfaction feature useless as it does not provide the hotel manager a correct representation of the satisfaction level.
Deleting or editing to test seems impossible since the user guide specifies that we should not touch the files directly.