Source:- Non functional requirements
For more questions and answers visit our website at Frontend Interview Questions
Non-functional requirements, also known as quality attributes or system properties, specify the characteristics and constraints that define the overall behavior, performance, and user experience of a software system. Unlike functional requirements that describe specific features and functionalities, non-functional requirements focus on the system’s attributes, qualities, and constraints. Here are some common categories of non-functional requirements:
- Performance: Specifies how the system should behave in terms of response time, throughput, scalability, and resource utilization. Examples include: — Response time should be less than 200 milliseconds for a given operation. — The system should handle a minimum of 1000 concurrent users. — The system should process a minimum of 1000 requests per second.
- Security: Describes the measures and constraints related to the protection of the system, data, and users’ privacy. Examples include: — User authentication and authorization mechanisms should be implemented. — Access to sensitive data should be restricted to authorized users. — The system should be protected against common security threats, such as cross-site scripting (XSS) or SQL injection.