moore at cs.utk.edu
Tue Feb 4 10:12:22 CET 2003
> if someone were to volunteer to write an "IETF's guide to writing a
> requirements document", with pointers to particularly good examples of
> processes that worked well or badly, we actually might manage to identify
> the useful tool and forget the time-wasting rathole.....
I'd be willing to write (or help write) a "guide to writing a problem statement".
I agree with Brian that changing the name from "reqiurements document" to
"problem statement" is not sufficient by itself, but I think a name change is
necessary to get people out of the rut that seems to be widespread.
More information about the Problem-statement