Non-functional requirement
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. Non-functional requirements are also known as cross-functional requirements by some.
From Wikipedia, the free encyclopedia 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]…
saved by
related reading
- Functional and Non Functional Requirements - GeeksforGeeksgeeksforgeeks.org
- Clean Coder Blogblog.cleancoder.com
- System Design Delivery Framework | Hello Interview System Design in a Hurryhellointerview.com
- NYSRGnotes.ekzhang.com
- Writing a good design documentnews.ycombinator.com
- You Have to Feel Itmitchellh.com
- What Makes a (Graphics) Systems Paper Beautifulgraphics.stanford.edu
- The two types of quality // Zeno Rochazenorocha.com
- Functional near-infrared spectroscopy - Wikipediaen.wikipedia.org
- FRAM in a nutshell – PAN-EUROPEAN TRAINING, RESEARCH AND EDUCATION NETWORK ON ELECTROMAGNETIC RISK MANAGEMENTetn-peter.eu
- The purpose of a system is what it does - Wikipediaen.wikipedia.org
- Yagnimartinfowler.com