On 9/4/07, Dan Scott <[EMAIL PROTECTED]> wrote: > Yes, lightweight, agile, blah blah... but if you're staring at code > without knowing what people want from the system, it seems that it > could be pretty frustrating. If you don't think that the problem > scenarios will be helpful in understanding the problem domain, it's > easy for me _not_ to write them :)
They are actually extremely helpful in understanding the problem domain, dbs++ If we had a similar story for other stakeholders (BC, etc?) I think we'd be well situated to create a use case for ordering monographs in Woodchip. //Ed
