lwlshawn / pe Goto Github PK

In the user guide, the "done" command appears to be missing from the command summary section.

Similar to the other report, the visit command does not appear to allow parameters to be given in any order.

The documentation for delete states that it will only delete the corresponding elderly's next visit, but for elderly with recurring visits, it will delete ALL the visits and not just the "next visit". I felt that there was a significant difference between the two, hence the high severity.

Find command is stated to only display elderly whose name contain any of the given keywords above, but below in the blue box, the documentation suggests that the command searches other fields, like language

Despite being documented, perhaps this second listed behavior where sort v/lv/ becomes sort v/ should be avoided altogether? When this occurs in use, I think its most likely due to a user error, and should probably be flagged for their notice. I think its very unlikely that the user keys two prefixes v/lv/ and intended for only v/ to be interpreted.

When using edit to remove the lastvisit field, the application warns the user that a lastvisit date should be in the future. This happens when editing an elderly whose current visit date is wrong. Perhaps the warning should be kept to what happened in the current command?

I thought this might throw a user off slightly, as you are unable to edit the next visit field using the edit command, and are receiving an error unrelated to the command you have just executed.

To reproduce this, create an elderly with a lastvisit date, and a next visit date that is in the past, and use the command "edit INDEX lv/" to clear the last visit date

When a last visit date is in the future, the user gets a warning but there is no other indication on the application box. However, when a future visit is in the past, the date is highlighted in red, and the contact box for the user is in red as well.

Although this is explicitly stated in the UG, perhaps restricting it to alphanumeric, or even strictly only alphabets might be better, given the form we expect a language to come in.

The application at present appears to allow the exact same datetime for Nextvisit and Lastvisit. Perhaps this should be disallowed, given that this is most likely a user error if it comes up in practice?

The UG states that parameters for an argument can be given in any order, however this does not appear to work for delete, as shown above.

The application appears to recognise the wrong error here. I gave the wrong label for next visit (nv/) but the correct date, and receive a warning about the format of the date, instead of a notice that I have given the wrong command.

The example for list w/ is abrubtly cut off.

I felt that reading this alone, it was not clear exactly what executing this command will do. For instance, what the format of the saved data will be, and what exactly will be contained. It is also unclear what the user should expect when executing the command (does the download happen immediately, will the user get to choose the location, etc.)

The phone number field has a hard cap of 8 digits, disallowing local codes. This prevents the user from keying in any non-singaporean phone numbers. The user guide does not seem to make explicit that the application is meant for use only in Singapore, so perhaps this can be outlined in the documentation, or otherwise made more lenient.

Two contacts with the same name are considered duplicates, but this does not appear to be mentioned in the User Guide. Given that it is possible for two different people to have the exact same name, perhaps a note should be added that this was intentional behavior? Either that or perhaps updating the way in which duplicates are detected. The given example above shows an attempt to add a new person with the same name, with entirely different fields

Perhaps more detail can be provided in the documentation, rather then simply stating "statistics", to help the user know what to expect. For example, the fact that the summary shows the total number of elderly is not reflected in the documentation.