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.
> Anyone written CBT's? I may be doing just the informational part (not the
> programming), based on existing info (for the application) and models (for
> the CBT format).
This is my first response to this list, so please bear with me as I
my way through.
Concerning CBT's: I've done both authoring and content, so I present my
> Is this as straightforward as it seems, or are there dragons behind those
>>Plan, plan, plan. And then plan some more.
I could not agree more! And even after planning, there is always
I used Allen Communications Quest for my CBT. It was created for a
audience - user's of our software package.
You need to know your audience. We needed to create a CBT that would
allow new users a linear progression through each lesson and then build
that information for the next lesson. We tested their knowledge at the
each lesson an allowed review of the information just learned as well as
review of previous lessons. The trick was to structure the first
of the lesson, not allowing any deviation, and then allow the student to
quickly review the information either before or after the test. This
users who hadn't used the system in a long time to go through a quick
Keep it simple. I came up with a great idea (at least I thought so) for
information in a clever manner. When I got to the authoring portion, it
complicated to execute properly. I had to scale it back.
Glossary. We found that putting definitions in a glossary cut down on
amount of text on a screen. Users could always click on a glossary
get the info they needed (or you could hot-spot terms).
>>3. Are you going to test? If so, how? When? And will your authoring
system support it?
Quest supports tests for a user (multiple choice, typed in answers with
match). It also allows scores to be output to a OLE database. This is
the reason we chose Quest over other packages.
>>4. Is the learner familiar with the computer environment?
Our experience is you never know who is going to run the CBT. Put a
Started" in the CBT. A paper-based version does not always go with the
Rick Rogers rogers_r -at- bsiwizard -dot- com