tlchicken / pe Goto Github PK

Expected:
According to the user guide, the constraint for the start date year is that it has to be before 3000. Hence the year 0000 is valid and should be parsed but it throws an error even though it is a valid date (2 December 0000)

Actual:
The valid date input is not parsed without a better reason shown to the user reason.

Instead of just double-clicking to start the app, alternative instructions should be given in case double clicking does not work. Eg: Starting the JAR file using java -jar in the command line

Double clicking to open the JAR file does not work on Macs and some Windows devices. In the worst case, the user may not be able to start the app at all and not know how to solve the issue, hence the severity level might even be "High" since it will cause major problems. However this may not affect windows users so the severity level has been placed as "Medium"

The input of 3 digits for phone numbers is very unrealistic since the general population would not be able to acquire such a short phone number. The input validation should be stricter in this case since there is no use case for having a person with a 3 digit phone number.

There is no documentation for what the dots in the command format means. Hence the reader might not know what "..." means and have to assume and guess the multiple of such parameters are allowed. This is unrealistic for users who have not used AB3-like applications before.

Expected:
According to the user guide:

The start date of a reminder needs to be before 3000, thus changing it to an invalid date (3005 in this case) should give an error, even if this was done through editing the JSON file.

Actual:
The data is loaded as per normal even though there is an invalid date

Some text in the class diagram are bolded while others are not which is inconsistent

Expected:
The app should still open by double clicking but fail gracefully

Actual:
Nothing happens when I double click the app

In the DG:

In the UG:

The UG says that ePoch has a giant capacity but the Non-Functional-Requirements state that the system could become sluggish past 1000 objects. The difference in number of objects is very large so the soft cap of 1000 should be stated in the UG as well since the huge capacity stated in the UG is giving the reader the wrong impression of ePoch's usable capacity.

Expected:
An error message should pop up since an email needs to have a domain name separated by periods as stated here:

Actual:

There was no error message and this email address was accepted as valid input

When the window size is made to be too big, the app opens on double click but nothing pops up.

Expected: There should be a way to view the contents of long tags. As of now, long tags extend right past the CCAs window as shown in the screenshot above, with no way of viewing it. Not only is this a cosmetic issue since it goes out of the panel, it is also a Feature Flaw as the tag functionality is broken if we cannot see the contents of the tag fully.

To produce:
Use an addp command but put in an extra INVALID prefix as shown in the screenshot. This works for prefixes not used in the addp command such as sd/ f/ o/ as well.

Expected:
Error because it is an invalid command format.

Actual:
No error and command is accepted as valid with the extra prefix going into the address field as shown in the screenshot. This flaw is quite jarring as invalid prefixes are not being detected, which could affect many users who accidentally enter a wrong command format which happens frequently.

The whole section on implementation (Page 12 to 17) is all just words. Some sequence diagrams or activity diagrams could be used to explain the interactions of the commands instead of just explaining using words which is too verbose.

There are 2 indexes being referred to, not just 1.

Test

Edit 1

At Page 19 and 20 there are 2 rows containing the same headers for the user stories table. There should only be one row.

Expected:
Reminders with the same name should be allowed because it was not stated that it was not allowed in the user guide.

This can cause a huge hinderance to the user especially since different CCAs may have reminders that contain the same names. (Rehearsal 1 can happen once for each CCA, same for Rehearsal 2, 3...)

Actual:
The reminder with the same name is not allowed to be added.

To produce:
Enter an addc command that takes in the incorrect input parameters.

Expected:
The error message should point out that an extraneous prefix has been used (The address prefix)

Actual:
ePoch says that there is something wrong with the tag instead even though there is nothing wrong with it. In the worst case the user may not be able to figure out what is wrong with their command input which will hinder their usage.

Expected:
The name of the CCA should not go out of the screen when it is too long, and should be truncated gracefully.

Actual:
The name goes out of the screen as shown in the picture which looks bad.

Expected:
The error message should point out that the cid/ prefix should not be used in the editr command

Actual:
The error message talks about the name of the reminder instead even though there is nothing wrong with it. In the worse case, the user would not be able to figure out what is wrong with the command

As we can see here in findp, a space then 4 dots are used but in editp, there is no leading space and there is only 3 dots. The functionality of the dots appears to be the same, however this may indicate to the user that the dots mean different things. (Eg: findp is supposed to take in mor eparameters than editp)