soc-pe-bot
commented
11 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.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: > 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.
I find this reasoning ambiguous. Yes, you would have to see a list of customers then choose from the list. My point is that the user does not need to filter the list before proceeding with the remaining steps. If the user does not have the list of customers (i.e, the list is empty), filtering the list will not help in any way.
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.
I disagree. Adding an unnecessary detail may make the Use Case confusing.
Sorry, but I am actually not very sure what you meant here, hence I did not provide any response to this.
I mean that if using the filtering function before proceeding to the remaining steps cause the index to be selected to change (e.g Originally Mr A was index 1, but after filtering by name Mr A was priority 2, and the index to be selected changes from 1 to 2), this would be a separate Use Case. The original one should be the one that does not involve any filtering.
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.