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.
The model becomes the software, the model becomes the docs?
Subject:The model becomes the software, the model becomes the docs? From:Geoff Hart <ghart -at- videotron -dot- ca> To:techwr-l List <techwr-l -at- lists -dot- techwr-l -dot- com>, Ned Bedinger <doc -at- edwordsmith -dot- com> Date:Mon, 29 Oct 2007 17:21:46 -0400
Ned Bedinger wonders: <<... if the model becomes the software,
couldn't it become the documentation too?>>
Nope. A model explains how something is implemented; documentation
translates the model into an explanation of how that implementation
is used. The two are clearly related, but not as strongly as we might
hope. User models come close, but rely on the assumption that
software design starts with how users work and builds a support
architecture around that. This seems to be about as common as
American $2 bills these days. That is, they exist, and they're legal,
but you have to look quite hard to find them out in the real world.
<<Anyway, as tech writer, I think I could work with 90% less SME time
required if I had a self-documenting model to work from.>>
In theory, yes; in practice, probably not. If SMEs were great
writers, they'd probably be writing instead of developing products.
Some of them are good writers, but they're the minority. More
importantly, developers need to spend 90% of their time developing
and debugging products; that leaves only 10% of their time for
documenting. (Play with the numbers how you will. They're supplied
only for dramatic purposes.) Plus, if you've ever been "in the flow"
while writing, you know what it's like when a developer gets all flow-
ey with coding or design: the last thing on their mind is documenting
what they're doing.
----------------------------------------------------
-- Geoff Hart
ghart -at- videotron -dot- ca / geoffhart -at- mac -dot- com
www.geoff-hart.com
--------------------------------------------------
***Now available*** _Effective onscreen editing_
(http://www.geoff-hart.com/home/onscreen-book.htm)
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-