search

jytheawesome / pe

0 stars 0 forks source link

Non functional requirements are not scoped clearly (i.e., hard to decide when it has been met) #15

Open jytheawesome opened 1 year ago

jytheawesome commented 1 year ago

For NFRs 3 - 7, they are ambiguous and not scoped clearly. It is probably going to be hard to decide when it has been met.

image.png

soc-pe-bot commented 1 year ago

Team's Response

The description of the issue is not phrase properly. Owner of bug report state that the NFR is generic and ambiguous but does not mention why and how or any missing parts. The team feels that "generic" and "ambiguous" should not be the reason why NFR should be wrong and be a bug. Hence, we are unable to accept this bug report in our stance as NFR are used to gauge how our app should work in an environment. We will only accept if there is any missing NFR which the owner did not state.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: Thanks for the response from the developer team.

Respectfully, I have to disagree here. I mentioned in the issue that Non-Functional Requirements 3 - 7 are ambiguous and not scoped clearly. Hence, it would be hard to decide when they are met.

For example, for NFR no.3, it is stated that the user with above average typing speed should be able to accomplish tasks faster using commands than the mouse. However, this is contentious. What is average typing speed? And how many seconds faster does the user have to be? As this is not mentioned, it would be hard to determine if the NFR is fulfilled or not, and may be up to personal interpretation.

For NFR no5, it is mentioned the app should start up fast. How many seconds would this roughly be? It is not stated.

For NFR no6, it is mentioned the app should work on most screen resolutions. Which screen resolutions are we talking about here? 1920 x 1080? 1366 x 768? 1280 x 1024? This is not specified as well.

For NFR no7, it is mentioned that the app should not consume too much battery or data usage on the device. Again, it is not mentioned how much battery percentage should be consumed, or how many megabytes of data should be consumed. Also, as the app is an offline application, it should not consume any data at all.

For the above reasons, since no specific details and figures are used to describe the NFRs, it is going to be very hard to decide when the NFRs have been fulfilled. Hence, I think this should be a valid issue.

This is a screenshot from the module website dictating when NFRs may consist of bugs:

image.png