Instance of addressbook still present in return message

[jinhanjinhan]

Using addressbook in the return message can be quite confusing for users, and leave the users wondering, "What is addressbook?" You should try to avoid such confusion among users, and a quick way is just to change all such instances of addressbook to EduTuTu.

[nus-se-script]

Team's Response

Thanks for the report. We think that this does not affect user experience and can change it in the future. However, it is out of scope for now.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement:

Hi, I disagree that this should be considered as notInScope. As stated in the screenshot above, an issue should be considered notInScope if only the supposedly better implementation takes more time such that it reduces the effort available to spend on more important tasks. However, I don't think rectifying this will take up much more time since you are basically changes the messages that uses addressbook to use EduTuTu instead. Moreover, neither did your UG specify that it is coming in future iterations, nor the software fails gracefully since the error message with addressbook will always be shown if the user key in something wrong.

Regarding the part that you mentioned about "this does not affect user experience ...", I have to disagree with you on this, because I think it does. Considering the perspective of an end user who just started using EduTuTu and have no prior knowledge of AB3, if I accidentally type in something wrong, it will show me errors like "This person already exists in the addressbook.", which will leave me confused about what an "addressbook" is.

While you might argue that only one word difference might not really affect user experience much, but there are actually other instances that EduTuTu will leave users "confused". For instance, using person instead of student in your error message, as well as using tags like friends, colleagues as default tags when users just initalised EduTuTu for the first time, as seen from the screenshot below, when the more appropriate tags should be scholar or maybe Needs additional help and so on.

So, in fact, it is an amalgamation of all these seemingly minor issues that will actually hurt the credibility of the app and shun users away from using the app. Hence, I think your argument that this does not affect user experience is invalid since users will always be seeing these errors and it also gives users the impression that the application is not really credible and not tested thoroughly before launching.

---