I agree with BEF
Broadly, functional requirements define what a system is supposed to do and non-functional requirements define how a system is supposed to be. Functional requirements are usually in the form of "system shall do <requirement>", (in this question Authorization, Availability, Authentication). In contrast, non-functional requirements are in the form of "system shall be <requirement>", an overall property of the system as a whole or of a particular aspect and not a specific function. (certification, scalability, cost).
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
lobana
Highly Voted 3 years, 6 months agoJesus_M
3 years, 5 months agohelal
3 years, 6 months agoBrianOC
Highly Voted 3 years, 4 months agoAT45816
Most Recent 7 months, 2 weeks agobcquest
1 year, 1 month agoMe_Loi1
3 years, 4 months agoAymanovitchy
3 years, 6 months agodiegof1
3 years, 5 months agoRevanT
3 years, 7 months agoRevanT
3 years, 7 months ago