nus-pe-bot
commented
3 years ago Team's Response
To address the feature flaw concern: One student having multiple appointments is not in our scope for 2103 v1.4. This is something that we could add in future iterations. It is something that we considered, however due to workload and the complex nature of implementing a one-to-many entity relationship, and due to the fact that we are a 4-person team, this was left out of our scope.
We acknowledge that there is a lack of clarity in the UG for not stating this constraint explicitly, we therefore recategorised this as a documentation bug.
Items for the Tester to Verify
:question: Issue type
Team chose [type.DocumentationBug]
Originally [type.FeatureFlaw]
- [x] I disagree
Reason for disagreement: I disagree that it is a documentation bug since you did not mention this constraint in your UG (at the time of the PE).
Your team acknowledged in your DG that Covid-19 requires 2 doses, hence one would naturally conclude that the application can accept more than 1 appointment per person.
Hence, this is a feature flaw.
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.Low]
- [x] I disagree
Reason for disagreement: This constraint affects the efficient management of Covid-19 appointments quite significantly as we cannot verify whether the student has really been vaccinated unless each student has at least 2 appointments in the system.
Covid 19 vaccines require 2 jabs and thus more than 1 appointment on different dates. It would be more logical if the application allows more than 1 appointments for each student.