search

Rishit02 / pe

0 stars 0 forks source link

Vague integrity NFR #33

Open Rishit02 opened 7 months ago

Rishit02 commented 7 months ago

image.png

It is unclear what exactly it means to maintain integrity. Should there not be more measures of integrity than just the save file feature?

nus-se-bot commented 7 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]

Vagueness in robustness NFR

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.

image.png

Developer might not know what exactly it means to be "highly relevant in the future". Perhaps could add come information about number of users willing to use this application which indicates robustness?

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

Their Response to the 'Original' Bug

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

No details provided by team.

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: These are different issues within the DG regarding different NFRs and their specificities. It is unclear why they are marked as duplicates.

## :question: Issue response Team chose [`response.NotInScope`] - [x] I disagree **Reason for disagreement:** It is unclear as to why this is marked as NotInScope. ![image.png](https://raw.githubusercontent.com/Rishit02/pe/main/files/9664f2bc-6a45-47a7-8da3-ef906b53007c.png) The vagueness of the NFR leaves the tester to not understand whether the product has satisfied the NFR or not. Which leads me to believe that my initial assessment of this bug could be correct.