Non functional requirements in Software Development

Non functional requirements

1. NON-FUNCTIONAL
REQUIREMENTS
Sumit Mukherjee

2. WHAT IS IT?
Non-functional requirements or NFRs are
requirements that talk about the
performance or quality attributes of the
system or solution.
NFRs generally apply to the overall
system or solution and not any specific
components.

3. WHY IS IT IMPORTANT?
NFRs are non-negotiable; they are the
constraints under which the solution
must exist and thus may impact
architectural and implementation
decisions.
Non-functional requirements (NFRs)
supplement the functional requirements
by identifying constraints, describing
quality attributes, etc.

4. Availability
Compatibility
Maintainability
Performance
Reliability
Scalability
Security
Compliance
Extensibility
TYPES OF
NON- FUNCTIONAL
REQUIREMENTS

5. EXAMPLE
90% of transactions should be performed within 2 seconds
The system should be available on workdays 24*7
All payment transactions must adhere to SSL protocols
Server setup and data hosting must adhere to GDPR laws
The system should be able to handle load of 20k concurrent users
at any given point in time
The maintenance cost of the solution must not exceed 10% of the
ROI of the solution
Modules must be geo-restricted with users being able to access
data only belonging to their own region
A user cannot view the salary report of any other user
Data must be archived every 2 months