kaijiel24/pe

pe's Issues

Should the glossary include more common terms used inthe DG?

Should the glossary include more terms such as MCs, S/U, CAP and Semesters to ensure all the stakeholders understand the terms used?

Is there a distinction between which special grades are included in the total mcs taken and which of them are not?

From the first to the second picture only a module with grade exe is given but the total cap is not included even though it seems like it should based on the website below

Typo in UG

Is there supposed to be a closing brackets here after module code key?

Should the error message be changed when an excessively long number is entered?

Should the error shown in the picture above, be changed since the index input is not a floating point number and is considered an integer that is just out of the range. This is compared to the output when smaller integers are input as shown below which is more accurate.

Is the error for failing to create logs dir unecessary?

As shown above, the logs file was not present before the program was ran but is created by the program so was a wrong message of Failed Createing logs Directory shown?

Should the return arrow start at the end of the activation bar?

Should the return arrow start at the end of the activation bar?

Diagram opt error.

Since there are 2 possible paths provided should it be alt instead of opt?

Add separator to table

Is it better to add a separator in the table above so it is obvious where the individula column title starts and ends

Is it necessary to create a new logs dir when there is an existing one?

As shown above, should the program have checked for an existing logs dir before attempting to create a new one for each session?

Should there be a one-liner option for most of the commands available?

Most of the commands require multiple steps inputs which might not be optimised for a fast typist as they have to wait for the prompt to the next step? For example the add command in acadplan:

It takes 2 addtional steps to add a single module with no option for a single line command.

Other commands that require multiple stpes include:
acadplan:

• edit
• view

capcalc:

• set target
• set su

Below is the recommendation from the module website

Should there be a one-liner option for these commands?

Should the error message be when a wrong cap target is entered?

Should the error message be changed since floating point numbers such as 3.5 for cap is allowed and input is not strictly limited to integer values only?

Should the error message when a floating point number is input be changed?

No details provided.

Should the error message when the a floating point number is entered be changed? Maybe "Floating point number not allowed" will be more accurate