Differences

This shows you the differences between two versions of the page.

@@ Line 1: / Line 1: @@
+====== Non-functional requirement (NFR) ======
+A non-functional requirement (NFR) is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviours.
+They are contrasted with functional requirements that define specific behaviour or functions
+<callout type='primary' title='What is NFR?' icon='fa fa-question-circle'>
+Non-functional requirements are the qualities or characteristics of a software system that define its overall behavior, but do not relate to specific functions or features. These requirements describe how the system performs, rather than what it does. Non-functional requirements can be grouped into various categories such as:
+  * **Performance**: This category deals with the response time, throughput, and resource utilization of the system. Examples include system availability, response time, scalability, and reliability.
+  * **Usability**: This category deals with how easy and intuitive the system is to use. Examples include accessibility, user interface design, and user experience.
+  * **Security**: This category deals with the protection of the system and its data from unauthorized access, modification, or destruction. Examples include data privacy, authentication, and authorization.
+  * **Maintainability**: This category deals with how easy it is to maintain and modify the system over time. Examples include code maintainability, extensibility, and testability.
+  * **Compatibility**: This category deals with how well the system can integrate with other systems, software, and hardware. Examples include platform compatibility and data format compatibility.
+  * **Legal and Regulatory**: This category deals with the legal and regulatory requirements that the system must comply with. Examples include data protection regulations and software licensing requirements.
+Non-functional requirements are essential to ensure that the software system meets the desired level of performance, usability, security, and maintainability, among other factors. They are often overlooked in the requirements gathering process, but neglecting them can lead to significant problems in the functionality and performance of the system.
+</callout>
+{{wp>Non-functional_requirement}}
+<file text Taxonomy of Non-functional requirements (NFRs).txt>
+Accessibility
+Adaptability
+Auditability and control
+Availability
+Backup
+Capacity
+Certification
+Compliance
+Cost
+Data integrity
+Data retention
+Dependency
+Deployment
+Development environment
+Disaster recovery
+Documentation
+Durability
+Effectiveness
+Efficiency
+Emotional factors
+Environmental
+Environmental protection
+Escrow
+Exploitability
+Extensibility
+Failure management
+Fault tolerance
+Integrability
+Internationalization
+Interoperability
+Legal
+Licensing
+Life-cycle cost
+Localization
+Maintainability
+Manageability
+Management
+Modifiability
+Network topology
+Open source
+Operability
+Patent-infringement
+Performance
+Platform compatibility
+Portability
+Privacy
+Quality
+Readability
+Recoverability
+Regulatory
+Reliability
+Reporting
+Resilience
+Resource constraints
+Response time
+Reusability
+Robustness
+Safety
+Scalability
+Security
+Serviceability
+Software
+Stability
+Supportability
+Testability
+Throughput
+Transparency
+Usability
+Volume
+</file>
+<callout title="External links:">
+  * https://www.scaledagileframework.com/nonfunctional-requirements/
+  * https://www.guru99.com/non-functional-requirement-type-example.html
+  * https://www.guru99.com/functional-vs-non-functional-requirements.html
+  * https://reqtest.com/requirements-blog/what-are-non-functional-requirements/
+  * http://users.csc.calpoly.edu/~jdalbey/SWE/QA/nonfunctional.html
+</callout>
+{{tag>kb acronym architecture   projects taxonomy  devopsplan list     }}