Non-functional requirement explained
In systems engineering and requirements engineering, 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 behavior or functions. The plan for implementing functional requirements is detailed in the system design. The plan for implementing non-functional requirements is detailed in the system architecture, because they are usually architecturally significant requirements.[1]
In software architecture, non-functional requirements are known as "architectural characteristics". Note that synchronous communication between software architectural components, entangles them and they must share the same architectural characteristics.[2]
Definition
Broadly, functional requirements define what a system is supposed to do and non-functional requirements define how a system is supposed to be. Functional requirements are usually in the form of "system shall do ", an individual action or part of the system, perhaps explicitly in the sense of a mathematical function, a black box description input, output, process and control functional model or IPO Model. In contrast, non-functional requirements are in the form of "system shall be ", an overall property of the system as a whole or of a particular aspect and not a specific function. The system's overall properties commonly mark the difference between whether the development project has succeeded or failed.
Non-functional requirements are often called the "quality attributes" of a system. Other terms for non-functional requirements are "qualities", "quality goals", "quality of service requirements", "constraints", "non-behavioral requirements",[3] or "technical requirements".[4] Informally these are sometimes called the "ilities", from attributes like stability and portability. Qualities—that is non-functional requirements—can be divided into two main categories:
- Execution qualities, such as safety, security and usability, which are observable during operation (at run time).
- Evolution qualities, such as testability, maintainability, extensibility and scalability, which are embodied in the static structure of the system.[5] [6]
It is important to specify non-functional requirements in a specific and measurable way.[7] [8]
Examples
A system may be required to present the user with a display of the number of records in a database. This is a functional requirement. How current this number needs to be, is a non-functional requirement. If the number needs to be updated in real time, the system architects must ensure that the system is capable of displaying the record count within an acceptably short interval of the number of records changing.
Sufficient network bandwidth may be a non-functional requirement of a system. Other examples include:
- Accessibility
- Adaptability
- Auditability and control
- Availability (see service level agreement)
- Backup
- Boot up time
- Capacity, current and forecast
- Certification
- Compliance
- Configuration management
- Conformance
- Cost, initial and Life-cycle cost
- Data integrity
- Data retention
- Dependency on other parties
- Deployment
- Development environment
- Disaster recovery
- Documentation
- Durability
- Efficiency (resource consumption for given load)
- Effectiveness (resulting performance in relation to effort)
- Elasticity
- Emotional factors (like fun or absorbing or has "Wow! Factor")
- Environmental protection
- Escrow
- Exploitability
- Extensibility (adding features, and carry-forward of customizations at next major version upgrade)
- Failure management
- Fault tolerance (e.g. Operational System Monitoring, Measuring, and Management)
- Flexibility (e.g. to deal with future changes in requirements)
- Footprint reduction - reduce the exe files size
- Integrability (e.g. ability to integrate components)
- Internationalization and localization
- Interoperability
- Legal and licensing issues or patent-infringement-avoidability
- Maintainability (e.g. mean time to repair – MTTR)
- Management
- Memory Optimization
- Modifiability
- Network topology
- Open source
- Operability
- Performance / response time (performance engineering)
- Platform compatibility
- Privacy (compliance to privacy laws)
- Portability
- Quality (e.g. faults discovered, faults delivered, fault removal efficacy)
- Reporting
- Resilience
- Resource constraints (processor speed, memory, disk space, network bandwidth, etc.)
- Response time
- Reusability
- Robustness
- Safety or factor of safety
- Scalability (horizontal, vertical)
- Security (cyber and physical)
- Software, tools, standards etc. Compatibility
- Stability
- Supportability
- Testability
- Throughput
- Transparency
- Usability (human factors) by target user community
- Volume testing
See also
2011
External links
Notes and References
- 10.1109/MS.2012.174. Characterizing Architecturally Significant Requirements. IEEE Software. 30. 2. 38–45. 2013. Chen. Lianping. Ali Babar. Muhammad. Nuseibeh. Bashar. 10344/3061. 17399565 . free.
- Book: Fundamentals of Software Architecture: An Engineering Approach . 2020 . 978-1492043454.
- Book: Stellman . Andrew . Greene . Jennifer . Applied Software Project Management . 113 . . 2005 . 978-0-596-00948-9 . dead . https://web.archive.org/web/20150209011617/http://www.stellman-greene.com/aspm/ . 2015-02-09 .
- Web site: Ambler . Scott . Technical (Non-Functional) Requirements: An Agile Introduction . Agile Modelling . Ambysoft Inc. . 5 October 2018.
- Book: Wiegers. Karl. Beatty. Joy. Software Requirements, Third Edition. 2013. Microsoft Press. 978-0-7356-7966-5.
- Book: Young . Ralph R. . Effective Requirements Practices . 2001 . Addison-Wesley . 978-0-201-70912-4 . registration .
- Book: Zimmermann. Olaf . Stocker. Mirko. Design Practice Repository . 2021 . LeanPub .
- 10.1109/MS.2008.31. A Risk-Based, Value-Oriented Approach to Quality Requirements. IEEE Software. 25. 2. 34–41. 2008. Glinz. Martin. 19015424 .
