You mean that's not the norm? :) Requirements docs are like bigfoot. You are assured it exists but when you see it, you are disappointed to find it is little more than "just do it". Plus its wearing a digital watch.
David "If we can hit that bullseye, the rest of the dominoes will fall like a house of cards... checkmate!" -Zapp Brannigan, Futurama On Fri, Feb 26, 2010 at 09:56, Jonathan Parker <[email protected]> wrote: > The problem with using emails as requirements documents... > Q: Where are the requirements for the cruise control software? > A: I'll forward you the email trail of the discussions I had with Toyota. > a year or so goes by > Q: Don't you know the cruise control should disengage when you brake? > A: Sorry I didn't read that part of the email. > On Fri, Feb 26, 2010 at 9:35 AM, Arjang Assadi <[email protected]> > wrote: >> >> People don't read more than the first 2 lines of emails. For example I >> stopped reading after "I'll generalise" :) >> >> Regards >> >> Arjang >>
