Deletion Of A Student Is Allowed Despite Outstanding Payment

[e1121208]

Description

As mentioned in the UG, the CLI serves to, and I quote,

efficiently manage payments and organize schedules.

However, allowing the deleting of a student with outstanding payment may cause the goal to fall short, or even regress. This is because once the student is deleted, data of the outstanding payment goes along with the student and the user may never be able to retrieve that amount back anymore.

---

Additional Information

John Doe, owing, $3000,

can be deleted.

---

Suggested Improvement

Possibly, run checks with the owe attribute of a student before allowing the deletion or throw a delete confirmation alert to remind the user of potentially deleting a student with outstanding payment.

[nus-se-script]

Team's Response

Thank you for your response. We think this is a valid concern raised.

We feel that the severity of this is low, from the user's perspective.

For UGTeach, the UI displays the full information of the student, which includes the amount owed and paid.

For a typical scenario, when user chooses to delete a student's information, it is likely that he looked through the list of the student displayed and to locate the index to delete, and verify all the information matches the student that he wishes to delete.

Then by that scenario, it is likely that the user would have ensured that there is no outstanding amount owed by that student.

Items for the Tester to Verify

❓ Issue severity

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

• I disagree

Reason for disagreement: [replace this with your explanation]

---