TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
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
> I think what the author (Scott Ambler) meant to say
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 http://search.yahoo.com