3 ms·
hmm -- confusing to use 'requirements' for software behavior required by users as well as dependency behavior required by the software. Is the author just sayin
by awinter-py 10y ago
hmm -- confusing to use 'requirements' for software behavior required by users as well as dependency behavior required by the software. Is the author just saying we should have a spec for software? Ok but that's a different blog post.
- ozten 10y agoThe usage of the term 'requirements' is traditional in the software development industry. It may be unusual for many teams, but it is common in the literature as well as larger, older organizations.
- tyingq 10y agoConfusing to me as well. Generically, he's saying that "non functional" requirements should be documented at least as well as "functional" requirements. But then his example isn't really a "non functional requirement". The example is basically saying that implementation details/choices that might have an impact should be documented. An example of an actual non-functional requirement would be some specific, defined, metric for privacy, performance, etc. ( vs an implementation choice...blocking vs non-blocking, method creates a new object under the covers, etc)