nus-pe-bot
commented
2 months ago Team's Response
This is not related to the quality of the documentation, but the quality of the application. It is true that this is a must-have user story. It has been implemented using through the remind and event commands, hence the documentation is correct. It is just that the implementation is not great, so this is not a documentation bug, but a flaw with the app. Hence, this issue is rejected since it was reported in part II.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: # Explanation
To the user, the remind and event commands does not output any information at all. It simply accepts those commands, given a valid command format. Since the current application barely even implements these features that aim to address the said user story, and that we are expected to follow the breadth-first iterative process (as seen here), user stories like these should not have been added at all, given the fact that we should have an idea of how fast the team can work (again, as seen in the link above (and screenshots below)).
Furthermore, we can see in the screenshots taken from the CS2103 website below, that we can tweak the user stories along the way, and we should avoid depth-first implementations. This bug is clearly due to a depth-first implementation since only a small portion of said feature works, and does not value-add the user at all.
To that end, the team also had opportunities to tweak the user stories along the way to account for their progress with these features (even up till v1.4). However, they did not, and chose to instead, release a non-working feature to the final product, despite having the highest priority for this related user story. It would at least make sense for them to modify this user story to a lower priority.
Screenshots
Under the User Stories of the DG, it seems like one of the must-have user stories is not implemented.