soc-se-bot
commented
16 hours ago Team's Response
This bug report contains multiple bugs. We have chosen the first bug ("The use cases seem to be lacking as there are only 3 use cases") as the other two are duplicate with other bug reports.
Only considering the first bug, we have downgraded the severity to severity.Low. The low number of use cases does not render the DG unusable and hence does not deserve a severity.High. Furthermore, we kept only 3 use cases as most other use cases (including the examples you gave) were deemed not important (according to the definition given by the course website attached below). The features themselves are already covered by the user stories, and their main success scenarios and extensions are simple enough so that it is very clear to future developers what and how to implement.
Items for the Tester to Verify
:question: Issue severity
Team chose [severity.Low]
Originally [severity.High]
- [x] I disagree
Reason for disagreement: If we are just taking the first bug, then I believe a severity.Medium is still minimally required (and what I would like to change to now) as other given use cases may not be as trivial as you expect. What is trivial are commands that are parameterless and only of a single form such as exit. For example, the search feature (and searchtag by extension) has multiple extensions (that may not be obvious) like
- Invalid syntax
- Empty parameter
- No matching keywords
- Multiple parameters
Issue The use cases seem to be lacking as there are only 3 use cases. Use case 3 is irrelevant to Service Track as there is no feature of reminder or dates. The use case states that System or Service Track is referenced but we mostly see AddressBook.
These are some use cases worth adding that are missing that are not as trivial:
Actual Result
Incorrect system type
Irrelevant Use Case