nus-pe-bot
commented
3 years ago Team's Response
Problem raised is unclear.
Assuming that the issue is directed at the lack of details in the Use Case steps, from the Textbook:
A step gives the intention of the actor (not the mechanics). That means UI details are usually omitted. The idea is to leave as much flexibility to the UI designer as possible. That is, the use case specification should be as general as possible (less specific) about the UI.
In addition, implementation details are to be avoided as well. Therefore, what is shown in the Use Case is what is supposed to be shown, and there is no issue.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.Medium]
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
Most use cases provided in the DG simply outline the user input and the final outcome produced by the system in the MSS segment (see example in screenshot). It does not describe the specific steps and sequence of actions that are taken by the system in order to produce the final outcome result.