soc-pe-bot
commented
2 years ago Team's Response
Hello tester, thanks for testing our app! You mentioned that the list is not well-depicted because it is hard for users to navigate around. However, this list is actually categorized based on the most apparent feature of our app, which is the four main entities, as you can see in the screenshot you provided. Therefore, the first reason why we feel this will be easily navigatable for users is that with this categorization, the users can find the commands based on which class they want to operate on. Secondly, you mentioned that there are too many add, edit and delete commands. This is necessary because the 4 entities in our app have different attributes, and require different prefixes for their add, delete and edit commands. There is no simple way to combine them together without confusing the reader (imagine reading: add[customer]{dish}(driver) [a/CUSTOMERADDRESS]{n/DISHNAME}(p/DRIVERPHONE), it is definitely not feasible to combine or try to take shortcuts in depicting the commands). Moreover, the user guide is supposed to be comprehensive, which makes another reason why this cannot and should not be compressed further.
As a result, we propose rejecting this issue. Thanks!
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: [replace this with your reason]
I would reject the explanation because it scares me as a use to see so many similar actions being repeated at first glance ("Add", "Delete", "Edit", "List").
Command summary actions not well depicted, there are many add, edit and delete columns, it is very hard for user to navigate around without looking into the right column.