Unnecessary repeat of use cases

[alientian]

The content of these two use cases are similar and they are implemented as a single command list. Should have combined them or simply indicate that uc4 is simlilar to uc3.

[nus-pe-script]

Team's Response

Hello there, thank you for raising this issue. However, we will be rejecting this issue as they are separate use cases just that they can be accomplished with the same command. One for listing events, and one for listing members. For instance, after using the findEvent command, we will only want to list all the events as the member list was unaltered.

Thank you.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: > For instance, after using the findEvent command, we will only want to list all the events as the member list was unaltered.

In the case that both list were altered, for example, after using the viewEvent command, the app is unable to allow them to list either all the members or all the events only.

The two different use cases may confuse readers that they can list members and events separately. The listing of members and events is inseparable for the functionality of the list feature and having two use cases foes not document this functionality well, thus i feel that it is unnecessary and should be combined.

---