Of the target service, the functional and non-functional requirements, including security requirements, and other service-related terms and conditions of the tender in the Annexes.
What does NFR stand for?
NFR stands for Non-Functional Requirement
This definition appears frequently and is found in the following Acronym Finder categories:
- Information technology (IT) and computers
- Military and Government
- Science, medicine, engineering, etc.
See other definitions of NFR
We have 56 other meanings of NFR in our Acronym Attic
- Near-Far Resistance
- Near-Field Recording
- Nearly Faithful Reproduction
- Need for Recovery (work survey)
- Net Financing Requirement (various locations)
- Network Flight Recorder
- New Feature Request
- No Further Record
- No Further Requirement
- No Further Resuscitation (see DNR)
- Northern Freegold Resources (Canada)
- Not Flag Related (meaning off-topic in Flags of the World mailing list and website)
- Not for Release
- Not for Reproduction
- Not for Resale
- Not for Resuscitation (see DNR)
- Note for the Record (various organizations)
- Notice of Final Rulemaking
- Notice of Findings and Recommendations
- Nucleosome Free Region
Samples in periodicals archive:
Conducting an agile requirements workshop, defining an iteration and writing non-functional requirements are practiced in detail.
It can be observed that non-functional requirements (NFR) are often referred to as soft criteria and exclusively considered for ranking .
Introduction The role of satisfying of non-functional requirements is at least important as it is for functional requirements.
The research in testing of functional requirements is well developed but the testing of non-functional requirements is still in the beginning.
The literature on the subject has been following the path taken by object oriented software development, and there have been several proposals as to adapt object-oriented models and specification languages to deal with the new non-functional requirements imposed by agent-oriented software.
Address System Qualities and Non-Functional Requirements Early The heady rush to provide new and innovative functionality to the warfighter can cause acquisition and development teams to overlook non-functional requirements and system qualities.
In most RUP projects functional requirements are documented using Use Case analysis whilst non-functional requirements (usability, reliability, performance and supportability) are documented separately in an artefact called the Supplementary Specification.