Open Berted opened 1 year ago
No details provided by team.
[The team marked this bug as a duplicate of the following bug]
Inaccurate NFRs in DG
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.
Certain NFRs in the DG are hard to measure, for example, how would you tell that the application would work better than an excel spreadsheet?
[original: nus-cs2103-AY2223S1/pe-interim#1752] [original labels: type.DocumentationBug severity.Low]
[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: [replace this with your explanation]
What are the bounds where the efficiency of the app is better than a typical spreadsheet application?
Should we only consider users who are tabulating results? Should we also consider users using macros and functions to improve their spreadsheet to a point where it's very efficient? I find this NFR to not be very clearly scoped.