Non Functional Requirements

Hello friends! in this post, we will be learning about Non-Functional Requirements or NFRs. We will also study the different examples and attributes of quality that comprise an NFR document.

What are Non-Functional Requirements?

Non-functional requirements or NFRs are the set of requirements that defines how well a system will operate as opposed to functional requirements that focus on the specific business functionalities that an application performs.

The way an application will operate is nothing but some defined quality parameters like accessibility, efficiency, reliability, usability, interoperability, etc. on the basis of which application’s quality is measured.

Attributes of NFRs

Following are some of the attributes of examples of NFRs-

1. Usability – Usability is defined as the measure of the degree to which an application can be easily used and operated. For example, in the case of a new application, the easier the flow of the application is for the user to operate it smoothly, the better will be the usability.
2. Scalability – Scalability is defined as the ability of the system to cater to the growing usage of the application. It is of two types horizontal and vertical scaling.

   Horizontal scaling is provided by adding more machines. Vertical scaling is provided by adding more CPU and RAM to the available machines.

3. Security – Security is one of the most important attributes of NFRs. It is the measure of the resilience of the application under any type of malicious attack.
4. Accessibility – Accessibility is the ability of an application to cater to the needs of the user with special needs or disabilities using some Assistive technology like screen readers.
5. Data integrity – Data integrity deals with the integrity, consistency, and correctness of the data in the application.
6. Durability – Durability is the measure of the ability of the application to cater to the requirements for a long period of time.
7. Interoperability – Interoperability is the ability of an application to work in conjunction with other applications smoothly at present as well as in the future.
8. Maintainability – Maintainability is defined as the ease with which an application can be restored to working conditions after a failure.
9. Performance – Performance is a non-functional requirement that deals with the measure of the response time of the application under different load conditions.
10. Reliability – Reliability of a software system makes use of the Mean Time Between Failure (MTBF) parameter that is the time elapsed between 2 failures. The longer the MTBF the more reliable is the application.
11. Robustness – The robustness of a software application is the measure of the ability of a software application to deal with invalid or erroneous input effectively.

Conclusion

This completes our tutorial on NFRs, its attributes, and examples. Let us know in case of any query or suggestion. You can also check our related tutorial – Non-Functional Testing which is based on testing all these non-functional requirements.

Еще об этом:

Non Functional Testing Quality Assurance Software Requirement Specifications in Software Engineering Manual Testing Interview Questions and Answers Quality Assurance vs Quality Control Requirements Traceability Matrix JAVASCRIPTEXECUTOR В SELENIUM WEBDRIVER, МЕТОДЫ С ПРИМЕРАМИ Waterfall Model in Software Engineering What is Manual Testing? Top Agile Methodology Interview Questions You Must Prepare