nus-cs2103-AY2324S1 / pe-dev-response

0 stars 0 forks source link

Unable to choose which appointment to unmark #5970

Open nus-se-script opened 1 year ago

nus-se-script commented 1 year ago

image.png

There is no way for the user to see or be sure they are unmarking the correct appointment, or to unmark a specific appointment without affecting others. If a user wants to unmark the previous appointment without affecting the most recent, they would have to manually reenter everything


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

Jweewee commented 1 year ago

Team's Response

Hi, since our Appendix: Planned Enhancements plans to implement a Unmark Appointment recovers appointment details feature, we do not feel that even having this feature to unmark specific appointments is needed that much as of now.

Our product's main focus is on being an addressbook for insurance agents and not to manage appointments. It is not meant as a holistic tool that is able to also keep track of individual appointments of customers in detail. Hence, the marking and unmarking of appointments is only currently meant in this iteration to keep track of one appointment in the present/future, they are not meant as a holistic tool to keep track of the history of individual appointments. The commands only 1) Delete/Recover the current appointment, 2) Update the counter.

Simplicity and Focus: Keeping the marking and unmarking functionality simple and focused on the present and future appointments aligns with the application's primary purpose of being an address book that has a simple way to keep track of customers' appointments, avoiding unnecessary complexity by being a dedicated appointment tracker. Hence, it only keeps track of one appointment concurrently with no detailed history of past appointments to be fuss-free, and a simple completed counter that can be manually updated if there are inaccuracies with the number.

Resource Allocation: Resources (time, development effort, etc.) are better spent on enhancing core features that are more critical to the overall user experience or addressing higher-priority user stories as compared to implenting an Unmark specific appointments feature which would necessitate the overhaul of our appointment system and UX design to be able to handle multiple appointments for each customer.

Design Considerations and Behaviour: Even if the user were able to unmark a specific appointment, such as in the command Unmarkappt 1(customer) 3(appt), where the 3rd appointment of the customer has been unmarked, causing the counter to decrement by 1, it would not have significant value since the 3rd appointment's details would not be able to recovered, and if it were to be recovered under our Appendix: Planned Enhancements, we would not be able to hold multiple appointments for a customer or an appointment in the past. Implementing Unmarkappt 1 3 would not help our user significantly as there is a workaround: the user can delete his current appointment, decrement the counter using unmark, and add the current appointment back again to achieve the same functionality.

In conclusion, this can be a valid feature, but as of now, it does not seamlessly fit our product's image of simplicity and focus and it is troublesome to implement, requiring the re-design of the appointment feature and further defining of the appointment feature's restrictions and boundaries. Most importantly, it would require whole new functionalities being added to our appointment tracker if we want to implement this, making its implementation non-trivial. Hence, we are not sure if we want to implement this, much less in this iteration, especially when there is a method to achieve the same functionality as reasoned about in Design Considerations and Behaviour.

Duplicate status (if any):

--