soc-se-bot
commented
2 months ago Team's Response
No details provided by team.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Empty boxes for the user stories in developer guide
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.
There are three users stories and 3 empty boxes below those three user stories.
[original: nus-cs2103-AY2324S2/pe-interim#3063] [original labels: type.DocumentationBug severity.VeryLow]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
Valid.
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)
- [x] I disagree
Reason for disagreement: This is not duplicate issue to the above. The issue "claimed" to be duplicate above is the cosmetic issue where there is an empty boxes below the user stories, which has severity verylow. However, the issue claimed here is that the list of user stories omit most of very important user stories that lead to implementing a key feature for this product.
## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [x] I disagree **Reason for disagreement:** This issue is not a cosmetic issue. As explained in the "issue duplicate status" above, the issue is that the list of user stories omit some key features that need to be considerd for this product to be useful to the users. For instance, as delineated above, user stories such as "As a EXCO / CCA member, I want to enroll into different CCAs with different roles so that I can be part of multiple CCAs as different positions / roles" is one of a key feature that need to be considered for the product, or "As a EXCO member, I want to filter CCA members by their roles and CCA they are enrolled in so that I can have an overview of which roles are empty (such that we can decide whether we need to recruit more students for) and quickly search for who is taking the position in the provided CCA." Other than the abovementioned user stories, lots of other key user stories are missing for the team's developer guide, which make it harder for developers to overview the key features developed and the necessary user requirements of this product.
For the above user stories, some important user stories that would be the key features of the product is missing. E.g.
As a EXCO / CCA member | I want to enroll into different CCAs with different roles | so that I can be part of multiple CCAs as different positions / roles
As a EXCO member | I want to know the total number of attendance of members | so that I can keep track\ of the attendance for important events or the society meetings