search

kab-dot / pe

0 stars 0 forks source link

User stories incomplete #20

Open kab-dot opened 2 months ago

kab-dot commented 2 months ago

Screenshot 2024-04-19 at 5.35.29 PM.png User stories are incomplete, last part could be added to make it more thorough

nus-se-script commented 2 months ago

Team's Response

Please refer: https://nus-cs2103-ay2324s2.github.io/website/se-book-adapted/chapters/specifyingRequirements.html#user-stories

image.png

The benefit of adding, editing and deleting contacts are obvious [easily perceived or understood; clear, self-evident, or apparent] , as they are the expected minimal features for any management system to function, and their benefits are self-evident, apparent and clear.

This is in contrast to other user stories that may need additional clarification on the benefits, in which the DG has provided additional explanation under {benefit}.

As tester is mistaken in the allowable format of user stories, this bug is given response.Rejected label and is invalid.

The 'Original' Bug

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

Not all Three Part Present in the User Stories - DG

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.

Screenshot 2024-04-19 at 5.19.02 PM.png

In the user stories section of the developer guide, the first three user stories are incomplete. The "So that I can..." section is missing for these three.

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

Their Response to the 'Original' Bug

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

Please refer: https://nus-cs2103-ay2324s2.github.io/website/se-book-adapted/chapters/specifyingRequirements.html#user-stories

image.png

The benefit of adding, editing and deleting contacts are obvious [easily perceived or understood; clear, self-evident, or apparent] , as they are the expected minimal features for any management system to function, and their benefits are self-evident, apparent and clear.

This is in contrast to other user stories that may need additional clarification on the benefits, in which we have provided additional explanation under {benefit}.

As tester is mistaken in the allowable format of user stories, this bug is given response.Rejected label and is invalid.

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: [replace this with your explanation]

## :question: Issue response Team chose [`response.Rejected`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]