Timeline for What is a Non-Functional Requirement?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 3, 2013 at 13:10 | vote | accept | atconway | ||
| Jul 3, 2013 at 9:58 | comment | added | James Anderson | Plus: adhere to a particular set of standards, use of a particular API/protocol, conform to a set of visual guidelines, minimum hardware/software to be supported, support of minimum maximum screen size, consume less than nK memory, etc. etc. are all non-functional requirements I have seen. | |
| Jul 3, 2013 at 6:46 | comment | added | Bart van Ingen Schenau | @RobertHarvey: Basically, yes, non-functional == not observable to the user. And page load time is then indeed a functional requirement, because an observant user will be able to observe that. | |
| Jul 2, 2013 at 23:35 | comment | added | Robert Harvey | So basically anything that the end user can't see is a non-functional requirement. I'm beginning to see that breaking down requirements by "functional" and "non-functional" categories could cause more harm than good; if all pages have to load in 2 seconds, that's a requirement, really. | |
| Jul 2, 2013 at 22:26 | history | answered | Julius | CC BY-SA 3.0 |