soc-se-bot
commented
5 days ago Team's Response
Thank you for your report. You have pointed out that the logo has not changed and the app name is not the title of the app and we recognise where you are coming from. However, we would like to point out the following:
Firstly, the app title need not necessarily be the exact name of the app. For example, AddressBook Level 3 (AB3) application has the product name “AddressBook Level 3” but the title found in their app is “Address App”.
As such, what we perceive as the so-called title is not the exact app name, but a reasonable alternative name that refers to the app. In AB3, “Address App” seems to be it. AB3 is an address book (as in the English meaning of address book) and it is reasonable to us that the word “Address” is a short form for “address book”.
In our case, we note that our app data_coNdUctorS is an address book app. Thus, having the alternative name as “Address App” remains valid and does justice to what our app is, especially given that the essence of both AB3 and data_coNdUctorS are the same: managing contacts. Moreover, in the first sentence of our user guide in page 1, we specifically associate our app with an address book:
data_coNdUctorS is a desktop address book application…
In a similar vein, the app icon image can be used for our app data_coNdUctorS as the app icon shows an icon of the address book, which is in line with the nature of data_coNdUctorS. Was the icon image the brand logo of AB3? It didn’t occur to us that the icon image is the brand logo, it looks like a random icon indicating that this is an address book. Therefore, we did not feel there was a need to change the app title, and the app icon, as compared to other pressing features we had to achieve.
After receiving your report, perhaps it is important to distinguish our application from AB3 and we do acknowledge that. We have noted this report and will improve in the future. The current priority will still be implementing other pressing features rather than this rather cosmetic issue.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [x] I disagree
Reason for disagreement:
By the rubrics, (under the greyed part) this change takes few seconds to implement + neither of the bullepoints is satisfied. Furthermore, they only allowed to delay to future iterations, IF its less important that the work thats already done (working on this feature, in this case fixing the name of the app, which is zero here)
The answer you gave is an excuse for not changing the title of the app. No app in the world does not change their app title from a generic name to their app name because its the very first thing that pops in the user's mind when using the app. Your app is supposedly a product to be sold/pitched to target users and not having its name is quite a big deal, even if its cosmetic. I don't think "Whatsapp" names themselves "Message App", cause no one would know who they are if so. Similar vein of thought for the icon, although I can be reasonable and agree if only the icon was not changed.
"But AB3 also wrote Address App when its is supposed be AB3 actually"
The assumption here that AB3 is all correct, the reason AB3 wrote Address App because its just a template meant for students to use, its not pitching its product to a target audience (Professors have mentioned that AB3 not all correct). Your task in TP was to modify the app to be tailored to your users, you can't be giving them a template title.
Nevertheless, I still agree is a cosmetic issue, as you pointed out and willing to give a very low severity but its perfectly in scope and valid. Not in scope means its valid but not something you should be faulted for, which I disagree. It's part of your requirements of the TP.
Conclusion
Disagree with response of "NotInScope", Agree with very low severity.
The icon could be customised instead of using the original AB3 Icon. Additionally, the app title should be the name of the app.