Timeline for Functional or non-functional requirement?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 25, 2017 at 14:35 | comment | added | fr_andres | +1! regarding subjectivity of non-functional requirements, it may be enough to point out that those are in the core of the very solid RESTful architecture en.wikipedia.org/wiki/… | |
| Oct 15, 2013 at 20:28 | review | Suggested edits | |||
| Oct 15, 2013 at 20:30 | |||||
| Jun 16, 2013 at 15:31 | comment | added | Aaronaught | @AramKocharyan: That's not a functional requirement. Clearly there's a customer SLA hiding in there somewhere, and that is the functional requirement. "Contact updates must be processed within 60 minutes to support timely customer service/marketing" - that is an internal, functional requirement. "Index the database of users" is not a requirement at all, it's an implementation; for example, another way to meet said SLA could be to use realtime background indexing, or to eliminate the need for indexing entirely by using a service broker or bus and processing updates in near-realtime. | |
| Jun 16, 2013 at 5:25 | comment | added | Aram Kocharyan | Nice! What thing I'd add is that functional requirements need not deal only with interactions with the external environment however (a related concept are "interface requirements" with other systems). A counterexample for this would be "The system must index the database of users every 60 minutes". This is clearly internal. | |
| Nov 8, 2011 at 9:21 | vote | accept | Piotr Müller | ||
| Nov 8, 2011 at 2:52 | history | edited | Aaronaught | CC BY-SA 3.0 |
added 1138 characters in body
|
| Nov 8, 2011 at 2:45 | history | answered | Aaronaught | CC BY-SA 3.0 |