Inconsistent in the naming of System and Actor in Use case

[TehOPanas]

It is specified that TuitionConnect and Actor is user but the Use case never use the term TuitionConnect to represent System but uses user to represent the Actor, causing the inconsistency.

[nus-se-bot]

Team's Response

Thank you for pointing that out. However, we decided that this bug was NotInScope because it does not hinder the user from understanding the use cases.

Items for the Tester to Verify

❓ Issue response

Team chose [response.NotInScope]

• I disagree

Reason for disagreement: Thanks for the response. However, I am sorry to disagree with your stance.

First of all, I do no think that this bug is justified to be NotInScope. This is because the effort required to fix this is very minimal, all it requires is a read-through and at most 5 minutes to change the term System to TuitionConnect. Even though the impact of the bug is rather low, the developer team does not has enough justification on why fixes with such little effort needed has to be postponed to later increments.

In some scenario, it still possible for reader to be confused, even for just a brief moment, they might question why is the term System or user used instead. Thus I categorized this bug as Severity.Low.

---