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.
I often refer to data flow diagrams in my postings as they are so applicable in so many facets of TWing: task analysis, documentation structuring (i.e., organizing), estimating, risk analysis, project scoping, reverse engineering, standardization of terms, and proper grammar use.
Structured writing is the main skill set of a TW. Structured writing is really all about analysis, that is coming up with a properly structured understanding of the product and then letting that understanding guide the writing process. And what could be more appropriate to a structured analysis than structured analysis (i.e., data flow diagrams).
Genric Richard
"Hickling, Lisa (TOR)" <lhickling -at- Express-Scripts -dot- com> wrote:
Sir, I did not accuse you. Post as you see fit, as often as you see fit.
My only wonder is that others are so easily drawn in by the fighting
words "Richard|Tony" + "DFD".
Richard, the tone and content of your posts on the subject of DFDs tend
to be predictable. Whether this is your intention or not is debatable.
The focus of my post, however, was the volume and nature of everyone
else's response. Whether you intend it or not, respondents are baited to
an equally predictable counter response in an effort to refute your
claims. The result is 2 or 3 threads a month with the same thesis and
antithesis.
Nevertheless, you have every conceivable right to broadcast and
rebroadcast your opinions. In fact, I rather look forward to more of
your posts, only on other subjects, for example, on the perils of being
one-dimensional in technical communications.
Lisa Hickling
Greater Toronto Area, Ontario
-----Original Message-----
From: techwr-l-bounces+lhickling=express-scripts -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+lhickling=express-scripts -dot- com -at- lists -dot- techwr-l -dot- co
m] On Behalf Of Richard Lewis
Sent: Thursday, October 18, 2007 2:20 PM
To: Bill Swallow
Cc: TECHWR-L
Subject: Data Flow Diagrams
What I thought Lisa H (forgot her last name something like Hickling)
said yesterday (and actually numerous others had said (I do not keep
these old e-mails)) is that I invoke discussion of data flow diagrams by
"baiting". Next time Lisa posts, I will ask her.
I do not know what baiting is. What I do is, if data flow diagrams
offer a solution, I bring them up. There is nothing wrong with that.
Generic Richard
Bill Swallow wrote:
It's not the content but the delivery. Many people have indicated this
to you before.
DFD = good
Please reconsider the tone and tact you use when responding to or
posting new threads, and try to supply actionable or useful
information, not just "this is why I use DFDs". And please refrain
from comments around "no one is doing documentation correctly",
because in a forum of technical writers, all those reading your posts
are the "everyone" you speak of. It doesn't go over well... kind of
like calling your mother in law a "fat pig" to her face.
On 10/18/07, Richard Lewis wrote:
> Hi all:
>
> A question on listserv protocol: In answering listserv questions, my
answer often revolves around data flow diagrams. (This often invokes a
condeming responses.) Am I "baiting"?
>
> Thanks,
>
> Generic Richard
--
Bill Swallow
HATT List Owner
WWP-Users List Owner
Senior Member STC, TechValley Chapter
STC Single-Sourcing SIG Manager http://techcommdood.blogspot.com
******* Confidentiality Notice *******
ESI Canada -- Optimizing the value of health benefits
This email, its electronic document attachments, and the contents of its website linkages may contain confidential health information. This information is intended solely for use by the individual or entity to whom it is addressed. If you have received this information in error, please notify the sender immediately and arrange for the prompt destruction of the material and any accompanying attachments.
******* Avis de confidentialite *******
ESI Canada -- Optimiser la valeur des regimes de soins de sante
Ce courriel ainsi que tout document y etant joint de meme que le contenu des liens vers des sites Web peuvent reunir des renseignements confidentiels sur la sante. Cette information s'adresse uniquement a l'usager ou a l'organisation auxquels elle est destinee. Si vous avez recu ce message par erreur, veuillez en aviser l'expediteur immediatement et proceder a la suppression du document et des fichiers joints sans tarder.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
