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.
Keith Hood wrote:
> I think there is some reason to believe the wikipedia article needs work.
Indeed. Functional requirements often are represented by their lack.
"Don't need it. We know the design already."
Some use cases I've seen (or proposed) have been dismissed as, "That'll
never occur. Nobody'll want that."
It can be hard to establish a template for one class of applications by
looking at templates for others. The technical writer is in a good
position to be an outside voice who points out missing items. Does the
proposed software have additional uses, heretofore unimagined? Will they
later become the driving force for the redesign? Web pages were once
static, then dynamic, and now interactive in ways unanticipated back in
the days of Mosaic.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices. http://www.doctohelp.com/SuperPages/Webcasts/
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
