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.
DFD as TA, was Re: Getting up to speed on UML (Was: Re: Documentation Correctness...)
Subject:DFD as TA, was Re: Getting up to speed on UML (Was: Re: Documentation Correctness...) From:Ned Bedinger <doc -at- edwordsmith -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Wed, 24 Oct 2007 14:58:39 -0700
Sorry about busting in on Stuart's UML query, but this appearance of the
DFD hydra reminded me of something last week that I thought was
important, but was too busy to post last week.
Richard Lewis wrote:
> Bottom Line: Data Flow Diagrams = Task Analysis.
Thankfully, Steve Jong took the time to put Data Flow and Task Analysis
into parallel perspective for us last week (see 10/17/2007, from
stevefjong -at- comcast -dot- net, "Re: Documentation Correctness was Re: How many
levels of indents and heads are reasonable?").
I believe that, with his thinkable example, Jong completed the
intractable "Bottom Line" thought from alias Richard Lewis.
IMHO, we can all now be free to believe that Data Flow Analysis has a
place in Task Analysis, and even that task Analysis is not complete
without Data Flow Analysis. But still, a major concern comes with the
claim that the DFD is sufficient for any task analysis, and that is that
we cannot count on our being able to infer all actor steps from the data
flow. The inevitable conclusion is that a DFD would not suffice for all
Task Analysis.
Many thanks to stevefjong for tackling the need for an example to help
us think about this. And to alias richard lewis for surviving and
sharing his/her discovery of data flow diagrams with us--I think you
must be like this:
If you want to build a ship
don't herd people together to collect wood
and don't assign them tasks and work,
but rather teach them to long for the
endless immensity of the sea.
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-