Introduction
Non-Functional Requirements are the constraints or the requirements imposed on the system. They specify the quality attribute of the software. Non-Functional Requirements deal with issues like scalability, maintainability, performance, portability, security, reliability, and many more. Non-Functional Requirements address vital issues of quality for software systems.
If NFRs not addressed properly, the results can include:
Users, clients, and developers are unsatisfied. Inconsistent software. Time and cost overrun to fix the software which was prepared without keeping NFRs in mind.
Types of Non-functional Requirements :
Scalability
Reliability
Regulatory
Maintainability
Serviceability
Utility
Security
Manageability
Data integrity
Capacity
Regulatory
Availability
Usability
Interoperability
Environmental
Categories
These can be classified as :
Performance constraints – Reliability, security, response time, etc.
Operating constraints – These include physical constraints (size, weight), personnel availability, skill level considerations, system accessibility for maintenance, etc.
Interface constraints – These describe how the system is to interface with its environment, users, and other systems. For example, user interfaces and their qualities (e.g., user-friendliness).
Economic constraints – Immediate and/or long-term costs.
Lifecycle requirements – Quality of the design: These measured in terms such as maintainability, enhance ability, portability.
Zero Friction and Non Functionals
Under this section you will find the non functionals of the Zero Friction Platform
Data Processing Agreement
Ennvironments
Releases
Security
Service Level Agreement
Single Sign On
User Profiles