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.
>I have just inherited the documentation for a totally configurable software
>application (large and expensive, intended for hospitals). This program
>is, like, the most un-shrinkwrapped software I've ever seen.
You have to go to the developers for help. They couldn't have created the
program without an underlying model that maintains internal consistency
while allowing users to make so many independent choices.
You need to understand the underlying model thoroughly. That's what you're
really documenting.
Then you need to understand the needs of typical hospitals for this sort of
application. This will help you identify which features and choices are
important to your potential readers.
Once you understand the model and the application, you'll be able to explain
the user interface, and you'll be able to tell users how to think about and
plan their final configurations.
This kind of project calls for a task-oriented user guide, focusing on the
most common problems users need to solve, and a comprehensive reference
guide. The latter should probably be integrated into the user interface, not
simply spewed out onto paper. ...RM
