RE: IT documentation

Subject: RE: IT documentation
From: "Goldstein, Dan" <DGoldstein -at- DeusTech -dot- com>
To: "TECHWR-L (E-mail)" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 3 Mar 2004 14:53:26 -0500

I'm not convinced. He also wrote, "Design decisions are often documented
throughout other artifacts, such as system overviews and source code,
although you may choose to have a separate document when appropriate to the
situation." Sounds like his after-the-fact system overview is *instead of* a
pre-development requirements spec.

Dan Goldstein

> -----Original Message-----
> From: k k
> Sent: Wednesday, March 03, 2004 2:32 PM
> Subject: RE: IT documentation
> I think the man wrote exactly what he meant. It makes
> sense if the overview isn't a design document. If it's
> just an executive summary type of document, or
> something else meant to give a customer peace of mind,
> then you're better off waiting to do the doc until the
> design is fairly stable. That way the reader doesn't
> see any big differences between what it says in the
> overview and what he actually sees in the product.

Previous by Author: RE: IT documentation
Next by Author: RE: IT documentation
Previous by Thread: Re: IT documentation
Next by Thread: RE: IT documentation

What this post helpful? Share it with friends and colleagues:

Sponsored Ads