nus-pe-bot
commented
5 months ago Team's Response
This decision was made as the student note feature is not a key feature of the product. TutorsGo focuses mainly on scheduling and managing students classes, hence the note feature was made as a simple GUI extension.
We believe the severity of the feature should be low, as it is unlikely to affect normal operations of the product, which are the scheduling and managing students. It only appears in very rare situations (because not every student would have a note) and causes a minor inconvenience only.
However, we do accept that the note feature should be able to be accessed through a command, which can be a feature enhancement in the future!
Items for the Tester to Verify
:question: Issue severity
Team chose [severity.Low]
Originally [severity.High]
- [x] I disagree
Reason for disagreement: Thank you for your response!
I politely differ from the opinion that the note is not a key feature. In the first sentence of the user guide, the app was introduced as follows:
Given the team mentioned the app focuses on scheduling and managing student details, the open note feature is included in the add student feature which involves adding all information relevant to schedules and student details management as seen below, including grade, attendance as well as notes. The user guide does not elaborate on what the student's notes serve to add. Therefore, since TutorsGo added the note parameter to the "add student feature" which is a key feature of the application, it may be understood that it is indeed part of the management of student classes by adding key remarks about student progress etc.
Since the key feature is managing students, this would include adding notes about the student's progress based on the expected behaviour of the tutor application. The other optional yet relevant parameters like grade and subject in the "add student feature" can be seen once the student is added in the GUI, unlike the open note feature which cannot be accessed via the CLI. As such, this will largely affect the normal operations of the application, and this feature is not rare and does cause a major inconvenience for users.
According to the tP constraint, the application should be targeting users who can type fast and prefer typing over other means of input which is expected to be adhered to by all the teams. So it can be safely understood that this will make the open note feature unusable for the target users since they cannot access this feature via the CLI at all. Therefore, the severity should not be low and should remain classified as severity high is defined as the feature being "almost unusable for most users".
Not only that, this is an important constraint to adhere to consider since all other groups had to adhere to this constraint to cater to the target users of "fast typers" specified by the 2103T team for better comparability, thus the fact that this feature can only be accessed through the GUI can therefore be classified as a highly crucial feature flaw.
Therefore, I would like to maintain that the issue is still high severity based on the tP constraints and the
Description
Open note feature can only be accessed by clicking on the GUI, which does not adhere to the project constraints which mention that the product should be targeting users who can type fast and prefer typing over other means of input, thus violating this constraint for target users who are fast typers thus making this feature rather unusable.
Steps to reproduce
Expected
Actual
Screenshot