RE: Modularization of Documentation

Subject: RE: Modularization of Documentation
From: "Dan Goldstein" <DGoldstein -at- riverainmedical -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Thu, 8 Jun 2006 08:43:37 -0400

Hi Tony,

Thanks for your response. So you're saying that in_the_whole_world,
there's not a single book about documentation that requires the

* Each section ("module," whatever) of documentation should describe a
specific task and be clearly labeled as such.
* Each section of printed documentation should be no more than one page
long. (What about onscreen Help? Varying page sizes?)
* Each section of documentation should have no more than five other
sections that either reference it or are referenced by it.

While I don't personally agree with all three requirements, I'll bet
*someone* has written a book that requires them.

If not, write it!



> -----Original Message-----
> From: Tony Markos
> Sent: Wednesday, June 07, 2006 7:57 PM
> To: Dan Goldstein; TECHWR-L
> Subject: RE: Modularization of Documentation
> I measure documentation module cohesiveness by:
> * Evaluating a module's label (title). Are strong
> noun/verb combo's used? Calculate Sales Tax is
> strong. Process Stuff is weak.
> * Evaluating a module's size. A module of text
> should be a page or less.
> I measure module coupling by:
> * Evaluating interface complexity between my modules.
> Using a taboo diagramming technique, I count the
> number of inputs from and outputs to other modules.
> These can be either data flows between modules or
> flows of control. There should be no more that four
> or five interfaces.

This message contains confidential information intended only for the use of the addressee(s). If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing, copying, electronic storing or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this message by mistake, please notify us, by replying to the sender, and delete the original message immediately thereafter. Thank you.


WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!.

Doc-To-Help includes a one-click RoboHelp project converter. It's that easy. Watch the demo at

You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit for more resources and info.

Previous by Author: RE: Modularization of Documentation
Next by Author: RE: Modularization of Documentation
Previous by Thread: RE: Modularization of Documentation
Next by Thread: RE: Modularization of Documentation

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

Sponsored Ads