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.
Subject:RE: Xtreme Documentation and Training From:"Michael West" <mike -dot- west -at- oz -dot- quest -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 14 Feb 2001 11:53:44 +1100
M. David Orr writes:
> I'm interested in how my fellow techwhirlers have adapted document
> development and training development practices to changing software
> development processes, including extreme programming.
I work with several software development teams,
most of which have adapted at least some elements
of UML methodology.
I find that the "use case" scenarios and diagrams
associated with UML, which as planning and scoping
documents essentially replace the old, paper-intensive
sequence of Requirements and Functional Specifications,
serve us tech writers very well in designing user
assistance material.
Tech writers like use-case diagrams because they
focus on the interaction between the user and the
software. They depict in a very concise and clear way
the "what and the why" of software functionality. Armed
with this information, the tech writer can design a task-
based user-assistance package before the first line of
code is written.
Developers like use-case diagrams because they require
very little actual "writing" on their part (and their aversion
to writing clearly and concisely was part of the reason why
the functional and technical specs of the bad old days were
fairly useless most of the time).
Another benefit (as I see it) of the new, streamlined methods
is that tech writers can generally spend less of their time in
fruitless paper-chasing tasks. That means more time discussing
or even participating in the development of the product itself
rather than mile-high stacks of specification documents that say
very little.
--
Michael West
Melbourne
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-Based Help with Macromedia Dreamweaver 4 ($100 STC Discount)
**WEST COAST LOCATIONS** San Jose (Mar 1-2), San Francisco (Apr 16-17) http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.
Sponsored by ForeFront, Inc., maker of ForeHelp Help authoring tools
for print, WinHelp, HTML Help, JavaHelp, and cross-platform InterHelp
See www.forehelp.com for more information and free evaluation downloads
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.