NFR : None Functional Requirement in Software Engineering or Application Development : Part 1

Here is the link of all of my posts on topic NFR:

Links:

• NFR : None Functional Requirement in Software Engineering or Application Development : Part 1
• NFR : None Functional Requirement in Software Engineering or Application Development : Part 2: Scalability, Performance, Testability
• NFR : None Functional Requirement in Software Engineering or Application Development : Part 3: Application Security
• NFR : None Functional Requirement in Software Engineering or Application Development : Part 4: Extensibility, Observability, Maintainability

NFR(None Functional Requirement) is abbreviated as Non Functional Requirement. In any application development or maintenance work, the NFRs are least discussed but most required activities. Generally, the NFRs of an application are not discussed by Business team. Its Developer's team's responsibility to discuss all the NFRs with business teams and try to understand and create a document of the discussion regarding NFRs implementation with Business team. There may be several discussion points regarding NFRs with Business team like:

1. Expected minimum or maximum load on application
2. What is the pick time and off pick time of the application usage
3. Is the application public facing or only client's employee facing
4. Application downtime required for build deployment or any upgradation
5. Response throughput in terms of millisecond required for a feature
6. Negotiation in business requirement to achieve the required throughput.
7. Whether the application's feature is read extensive or write extensive to decide how frequently data should be flushed in caching if caching is implemented
8. Whether customer requires latest data as soon as it is updated in system to decide whether to implement caching
9. Cost of any 3rd party API that Business can bear.
10. Cost of skilled resources that Business should bear till the time the application becomes stable(Should be discussed more by Management team)
11. Tradeoff analysis and discuss with Business team about conflict between different NFRs.

There are several types of Non Functional Requirements. Few important NFRs are as follows:

1. Scalability
2. Performance
3. Testability
4. Security
5. Extensibility
6. Observability
7. Maintainability

The actual list of NFRs are very vast. Here, I have included only few that are mostly required to be considered in Application development.

In my next blog, I will discuss about the above mentioned NFRs in short.