search

nus-cs2103-AY2324S1 / pe-dev-response

0 stars 0 forks source link

Conflict between User Story and actual implementation #5445

Open nus-se-script opened 11 months ago

nus-se-script commented 11 months ago

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 your user story: "As an insurance agent, I want to be able to add details of appointments with customers so that I can keep track of appointments with customers". However, your current implementation only allows for one appointment to be added.

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

Jweewee commented 11 months ago

Team's Response

From the textbook, User stories should only provide enough detail to make a reasonably low risk estimate of how long the story will take to implement. When the time comes to implement the story developers will go to the customer and receive a detailed description of the requirements face to face. You can write user stories at various levels. High-level user stories, called epics (or themes) cover bigger functionality. You can then break down these epics to multiple user stories of normal size. [Epic] As a lecturer, I can monitor student participation levels. As a lecturer, I can view the forum post count of each student so that I can identify the activity level of students in the forum

In our user story, when referring to appointments with customers, this was a general description of our appointment tracker where its details are not specifically defined in the user story. We intended to refer to "appointments" as the general cumulative term of appointments of multiple customers(ie. each individual appointment with customers being summed up and cumulative). Since this user story's grammar and language still matches our implementation, we feel that this bug can be rejected. If we were to accept this bug, it would be more of a grammar issue and hence of severity*VeryLow. Hence, as this bug was reported in phase 2, and our user story is still correct, it can be rejected as compared to if it was reported as a feture flaw.

Duplicate status (if any):

--