yhtMinceraft1010X / pe

0 stars 0 forks source link

Unable to add additional appointments #9

Open yhtMinceraft1010X opened 3 years ago

yhtMinceraft1010X commented 3 years ago

Application: image.png

User Guide: image.png

I think it would be helpful to have an ability to add multiple appointments for the same student, given that both vaccination appointments can be made in advance (since the other shot is just 3-4 weeks apart) and there could also be appointments for covid testing and checkups (which was mentioned in the user guide).

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.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Cant add a recurring patient to the appointment list (but should be since covid 19 vaccines require 2 jabs)

image.png

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.


[original: nus-cs2103-AY2021S2/pe-interim#1349] [original labels: severity.Low type.FeatureFlaw]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

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 duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: [replace this with your explanation]


:question: Issue type

Team chose [type.DocumentationBug] Originally [type.FeatureFlaw]

Reason for disagreement: [replace this with your explanation]


:question: Issue severity

Team chose [severity.VeryLow] Originally [severity.Medium]

Reason for disagreement: Personally, I do not think that the severity should be considered as VeryLow given that the bug, even if reclassified as a documentation error, still causes a misunderstanding in the way the main software should be used.

Perhaps a Low rating would be a good compromise given that its still not too difficult to get around as a user.