search

btaanish / pe

0 stars 0 forks source link

error message for date of appointment #9

Open btaanish opened 11 months ago

btaanish commented 11 months ago

image.png

While adding an appointment, if the receptionist adds a past date by mistake, especially a wrong year, the appointment can be added. This can lead to occasional inconveniences for the receptionist as a small typo here can lead to issues while looking to find out upcoming appointments

nus-se-bot commented 11 months ago

Team's Response

The UG or DG did not state we intended to allow receptionist to only add upcoming appointment. Hence this cannot be a functionality bug.

Tester can refer to the course website for the definition of a functionality bug.

Screenshot 2023-11-19 at 4.32.44 PM.png

The ability to add appointments in the past allows a clinic that just adopted MediConnect to migrate their past records into the system as there is currently no alternative method for data import other than entering the Appointments through the add_a command.

That being said the case that the tester pointed out is still valid but at most constitute a Feature Flaw, the only way around it is to show a warning message after the user adds a past appointment.

We will accept this as not in scope as well since this lack of the suggested feature does not hinder or limit users to accomplish add appointment task.

We propose the severity to be Low as the user is fully aware of the appointment date added with the result box reading back the input date, thus this lack of the suggested feature does not inconvenient the user at all.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: > We will accept this as not in scope as well since this lack of the suggested feature does not hinder or limit users to accomplish add appointment task.

If the target user - clinical receptionisits - inadvertently make a typo for the date, adding a year that is probably already passed, the system neither raises an error nor informs the user that an already passed date is added. The impacts the users - clinical receptionists - both from keeping track of the appointments made and also referring to upcoming appointments(primary purpose of the whole app), very well hindering their usage of the app to access the basic functionality of keeping track of the saved appointments. Hence, this, the ability to add apointments and referring to the upcoming appointments is very well in scope for the project.

## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [x] I disagree **Reason for disagreement:** >there is currently no alternative method for data import As claimed in the team's response, the lack of a command to load previously added appointments or migrate existing appointments into the current system may very well be termed a feature flaw. However, the inability of the system to warn the user if an erroneous entry for an already passed appointment is made, is most definitely a feature-flaw. This is because making a typo while entering a date is a `legitimate user behavior`, and the current command structure fails to accommodate this.
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** The system's inability to alert the user when an appointment for a past date is added will, most definitely, cause `occasional inconveniences` in keeping track of appointments. This is because there is no way for them to realize if there is an upcoming appointment, leading to missed appointments for both the user and the doctor. >The ability to add appointments in the past allows a clinic that just adopted MediConnect to migrate their past records into the system as there is currently no alternative method for data import other than entering the Appointments through the add_a command. The use of the same command to add a previously past appointment constitutes a functionality bug in itself, as using the same command for two completely different functionalities can cause occasional inconveniences to the user. This adds to the confusion and recurrence of the same kind of mistakes. Hence, these issues certainly impact the user's utilization of the system to make appointments and undoubtedly cause `occasional inconveniences` to the user.