insafhere / pe

0 stars 0 forks source link

Incorrect user story explanation #17

Open insafhere opened 1 year ago

insafhere commented 1 year ago

image.png

Perhaps can be done in this way as currently the issue is not addresses clearly:

nus-pe-bot commented 1 year ago

Team's Response

user story phrasing

The 'Original' Bug

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

User Story is unclear

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.


From DG:

image.png

Perhaps the first User story is trying to address the search feature, hence it could have been written in this way to avoid confusion:

As a "student" i want to "search for modules by module code, name or faculty" so that i am able "to know the existing/available modules i can take during my semester"


[original: nus-cs2113-AY2223S1/pe-interim#25] [original labels: type.DocumentationBug severity.Medium]

Their Response to the 'Original' Bug

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

Changing the user story's phrasing wont change how we designed the product

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 not a duplicate. This is a separate issue, addressing the search feature's objective.


:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: I still believe that the user story has not addressed the search feature's objective clearly. It addresses the addition of modules to planner instead.

It should be as follows : As a "student" i want to "search for modules by module code, name or faculty" so that i am able "to know the existing/available modules i can take during my semester"


:question: Issue severity

Team chose [severity.VeryLow] Originally [severity.Medium]

Reason for disagreement: It should be Low instead.