Pace function provides redundant information

[J-Y-Yan]

As you retrieve the year of students already, like I am a year 3 student, when provide function for user to check their pace on year 1 or year 2?

[nus-pe-bot]

Team's Response

The use case is to allow the planning for future academic years and there is no reason to not allow the input of previous years as they may want to revisit the pace of Past Academic Plans. Hence bug rejected as it does not affect the usability of the application

Items for the Tester to Verify

❓ Issue response

Team chose [response.NotInScope]

• I disagree

Reason for disagreement: The pace function is used to provide information about the number of credits left in a particular semester and suggest on how many credits can be spent in the remaining year.

The tester mention user may want to revisit the pace of Past Academic Plans. That means user want to know suggestions and number of credits spent in the past academic year. This is unreasonable especially in a schedule planning app.

Imaging that I am a year-3 user planing for my module schedule, and there is a function suggesting the study plan and number of credits left in the past. This is so weird and unnecessary. I don't see in any situation that we need such a function.

The team should reevaluate the pace function and show the users only the necessary information.

---