nus-pe-bot
commented
1 year ago Team's Response
Our application is only a tracker so the onus is on the user to add the correct module details, as stated in our UG
Furthermore, the functionality of all the commands are still the same.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [x] I disagree
Reason for disagreement: I disagree with the assessment that it is not in scope, but I agree with the assessment that this is in fact a feature flaw rather than a functionality issue. based on what the fact that the difference between this and someone merely using an excel sheet is the fact that the application actively tags modules as part of the degree requirements, and displays a corresponding dashboard. Furthermore, the DG states "MODTrek is a desktop application for managing a typical NUS Computer Science student’s modules and degree progression, optimised for use via a Command Line Interface (CLI). " the choice of the word 'manage' rather than 'track' implies that the user is expected to act (i.e. take modules based at different timings) based on the information stored in the application. Hence it is important that the information stored here is accurate. There are a limited number of modules (especially those most important and common to the CS curriculum), that have more or less than 4 MCs. Hence, the lack of attempt, and not stating this as a future feature, suggest to me that this is a problem in product design, rather than the scope.
## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** Again, DG states "MODTrek is a desktop application for managing a typical NUS Computer Science student’s modules and degree progression, optimised for use via a Command Line Interface (CLI). " the choice of the word 'manage' rather than 'track' implies that the user is expected to act (i.e. take modules based at different timings) based on the information stored in the application. At the worst case, a user who acts on the wrongly entered information may have to extend semesters, rendering objective of 'managing' the users 'degree progresson' as not achieved.
Modtrek purports to be able to assist the undergraduate in tracking the degree progress, however this might be trouble some if they are able to mistakenly key in the wrong number of MCs for a given module. This can prove extremely bad for the undergraduate as they may have mistakenly planned their curriculum. This diminishes the utility of using modtrek because one would then still have to go and match the required MCs with the actual degree requirement. Since this goes against the claimed functionality of the app, i will list this as a functionality bug. Since most of the undergraduates know the number of MCs for a given mod. The severity of this is not high. However, I will keep this as medium since this can happen also due to forgetfulness, and the consequences are quite severe should they plan their undergraduate curriculum using this application. I hope you understand this decision. (For the screenshot, you can see from the message that i have succesfully added a known 4mc module, CS2100, as a 5mc module)