RE: IT documentation

Subject: RE: IT documentation
From: k k <turnleftatnowhere -at- yahoo -dot- com>
To: TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 3 Mar 2004 11:32:07 -0800 (PST)

> From Ken's second link: "System overviews are best
> written towards the end
> of the development of a release because you know
> what you've actually
> built."
> I think what the author (Scott Ambler) meant to say
> was,

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.

Do you Yahoo!?
Yahoo! Search - Find what you?re looking for faster

RE: IT documentation: From: Goldstein, Dan

Previous by Author: RE: IT documentation
Next by Author: Re: The Amazing Disappearing XRefs
Previous by Thread: RE: IT documentation
Next by Thread: Re: IT documentation

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

Sponsored Ads

Sponsored Ads