chenling1022 / pe Goto Github PK

In sections like this, in the command, the user name input should be case-sensitive or not? I think it is better to indicate clearly in the UG, or else it might cause confusion to users.

As shown here, after adding tom as an employee, when I tried to add schedule to tom, it worked. However, when I tried to add schedule to Tom, it did not work. This shows that the input for user name is case sensitive, which is not specified in the UG. This may cause confusion to users.

As shown here, the shift date instructions are different in the same section of the UG, this may cause confusion to users when they input the date and encounter error even though they are following your instruction by inputting DDMMYYYY.

Symbols to represent user are different in 2 sequence diagrams, this might cause confusion to readers.

In the entire DG, there is only 1 class shown in the class diagram. This will overlook the relations among the interacting classes.

As shown in the circle region, there is typo error.

I personally feel that the list of all shifts without showing the employees who are assigned to this shift should be shown here, after the command is called by users, to make it more user-friendly, because users may not remember what are the available shifts in the system.

As shown here, the vacancy I input was 1000. this is abnormally large, and should be possibly handled as an error input.

As shown here, I inputed 'add shift', and when I was asked to enter an employee name to assign to this shift, when all of the employees do not have schedules that fit into this particular shift date, there is no way for me to go back to input new command.....

As shown here, after adding a shift, even thought I did not assign an employee at that time, but the shift should be successfully added. However, after that, I wanted to add another employee to the shift, the shift does not exists.

One possible flaw of the program is that the program does not enable users to delete the employee from the database, which would improve the functionality of the entire program.

As shown here, after I typed a non-existing user name, I feel that the system should be able to allow me to re-enter, instead of having to start from the beginning command again.

It is a bit hard to show it down here, but I think you should be able to reproduce this in your own testing. I feel that if you are doing exact string matching, then should inform the users in the UG to ensure convenience. This is because some of the users have the habit to input a spacing after they type a command. It is better to address this as well.

These parts are unnecessary, it is simply the instruction given in the template.