nus-se-bot
commented
3 years ago Team's Response
Firstly, we would like to highlight that these steps have similarly been included in the use case for deleting a person in the AB3 DG.
Secondly, referring to this example given in the textbook, we have not described UI details in steps 1-4 of the use cases.
Thirdly, these steps are necessary to list all workers and shifts, in order to include scenarios where the lists have been filtered and the user's desired worker/shift to manipulate are not currently listed on the screen.
Lastly, the severity has been lowered to low as these steps, even if deemed unnecessary, are valid and correct, and will not cause any confusion to the reader, maybe only inconveniencing the reader slightly to read a few more lines.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: This is similar to the issue I post regarding reassign command in UG.
The problem is that it makes the use case look long and repeated. Same steps repeat for UC 15 to UC 17. Is it necessary if we remove those lines? If we take UC15 as an example, the aim is to delete a person. We can start from step 3 directly. And step 1-2 is about another thing which is list command. If we support this kind of explantion, we can start from "how to launch app" to delete a person. Also, it is not only for one use case. Same parts (step1-2) repeat for UC15 to UC 17. How can three use cases need same steps to start? Can these repeated steps written as a new user case?
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
From UC-015 to UC-017, it is unnecessary to describe UI and user operation in step 1-4 which is not important and repeated. Those four steps are not special for these four use cases. It can be fit for any other operations.