yucongkoo
commented
10 months ago Team's Response
Hi there, thanks for bring this issue up.
I believe use cases are supposed to describe the sequence of interaction between the user and the system, so I will be describing the sequence of actions that will be taken by the users.
From my point of view, as a user, when I want to update a tag of a customer, I will first have to see a list of customers, then choose from the list the customer I want to update. For instance, if the user does not have the list of customers, how does the user choose an index? Therefore, I think it is appropriate to include such a step in the use case.
Step 1 is unnecessary as user does not need to filter customers before editing.
As use cases are not used to describe how the application functions (uses cases should be gathered before actually implementing a feature), hence, I believe whether or not the users need to filter customers before editing does not matter here.
If indices change, it should be given as a different use case.
Sorry, but I am actually not very sure what you meant here, hence I did not provide any response to this.
Duplicate status (if any):
--
Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.
Step 1 is unnecessary as user does not need to filter customers before editing. If indices change, it should be given as a different use case.
[original: nus-cs2103-AY2324S1/pe-interim#5106] [original labels: severity.Low type.DocumentationBug]