list - feature flaw

[sylviaokt]

The list and elist command has too many different combinations of parameters, and maybe that is a result of combining list and sorting under one command. That might be prove to be confusing for users to use, hence it would not be efficient. Thus, this feature is not optimized for target users who just want to list or search for a contact or event.

[nus-pe-bot]

Team's Response

• Rejected, this is an intentional design decision (see #102), as a balance between excessive number of commands and overloading features.
  • For experienced users, this proves much more beneficial: (1) less commands to remember, (2) fits cohesively into the app (e.g. list allows you to find contacts / events without modifying them)
• Being thorough in detailing commands is not uncommon (for a more familiar example within the context of this module, see git branch).
• Ease of use is encouraged through the use of optional parameters, so user does not need to type every parameter listed.
  • Examples are additionally provided to showcase potential uses.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: The group mentioned that this is more beneficial as there are less commands to remember. I agree with that point, however, this requires users to remember more parameters to compensate for the less number of commands. I do not see how this is more beneficial. As they are all under list and elist, it is less intuitive for the users. In addition, I agree that ease of use is encouraged through the use of optional parameters. However, this does not change the fact that users have to remember all the possible parameters if they want to make full use of the command. In this case, when user wants to search for a contact, using a more intuitive command such as find would be much better than using list and trying to remember the correct parameters for it.

---