Open sc-arecrow opened 3 years ago
There's no requirement stated in the module website that we need to list out every single use case.
In addition, we wrote about delete exercise in the instructions for manual testing.
Team chose [response.NotInScope
]
Reason for disagreement: It is stated in the CS2103 textbook that
Use cases capture the functional requirements of a system
hence the failure to reflect said features in your use cases implies the failure to capture these functional requirements of FixMyAbs.
Team chose [severity.VeryLow
]
Originally [severity.Medium
]
Reason for disagreement: Given the advantages of documenting system requirements as use cases, such as
- Identifying all possible extensions encourages us to consider all situations that a software product might face during its operation
- Separating typical scenarios from special cases encourages us to optimize the typical scenarios
a VeryLow
severity, which is stated on the CS2103 website as
severity.VeryLow
: A flaw that is purely cosmetic and does not affect usage e.g., a typo/spacing/layout/color/font issues in the docs or the UI that doesn't affect usage
does not seem to reflect the true severity of this bug.
Missing use cases seem far more severe than purely cosmetic bugs, and missing use cases will definitely affect future developers that work on or add on to the functional requirements that were supposed to be covered by those use cases.
The DG is missing use cases for deleting exercise and clearing data