Because many NFRs can actually be refined into functional requirements, many people prefer to call them “quality” requirements, “ilities”, or even
“systemic” requirements. Often NFRs can not be directly implemented as stand-alone functions, but are realized through the careful implementation of other requirements on which they depend.