Comments on: Abstraction And “Requirements” http://tynerblain.com/blog/2006/11/29/abstraction-and-requirements/ Software product success. Tue, 22 May 2012 20:46:27 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Scott Sehlhorst http://tynerblain.com/blog/2006/11/29/abstraction-and-requirements/comment-page-1/#comment-57562 Scott Sehlhorst Thu, 30 Nov 2006 17:42:09 +0000 http://tynerblain.com/blog/2006/11/29/abstraction-and-requirements/#comment-57562 Thanks Roger! If there are other folks that would like to chime in, I think the conversation will be much more valuable to everyone. I won't have a chance to reply for a little while. Anyone? Bueller?... Thanks Roger!

If there are other folks that would like to chime in, I think the conversation will be much more valuable to everyone. I won’t have a chance to reply for a little while.

Anyone? Bueller?…

]]> By: Roger L. Cauvin http://tynerblain.com/blog/2006/11/29/abstraction-and-requirements/comment-page-1/#comment-57561 Roger L. Cauvin Thu, 30 Nov 2006 15:52:35 +0000 http://tynerblain.com/blog/2006/11/29/abstraction-and-requirements/#comment-57561 Thanks for the reply. Perhaps we can continue this discussion offline if you think we're boring or annoying your readers :-) Four things: 1. Usage of requirements terminology is <i>not</i> established, it is confused and inconsistent. If you asked a hundred product managers to define "market requirement" and "product requirement", you'd get dozens of significantly different responses. 2. There is little doubt that there is a crisis in requirements. I think you're too dismissive of the possibility that the crisis is due in part to the terminological confusion (though I believe the cause and effect works both ways). 3. I have never questioned the coherenece, validity, or usefulness of the distinction between functional and nonfunctional requirements. 4. I still am curious how you reconcile some of your examples with your contention that product requirements are neither functional nor nonfunctional. On the face of it, there seems to be a fundamental inconsistency. Thanks for the reply. Perhaps we can continue this discussion offline if you think we’re boring or annoying your readers :-)

Four things:

1. Usage of requirements terminology is not established, it is confused and inconsistent. If you asked a hundred product managers to define “market requirement” and “product requirement”, you’d get dozens of significantly different responses.

2. There is little doubt that there is a crisis in requirements. I think you’re too dismissive of the possibility that the crisis is due in part to the terminological confusion (though I believe the cause and effect works both ways).

3. I have never questioned the coherenece, validity, or usefulness of the distinction between functional and nonfunctional requirements.

4. I still am curious how you reconcile some of your examples with your contention that product requirements are neither functional nor nonfunctional. On the face of it, there seems to be a fundamental inconsistency.

]]>