Jon, I think you should re-read what constitutes a functional requirements document. What James is writing is certainly *not* such a beast. It is simply documenting how his proposal works. Closer to a design document.
James has already stated that he doesn't want to waste time with a requirements document. jim ----- Original Message ----- From: "Jon Stevens" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, January 15, 2001 4:57 PM Subject: Re: Functional Requirements Document > on 1/15/01 1:52 PM, "Siberski, Wolf" <[EMAIL PROTECTED]> wrote: > > > I'm not sure if writing such a document > > is really the right approach, but > > it can't hurt to try it... > > > > Wolf > > It is actually the perfect approach. Thanks for doing it. Have you seen > James Davidson's start on such a document? Maybe you can work with him on > improving his document. > > -jon > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
