Open nus-se-script opened 9 months ago
While the current design limits the number of emergency contacts to two, we understand that individual preferences and circumstances may vary. We acknowledge the importance of personal choice in such matters. However, it's crucial to strike a balance between user preference and the system's intended functionality.
The decision to restrict emergency contacts to two is rooted in the goal of streamlining the emergency response process. Nevertheless, we recognise that users may have unique situations where additional contacts could be beneficial. To address this, we are actively exploring ways to enhance the feature, possibly by allowing users to choose their preferred number of emergency contacts within reasonable limits. However, at this stage, we would not label this as a feature flaw but notinscope.
Even though it is notinscope, this should not be defined as medium severity as well. The reason for this is my team feels that NUSCoursemates is meant for and to be used by SoC students, so it would be rare for students to have more than 2 emergency contacts other than their friends. Moreover, you would not normally add NUS Campus Security, Family Member 1 and Family Member 2 into a peer-keeping contact book such as NUSCoursemates.
Thank you for the great suggestion though! We would definitely consider doing it in a future version of NUSCoursemates!
--
It might be considered an overzealous form of validation by mandating up to 2 emergencies. Consider a simple case where one might have the following emergency contact in NUS: "NUS Campus Security, Family Member 1, Family Member 2, Very Close Friend".
In the first place, perhaps let users have the freedom to choose.
[original: nus-cs2103-AY2324S1/pe-interim#2774] [original labels: type.FeatureFlaw severity.Medium]