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.
Re: Documentation Correctness was Re: How many levels of indents and heads are reasonable?
Subject:Re: Documentation Correctness was Re: How many levels of indents and heads are reasonable? From:John Posada <jposada01 -at- yahoo -dot- com> To:Richard Lewis <tech44writer -at- yahoo -dot- com> Date:Thu, 18 Oct 2007 17:29:33 -0700 (PDT)
--- Richard Lewis <tech44writer -at- yahoo -dot- com> wrote:
> For task/functional analysis, only the activity diagram and use
> cases come into play. Data and state modeling is something else.
> The key interrelationships, as far as task analysis is concerned,
> are data flows - not any other interrelationship other than data
> flows. Neither use cases nor activity diagrams capture data flows.
<sigh> You made the statement that nothing besides DFDs "rigorously
identifying the interrelationships between tasks".
I identify a very broad methodology that does. That's all I
did...refute your statement. So, instead of say "Ya'know...you're
right.", you immediately go off on a tangent that was never part of
your statement by identifying what you believe to be a "tragic flaw
of UML.
The validity of UML was never under discussion, but then you can
never be right when you keep moving the point being questioned. You
are wrong with the statement that nothing in UML focuses on the flow
of data. UML is about flow of data...flow of data through time, flow
of data through events, flow of data through rules, through
conditions. However, you don't justify your position
> That is because use cases and activity diagrams derail the
> task/function discovery process.
You know that Use cases and Activity diagrams leave 11 other ways
that UML shows data flow, right?
John Posada
Senior Technical Writer
"They say everyone needs goals. Mine is to live forever.
So far, so good."
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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-