Often, you have to deal with the non-functional requirements (NFRs) in your application. For project success, it is highly essential to address them, as they have a broader impact on the overall project and solution. These NFRs can make or break your user base, and address very critical aspects of a solution such as security, availability, latency concerns, maintenance, logging, masking confidential information, performance concerns, reliability, maintainability, scalability, usability, and so on. If these are not considered on time, it can impact your project delivery.
The following diagram shows some of the most common NFRs:
As shown, NFRs include the following attributes of solution architecture. However, there can be more NFRs, depending upon the project:
- Disaster recovery: To make sure the solution is up and running in case of any unforeseen events.
- Security and compliance: Put a safety net...