The gap between business and code
I wrote a paper for PNSQC 2005 that I seem to never have put on line. Here’s the abstract:
This paper argues that the continuing problems we have with requirements elicitation and transmission are not a result of poor skills or sloppy people. It’s rather that the entire idea is based on dubious assumptions. A different assumption is introduced, namely that effectiveness can only be obtained by parties having iterative conversations over time, and that communication is meant more to provoke right action than to transmit understanding. Based on examples of this assumption in practice, suggestions for software development are sketched.
November 29th, 2007 at 8:52 am
Examples may, in fact, trigger something in one’s head. Thank you for putting this paper on line, it makes some very interesting points and it has useful references.