search

kayyenl / pe

0 stars 0 forks source link

NFR does not make sense #15

Open kayyenl opened 1 year ago

kayyenl commented 1 year ago

image.png

In NFR number #3, it is said that a user with average typing speed should accomplish the todos faster using commands than using the mouse. However, there is no reference to what "mouse commands" mean. In this case, since there are no mouse commands available for use within Calidr, it is quite ambiguous.

nus-pe-script commented 1 year ago

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Ambiguous NFR phrasing

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.

image.png

In NFR #3, it is said that the user "should be able to accomplish most of the todos faster...". Does this refer to the execution of the todo tasks (actually doing each stated todo task) or the execution of commands related to the todo tasks?

What can be done: Better phrasing can be done to improve overall DG readability.

[original: nus-cs2103-AY2223S2/pe-interim#153] [original labels: severity.Low type.DocumentationBug]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

No details provided by team.

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 ambiguity is a separate issue compared to the one above. In this issue, the "mouse commands" are seemingly non-existent, so I don't know exactly what you were referring to when you mentioned it.

The other issue marked as its duplicate is talking about a different kind of ambiguity.

## :question: Issue response Team chose [`response.NotInScope`] - [x] I disagree **Reason for disagreement:** This isn't a good-to-have bug. Maybe explain why it is, or it will just look like a middle ground was trying to be made :(
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** Since no reasoning was being provided to explain this change in severity, I can't really counter-argue this...