Open teoks0199 opened 1 year ago
The NFR being hard to quantify is the same as the bug we believe this to be a duplicate of. This is because the issue here is the ability to quantify the same NFR.
[The team marked this bug as a duplicate of the following bug]
Hard to quantify NFR
Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.
In the 3rd NFR, it is not clear what the average typing speed is and how to tell if it is faster than a mouse.
[original: nus-cs2103-AY2324S1/pe-interim#1687] [original labels: type.DocumentationBug severity.VeryLow]
[This is the team's response to the above 'original' bug]
Hello, thank you for your bug report.
While we understand that attributing some numbers to what "average typing speed" is would provide some clarity. However, in the grand scheme of things, NFRs are for stakeholders to assess and evaluate the expectations of the product, and the term "average typing speed" will serve as sufficient information for the stakeholder. While the term is subjective, it still gets the message across.
Let's refer to the CS2103/T website:
Here, ambiguous terms such as "novice" and "images deemed offensive" are used. While they are ambiguous, they still get the general message across to the stakeholders.
As such, we will have to reject your bug report.
Warmest Regards,
Team F.A.K.E.J.A.R.V.I.S.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
Reason for disagreement: This is a separate NFR, so it should not be a duplicate issue.
Hard to quantify what is considered as intuitive.