search

nknguyenhc / pe

0 stars 0 forks source link

Missing user story on editing a contact #12

Open nknguyenhc opened 11 months ago

nknguyenhc commented 11 months ago

As listed in the user guide and by the actual app, the user can edit a contact. However, in the list of use cases, there is no user story on editing a contact.

I think this is a very important user story that should not be missed, because a user might always key in details wrongly and need to edit a contact's details.

nus-se-script commented 11 months ago

Team's Response

This should be talking about use case, however, title of this bug report is misleading.

The 'Original' Bug

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

Missing use case on editing a contact

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.

As listed in the UG and by the actual app, user can edit a contact. However, there is no use case on editing a contact's details.

This use case is important, as it specifies how the edit command should behave, and for reference for future developers of the project.

[original: nus-cs2103-AY2324S1/pe-interim#4784] [original labels: type.DocumentationBug severity.Medium]

Their Response to the 'Original' Bug

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

Good catch, we completely missed the use case for that particular command. However, we feel that it should be a low severity as edit contact is similar to that of other commands.

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 report initially has roughly the same elaboration as the 'original' bug report, but is in fact on user story, not use case. The team misses both a user story on editing a contact and a use case on editing a contact, which are both important parts of the DG and can be fixed independently.

Base on your list of user stories found here, the user story on editing contact is obviously missing.

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** Unlike the use case on editing a contact, the user story on editing a contact does not have the same details as the other user stories. The user story on editing a contact is in fact a very important user story, so that the user can rectify their errors when keying in a contact, or when the contact's details change. No other user stories can make up for this user story if this user story is to be left out. This user story should not be left out, so that the corresponding feature is implemented and is kept throughout the next iterations.