icewizard4902 / pe Goto Github PK

From the UG of sort

Is it a little bit unintuitive for the user to figure out how to specify the order (entered after the o/ flag) here? The explanation and example command does not include any clue for the user wanting to sort the tasks in ascending order.

This is only made clear in the actual application:

Should the UG for sort include an example for sorting in ascending order as well. The example command for this appeared in the command summary though:

When the user types in an incorrect command, in this case sort x/time o/ascend

The example command given has a typo: it should have a space between sort and x/

From the UG, it seems like there are no limitations/specifications on how the user should name a tag.

From the testing in the actual application, it seems like only alphanumeric tags are allowed.

Should the UG include specifications of the tags - they should only contain alphanumeric characters?

It seems like the user cannot store any workload (tutorials, assignments, ...) beyond the scope of the year 2021, as shown here:

From the overview of the user guide,

Should a product for managing university workload be used in any other year other than 2021? Our juniors might be interested to use this product, thus it should be able to handle workload in future years according to the user guide given.

The user guide for show does not mention anything about this limitation.

The developer guide for show does not mention design choices related to this limitation in the time range of the workload stored.

There is only this in the user guide specified that the year should be 2021.

Hence, this is a feature flaw as a university workload management application should be able to handle workload in other years (2022, 2023,..) as well, not just 2021.

From the UG of delete

It seems like this delete feature deletes tasks by the given ids in the general task list (the list which contains all the tasks of the user).

I believe the documentation for this feature forgot to specify that the task list that the delete feature operated on is the displayed task list.

From using the delete command, as shown in the steps taken:

I added three new entries with the name of Task4 using the add command. 2 of the entries were entered in earlier.

The result of the add command.

The result of inputting find Task4.

Now, if I typed in delete 1, from the UG I should expect the first element in the task list (using the list command) to be deleted.

However, the behavior here seems like the entry deleted is the first entry in the displayed task list.

Hence, rather than a functionality/feature bug, I believe this is a documentation bug.

Should the format for viewing help here be help?

From the UG, it seems like there are two ways of showing all the tasks in a specific week.

From the DG, it seems like there is only one way adopted for this feature in the current implementation.

Are there inconsistencies between the DG and the UG?

It seems like there are only three priority levels for workload in this product: LOW, MEDIUM, HIGH.

Would typing these priority be a burden for users. Most university students should have at least 10 tasks per week. Continuously typing the priority for 10 tasks every week can be a little annoying as it only accepts the priority in all caps. Typing in medium as a priority level is not accepted though.

Perhaps, since there are only 3 priority levels, the priority levels can be shortened to L, M, H? Or should this feature accept priority in both no caps and with caps?

Dummy