When developing software there is no such thing as a "Non-functional requirement". All requirements are functional requirements.
Agree? Disagree?
For further actions, you may consider blocking this person and/or reporting abuse
Read next
The Only Open-Source FAQ Guide You'll Ever Need—Straight From the 0x3d Collection
0x3d Site -
Next.js: Build Optimized and Scalable Web Applications
ANIRUDDHA -
How to Build a BlueSky RSS-like Bot with AWS Lambda and Terraform
Ervin Szilagyi -
Introducing Fleek Machines (Early Access): One Click Verified and Private Compute
Fleek -
Top comments (3)
Documentation (both for the user and the development process), conformity to certain standards and practices during the development, and deadlines are examples for requirements that have nothing to do with the functionality of the software.
Those are just the examples that came to mind after thinking a few seconds about it. So yes, I think there are non-functional requirements.
Documentation outside of the software is clearly a non-functional requirement, so I agree with you there!
Can you think of some examples of requirements many label as non-functional that are really in the software?
Code obfuscation (should not change the functionality, becomes inherent part of the distributed code) is the first that comes to mind.
That being said, your question implies that documentation would not be part of the software. I believe you confuse software (the product) with code (the means that makes it run on the computer).