yeppog / pe Goto Github PK

Error message not specific as this is not due to a format issue but an invalid date of 2022-02-29 not existing (leap year issue). This could be a potential problem.

From the UG:

We would assume the target audience to not be particularly technologically savvy, and they would process many patients per day due to the COVID-19 situation in Singapore.

In this case, the GUI only serves as means to view, but there is no GUI functionality for the CLI actions. Given that the users of the application may not be technologically savvy, having CLI as the only means of operations could render the application very much unlikely to be used since. Furthermore, with no means of repeating actions, importing from external sources, the data processing method is extremely tedious and not feasible for the scale the application is set out to be built for.

While I understand that it is optimised for CLI use, the GUI only serves as a display means, which could be easily done through CLI eitherways.

Lastly, the target audience of this application may not be the most correct, as it is meant for contact tracing personnel, but is only built for people who prefer CLI.

In Person, fields are custom wrappers around their specific purpose, which extends the abstract class Attribute<T>. This abstract class is not documented in the diagram above.

Given that this is a app for tracking, it is not safe to assume that every single person being added will have a phone number belonging to the same country code, in this case Singapore, hence country codes should be allowed in the phone number field.

find takes a considerable amount of time to look through the list to filter. It took me about 2-3 seconds to return all results.

list ends up taking about 5-8 seconds to reset the filter with a size of only 20 contacts. Given that this is an app to trace covid patients and that the covid infection rate in singapore is very high, this app would be unable to support the scale required. Furthermore, given that the limit is 6 digit for the case number, I would be expecting smooth operation for up to 999999 cases.

find is not able to look through all possible fields of Person, which may be troublesome if there is a need to search through NOK names or NOK phone number.

In the above example, if a user has a long address, it is not possible to view the entirety of it. Furthermore, the app width is fixed and cannot be expanded, hence there is absolutely no way of viewing the address other than going into track2gather.json, which defeats the purpose of the app due to to poor UX.

The example and command format could have been separated into different columns to increase readability.

e.g

2021-11-12 17-06-53.mp4

The application runs rather choppily (really laggy while scrolling as seen in the video) with only 50 people in the list. Furthermore, it is taking up 2gb of my ram with only 50 contacts, even chrome with 23 tabs doesnt take up that much ram. This is a huge issue if the application is to be used by contact tracing personnel, as their computers might not be capable to handle this much load, especially when there are way more contacts to be involved in a real situation.

A new .json file is not actually generated until the first command is input. The original .json file stays in the folder until the app writes something to a new .json file.

As per title.

The application has a fixed width and it is frustrating to use such a small window on a big monitor. The window width show be allowed to be flexible to cater to different users.

Furthermore, it cant be shrunk either, which means users with low resolution screens, e.g 800x600 may be unable to use the application properly

Not too sure what the definition of Private contact detail is for. It is not seen elsewhere in the DG.

I guess User is universal, but some specificity could have been added.

Unable to resize window horizontally on my OS, but said to be able to.

In the UG, the example to add a Person with all details lacks a space before sh, causing the date to be appended to the address field instead.