nus-pe-bot
commented
3 years ago Team's Response
The issue raised suggests that most if not all points were functional requirements, but we reject it on the basis that some points are indeed valid non-functional requirements.
The first point - 'The program must be easy for admins to use' addresses usability, and the second point - 'The program should run on any system running Java 11' addresses portability.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: As developers, we should always ensure that details are accurate and specific, especially so for documentation. Every piece of information has a place where it is suppose to be and should not be placed without a care.
However, the response from the team seems to suggest that they are not as concerned with professionally addressing a potential flaw in their documentation that could be improved, but would rather play with semantics of the english language.
My stand still remains that this section of the DG could be improved by having more points relating to non-functional requirements and removing any functional requirements to prevent confusion and exhibit better organization.
The listed points below are more functional requirements than non-functional as being able to store information is part of the core feature/function. Non-functional requirements should be related to performance, load testing, Compatibility, Portability, Security. Usability.