Sequence diagram

There should be a colon : before each class name on the sequence diagram.

Screenshot

FAQ is not helpful

Outdated DG

Under manual testing, it shows that can delete the user by its index. Not mentioned in UG nor the actual program itself.

Screenshot

Sequence diagram

The optional break is not following the UML standard

Screenshot

List command does not show patient's appointment

The behavior of list command is different from the User Guide. It says that list is used to view patient's appointment while the app shows the list of patients instead.

Steps to recreate

1. Invoke list command

Expected

(According to UG) view patient's appointment

Actual

Prints the list of patients

Screenshot

User stories

It says that the admin wants to retrieve the patient's details to schedule the appointment. But, both retrieve and book requires the admin to know the NRIC (and only NRIC is required) beforehand. Thus, the retrieve serves nothing to help the admin to schedule an appointment.

Program crashes when user modify the save data externally

The program does not handle the case where the save data saved by the user is in the wrong format. The user may accidentally type 2020-13-10 when trying to change the month to 12 (December), causing the app to crash.

Steps to recreate the bug

1. Add a patient
2. Exit the program
3. Edit the data file such that the date is in the wrong format
4. Restart the app

Expected

The program will skip the faulty data when parsing

Actual

Complete class diagram

The class diagram is too complicated, the size is too small to be seen without magnification.

Screenshot

No expected output for all commands

There is no screenshot on the expected output of the commands, making it impossible to tell whether the application is working correctly or not

Screenshot

List command does not show patient's appointment

In real life scenario, it is hard to see how this app can benefit the user if they can only see the date of their appointments but not the doctors.

Steps to recreate

1. invoke appointments

Expected

Prints both the date and the doctor (similar to editappt)

Actual

Only prints the date

Screenshot

Faulty NRIC data is accepted if the save data is edited manually

An expert user may want to edit the data directly from the save file instead of using the program. In this case, if the user made a typo, they will not be able to access that particular user again because when the user tries to edit/assign/anything, as the program does not accept invalid NRIC.

Steps to recreate

1. Add a user to the database
2. Exit the program
3. Edit the save file manually
4. Reopen the application
5. Try to edit/book an appointment

Expected

The faulty data should be skipped during parsing and the user should be notified that there is a faulty data

Actual

Duplicate appointment dates accepted

Theapplication shows a duplicate in the dates when 2 same dates are created

Steps to recreate

1. create 2020-01-01
2. create 2020-01-01
3. editappt NRIC

Expected

Duplicate dates should not be listed as this application does not specify the time

Actual

Duplicate dates are listed

Screenshot

Appointment numbering

The list should start form 1 instead of 2

Steps to recreate

1. Edit appointment
2. Change the date
3. List the appointment

Expected

List starts from 1

Actual

List starts from 2

Screenshot