nus-se-bot
commented
1 year ago Team's Response
We recognise this as an unfulfilled NFR and its clear the feature is doable with various encryption, password etc. Thus should be classified as a FeatureFlaw. However, this bug was reported during the Part II (Evaluating Documents) stage of the PE. Thus we will reject this bug as it is not related to the quality of documentation.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: During Phase 1, it is unreasonable to demand a tester to test the DG also, which is why this is not caught in Phase 1.
The reasoning is also wrong. The NFR is CLEARLY not met by the product, but the team backs it up by saying " its clear the feature is doable with various encryption, password etc". From the screenshot, it is already said that the NFR is not met, then it is a documentation bug, which it is in this case.
Furthermore, the team understands it is a bug but chose to reject it...
:question: Issue type
Team chose [type.FeatureFlaw]
Originally [type.DocumentationBug]
- [x] I disagree
Reason for disagreement: During Phase 1, it is unreasonable to demand a tester to test the DG also, which is why this is not caught in Phase 1.
The reasoning is also wrong. The NFR is CLEARLY not met by the product, but the team backs it up by saying " its clear the feature is doable with various encryption, password etc". From the screenshot, it is already said that the NFR is not met, then it is a documentation bug, which it is in this case.
Furthermore, the team understands it is a bug but chose to reject it...
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [x] I disagree
Reason for disagreement:
The reader may try to find where is the promised NFR, and scan through the entire document and app to no avail (which I did), which is extremely misleading.
NFRs should be achieved already, however there are no authority rules in the app.