gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Explained NFR in layman's terms (#33914)

Browse Source
This commit is contained in:
Tareq K
2019-01-22 20:31:10 -05:00
committed by Tom
parent 280d042248
commit 467a9257c4
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
guide/english/agile/nonfunctional-requirements/index.md
View File

@ -5,6 +5,8 @@ title: Nonfunctional Requirements
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 (a functional requirement). Non-functional requirements are often called "quality attributes", "constraints" or "non-behavioral requirements". 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 (a functional requirement). Non-functional requirements are often called "quality attributes", "constraints" or "non-behavioral requirements".
In plain English, non-functional requirements are things that 100% is needed for the code to run. For example, a requirement would be to be able to login, but whether it takes 1 second to log in or 1 hour to login, both satisfy the functional requirement. The non-functional requirement would then be that the login time should take no more than 3 seconds.
Informally, these are sometimes called the "ilities", from attributes like stability and portability. NFRs can be divided into two main categories: Informally, these are sometimes called the "ilities", from attributes like stability and portability. NFRs can be divided into two main categories:
* **Execution qualities**, such as safety, security and usability, which are observable during operation (at run time). * **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 * **Evolution qualities**, such as testability, maintainability, extensibility and scalability, which are embodied in the static structure of the system