text: Q:
  
  Is providing a user login a functional requirement of a system?
  
  Is providing a user login a non functional requirement?
  Since this is concerned with security which is a non functional requirement, I feel that providing a user login is also non functional but again I feel that it is functional.
  
  A:
  
  User logins are more of a "feature" than a "requirement." 
  If you said "System shall block user from access to [some area of the system] if they are not logged in," or "System shall block user from access to [some area of the system] if they don't have the necessary security credentials," then it would be a functional requirement.
  Requirements should always be accompanied by a test that, when executed, constitutes proof to the stakeholders that a requirement has been met.  Otherwise, it's not a requirement.  "System shall have user logins" is not a requirement, because you can merely have user and password fields on some form and call it a login system.
  
  