Non-Functional Requirements

A software requirement that describes how the software will function rather than what the software will do is called non -functional requirement (NFR).

Non-Functional Requirements need to be gathered from the business and technical users to complement the functional requirements for the solution.

There are numerous reasons why Non Functional requirements are difficult to identify and test:

  • They can be interpreted differently by different users. For example, for an expert, some documentation and training material may be easy to learn, but for entry level personnel it might be difficult.
  • The relevance or importance of a NFR might vary depending on the system or products and services under consideration. For example in the financial services industry, accuracy or correctness of information and software security would be amongst the most important quality attributes.
  • Goals of two different NFRs can be conflicting. For example, the extra code and processing requirements to increase usability usually increases processing run-time, thus hampering performance.

Examples of NFR:

  1. The system shall allow access to only approved users
  2. The system shall provide controls and be configured to ensure each user has access to only the information and functions for which they are authorized.
  3. The system shall be accessible 24/7
  4. Response time to display the Website screens should be less than {#} seconds on average.
Last modified on Saturday, 11 March 2017 21:33
Tagged under
Share this article

Contact info

About us


Join the network: We are Business Folks, analyzing IT projects.
We use cookies to improve our website. By continuing to use this website, you are giving consent to cookies being used. More details…