nus-pe-bot
commented
1 year ago Team's Response
We chose to define Guest here as we want to specify its meaning in the context of our DG and compare it with the meaning of Number of Guests. The meaning of a typical guest should be obvious for any reader.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Precisely because the team has used the term guest again when defining number of guests, they have to provide a clear definition of what is guest right from the start, instead of explaining the term using recursive definition which confuses more than explains.
Defining guests as "guest who booked the hotel room" would confuse the stakeholders to think as to what again is this guest who booked the hotel room?
In this case, it would have been better off if they don't even put this term in glossary. Since they have already put it there, they should define guests clearly such as "customers who booked the hotel room".
Glossary is to ensure common understanding of all stakeholders, even if the team's intention was merely to "specify its meaning in the context of our DG", they should also state clearly who exactly is this guests, since they have already decided to put it in glossary. This is to prevent any confusion amongst the stakeholders, which defeats the very purpose of them putting that term up on glossary.
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.Low]
- [x] I disagree
Reason for disagreement: This is not a cosmetic issue and indeed creates confusion and inconvenience to the stakeholders when they read the glossary.
"Guest" is being defined here (under developer guide), it is a bit weird to use the same word again.