Hi Ilja,
Originally posted by Ilja Preuss:
How does waterfall substitute for the ongoing customer involvement???
Although, I am not advocating what the author had to say, I probably feel that the ongoing customer requirement/changes does not play a role in waterfall methodology which is unlike the RAD methodology.So in the case of RAD, you need to have active customer involvement which is not required in Waterfall process.
Originally posted by Ilja Preuss:
So you can't show the customer that the batch system is doing what she expects it to do?
I agree with you.I donot think if you have lot of batch processing you should shift from RAD to Waterfall process.May be the author again puts its from client involvement perspective.Since Batch processing is one time design spec (the changes ofcourse could be handled by change requests which the author proposes!), one may not require as much client involvement as you would normally do while designing applications with RAD.
May be he wants to say why do you want to show the customer what you are doing while designing batch systems?Why not show him after the whole design/construct process is over- after all it doesnot require user interaction!
In any case, I have mailed him for requesting further information on the same.
Thank you for your views,
Sandeep
[This message has been edited by Desai Sandeep (edited December 11, 2001).]