Many requirement frameworks exemplify the types of NFRs that should be elicited. When the list is short, it becomes very easy to overlook less frequent operational scenarios.
Works as designed, performs as defined.
performance
Filter by:
Categories
-
Accessibility
-
Auditability and control
-
Availability
-
Backup
-
Business Analyst
-
Capacity, current and forecast
-
Certification
-
Compliance
-
Configuration management
-
Cost, initial and Life-cycle cost
-
Data integrity
-
Decommission & Disposition of IT Assets
-
Dependency on other parties
-
Deployment
-
Development environment
-
Disaster recovery
-
Documentation
-
Durability
-
Effectiveness
-
Efficiency
-
Emotional factors
-
Environmental protection
-
Escrow
-
Exploitability
-
Extensibility
-
Failure management
-
Fault tolerance
-
Geographical distribution (users, systems, etc.)
-
Integrability
-
Internationalization and localization
-
Interoperability
-
Legal and licensing issues or patent-infringement-avoidability
-
Maintainability (code)
-
Modifiability
-
Network topology
-
NFR
-
Open source
-
Operability
-
Operationnal environment
-
Performance and response time
-
Platform compatibility
-
Portability
-
Privacy
-
Promote
-
Quality
-
Readability
-
Reliability
-
Reporting
-
Requirements Management
-
Resilience
-
Resource constraints
-
Reusability
-
Robustness
-
Scalability (horizontal, vertical)
-
Security
-
Stability
-
Supportability
-
Testability
-
Throughput
-
Traceability
-
Transparency
-
Usability
-
Volume
Whether you’re refining an architecture, evaluating trade-offs, or bridging the gap between user expectations and technical constraints, Beyond Functional serves as your guide to mastering the subtle but crucial elements that define software excellence.
