Bug in use cases 2 and 6 - incorrect use of word return

[yucongkoo]

In use case 2 and 6, the word return is used where I believe it should have been displays or shows. return sounds like an internal behaviour rather than external behaviour.

[nus-pe-script]

Team's Response

return just states that insurahub will show the new client without the tag that the user wants removed, which is similar to displays, hence i believe that we can use returns in this case.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: Quoting the tester's response:

insurahub will show the new client without the tag that the user wants removed, which is similar to displays

Hence, I believe my assumption on the meaning of return is correct.

However, I could not agree with the testers that return has the same meaning as show or display, what is the system returning? It is very vague. Besides, from my understanding, it is really hard to actually link the word return to the meaning of showing/displaying something. I was able to guess the meaning that the testers intended by actually using the product and observing the behaviour. However, this is not a valid reason for the use case to be vague, as use cases are supposed to be a requirement specification(before the product is being implemented), and it is not possible to guess the meaning by observing the product behaviour.

Here is an example of the use case(that I did not have time to include during the bug reporting phase):

---