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.
Dori is absolutely correct that task based development is instructional.
The best way to train someone on any software application is to base the
development on a process that the student must complete, not a task. The
reason for that is that a process may contain multiple tasks, so to
provide the learner with the level of knowledge transfer necessary for
him/her to accomplish a specific learning objective (goal), you must
start with that specific process.
Using MS Word as an example, one process is creating a new document.
That has multiple tasks, depending on the depth of knowledge you provide
the learner. The first task is to access the menu to create the blank
page. That task has several steps, to include using a template if that
is required. The second task is to set the page margins and its
requisite steps. The third task is to verify and modify the styles and
so on and so forth.
Process/task based development has nothing to do with "importance," but
everything to do with logic and the process flow of the process/task you
are documenting.
Just my 3 cents worth (adjusted for inflation ;^} )
David B. Dubin
Senior Curriculum Developer
Sage Software
727-579-1111 x 3356
david -dot- dubin -at- sage -dot- com
Your business in mind.
-----Original Message-----
From: techwr-l-bounces+david -dot- dubin=sage -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+david -dot- dubin=sage -dot- com -at- lists -dot- techwr-l -dot- com] On
Behalf Of Dori Green
Sent: Friday, January 19, 2007 12:25 PM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RE: Approach for user manual
As far as I have understood, a task-based approach is more suitable for
applications like Microsoft Word, where the tasks the user has to do can
be described in their order of decreasing importance. On the other hand,
a screen-based approach would be more suitable for web applications,
where the user goes from one screen to the next in a logical sequence.
**************
No, you are not getting it. The output application has nothing to do
with the difference between "task based" and "screen based".
Based on tasks -- instruction -- how to accomplish a specific outcome
(for instance, enter a customer order). Muy importante in a User's
Guide.
Based on screens -- reference -- screens used (mine are usually listed
in alphabetical order by unique title). Most likely found in a System
Specifications document.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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! http://www.webworks.com/techwr-l
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-
