Non-Functional Requirement
A Non-Functional Requirement is a system requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors.
- …
- Counter-Example(s):
- See: Software Testability, Systems Engineering, Requirements Engineering, Requirement, Functional Requirement, Systems Design, Systems Architecture, Architecturally Significant Requirements, Function (Mathematics), Black Box, Functional Model, IPO Model.
References
2018
- (Wikipedia, 2018) ⇒ https://en.wikipedia.org/wiki/Non-functional_requirement Retrieved:2018-3-5.
- 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 behaviors. 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.
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 <requirement>", 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 <requirement>", 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 “quality attributes” of a system. Other terms for non-functional requirements are "qualities", "quality goals", "quality of service requirements", "constraints" and "non-behavioral requirements". 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.
- 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 behaviors. 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.