Re: multiple TWs for a project

Subject: Re: multiple TWs for a project
From: "Bonnie Granat" <bgranat -at- worldnet -dot- att -dot- net>
To: "Anthony Markatos" <tonymar -at- hotmail -dot- com>, "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Fri, 11 Feb 2000 02:16:42 -0500

-----Original Message-----
From: Anthony Markatos <tonymar -at- hotmail -dot- com>
To: TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Friday, February 11, 2000 12:22 AM
Subject: Re: multiple TWs for a project

>Tony Markatos said:
>In properly chunked projects, all procedure to accomplish a given task will
>be together. (The end-user will not have to jump around between different
>sections of the documentation to accomplish the task.)
>In writing a properly chunked document, the TWs will not have to do a lot
>coordinating between themselves. It is in coordinating the different
>that major disagreements occur.
>Bonnie Granat asks:
>I didn't know there were two meanings of "chunking" in technical writing.
>I've only known the meaning of chunking as breaking apart information into
>small bits, both visually and logically.
>Tony Markatos responds:
>The logical way to chunk (break into smaller pieces) procedural information
>is by task. In this way the dependencies between the chunks are minimized.

Is your use of the word common? "Chunking" in my experience is about
presentation and layout only. Rather than repeat my initial comment, please
read it again.

Bonnie Granat

Previous by Author: Re: multiple TWs for a project
Next by Author: Re: Chunking information (Was: multiple TWs for a project)
Previous by Thread: Re: Re[2]: multiple TWs for a project
Next by Thread: Re: multiple TWs for a project

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

Sponsored Ads

Sponsored Ads