weishuangtan / pe Goto Github PK

This might not be suited for all users if calories are being kept within a limit and if a big eater is eating more than 3000 calories. This will result in the file creation error, and also in the file being unable to load and delete properly.

This is the aim of the application, which did not specify on the age range of users.

Students who are facing underweight problems may want to use this application to gain weight, but are unable to do so due to the restriction given when creating the user profile.

A solution could perhaps be more specific about your target audience, or increase the range of height and weight for users to input.

I first tried creating a set called "lunch" with a typo of the calories being "500 c/". The error message appeared after saying that this set was not successfully created as there was an error. I then tried to recreate again with the correct parameters this time but am however faced with the issue of having a shortcut with this name already.

There should be a return arrow after calling each of the 3 methods back to :UserSetStorage.

The description mentions 8 components but only 6 were reflected in the diagram, perhaps it is a typo?

As the errors are not properlly labelled as subsections with the naming conventions of e.g. (10.4.2), perhaps they could've been excluded to make it easier to navigate around the User Guide, as the table of contents span across more than 2 pages now.

Two figures are labelled as Figure 2, and there are more figure numbers that do not follow the correct order. Perhaps you can check through and make the necessary edits for this.

There is a broken activation bar in the sequence diagram for GraphDrawing.

The entire help command output is placed in the User Guide, which also lengthens the guide a lot. Perhaps just showing the first three rows of the output will suffice. Also, the Help Command itself is not aligned properly and makes it hard for users to navigate through the help list, as shown in the following:

When given multiple parameters in a single command line, there is no error message and activity is still successfully moved. Perhaps an error message could've been printed to make it clearer to users?

There are too many expected outputs, especially when listing out all the possibilities for the user input to have errors. I think that since the error messages shown in the application is self-explanatory, there is minimal need to place these in the User Guide, which lengthens it greatly and making it quite hard to navigate around.

This is shown in the UG:

which differs from the actual output:

Section 2.0 Prerequisites is placed as a subsection under Section 1.0 Introduction.

Also, there are severe misalignments for the labelling of subsections as shown, where 4.4 onwards were indented to the right:

Even after the message to delete the file, the text file "lunch" still remains in the repository as shown.

I am unable to recreate a set called "lunch" unless I manually delete the "lunch" text file.

The statement is contradictory with the expected output. I think you meant that "Weight goals is specified as..."?

Bullet points are not showing up properly.

Examples: 4.1, 6.1, 7.3.1.

When Ctrl + C is used to terminate the file at this point, the jar file crashes with a "Null Pointer Exception". Perhaps a try catch could've been used to make the file terminate more gracefully.

When user inputs female with an empty space behind, the error message says "invalid gender format", which may seem a little contradictory. Perhaps you can include trimming in your code?

The current sequence diagram as shown is quite lengthy and decreases its resolution greatly. Perhaps the bars could be shortened? Also, the condition [if ActivityList is null] should be written on the right hand side of "opt".

The subsections like 10.1 and 10.1.1 were all aligned it was non-intuitive that 10.1.1 was a section under 10.1. Perhaps this could have been done instead:

10.0 Graph - Rani Karthigeyan Rajendrakumar
(1 space)10.1 Showing past net calories
(1 space) (1 space) 10.1.1 Possible errors when graphing
(1 space) (1 space) - Adding extra inputs after graph command