Team's Response

As described in the UG, set su command does not allow user to set the modules to S/U. Rather, it provides user with a suggestion of which modules to S/U in order to achieve the best CAP. Thus in this case, since S/Uing cs2113 will result in the user having no CAP rather than a CAP of 3.5, it provides a suggestion to not S/U any subject. Whether or not having no CAP or low CAP is better is arguable, hence as explained in the UG, we have simplified this argument to prevent the perversion of such a feature. In the UG, we have stated that when you have NO CAP it will be treated as 0.00 GPA. Hence, the program suggesting you not to SU anything is actually legitimate and at the end of the day, an intended result.

Furthermore, if the user would wishes to S/U a specific module, he CAN do it in the academic planner page and edit the module to a 'S' or 'U' grade. This should be no issue for a fast typist undergraduate, which is the core audience if this program. From the capcalc screen you are at, it requires a acadplan, edit cs2113, 2 then a s or u. 4 commands which is reasonable. Another way is to simply terminate the program in any way you wish and edit the save file yourself to su your module you wish. Thus there is no ill effect, as you are looking for the functionality at the wrong place. Hence saying that

 I just CANNOT s/u the mod I want because the program deems it unnecessary. It does not even give me a choice.

is grossly untrue and missleading to a large extent, which over-inflates this issue severely. You can SU the module, and the program suggesting the mod to not be SUed is legitimate.

Thus, we feel the value of this bug, as per CS2113 module guidelines would be rejected instead of the HIGH reported. HIGH severity bug is as such:

severity.High : A flaw that affects most users and causes major problems for users. i.e., makes the product almost unusable for most users.

There is no major problems arising from this inability to SU at this stage (you can SU in acadplan) and thus the program is miles away from being unusable for most users.

For these reasons, we are rejecting this issue as you can su the module as per the title in your bug report.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: [replace this with your explanation]

❓ Issue severity

Team chose [severity.Low]
Originally [severity.High]

• I disagree

Reason for disagreement: [replace this with your explanation]

from pe.