Definitions[]
A non-functional requirement
| “ | specifies a particular quality of the system rather than a function of the system. Two kinds of non-functional requirements are typically distinguished: 1. Execution qualities observable at run-time such as security, availability, reliability, etc.; 2. Evolution qualities observable at design time such as scalability and extensibility.[1] | ” |
| “ | specif[ies] criteria useful to evaluate the qualities, goals or operations of a system, rather than specific behaviors or functions of a system.[2] | ” |
| “ | is a statement that specifies a constraint about how a system must behave to meet functional requirements.[3] | ” |
References[]
- ↑ SOA4All, Glossary (full-text).
- ↑ Framework for Cyber-Physical Systems, at 14.
- ↑ NIST Framework and Roadmap for Smart Grid Interoperability Standards, Release 2.0, at 22.