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.
What you need is a dependency diagram. These can be part of flow charting for
instructions or stand-alone for specifications. Some of them can get pretty
hairy, though, so definitely a system administrator sort of thing, not usually
suitable for end users.
Gene Kim-Eng
----- Original Message -----
From: "McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com>
Yeah, and when we advance from command-line-only, that
will become a possibility. Until then, I guess I'm
looking for suggestions as to the optimum presentation
(there are dozens of flow-chart options in Visio,
for example, as well as mind-map and other squiggly
ways to show things interacting) - what would be the
visual thingie that would most clearly show a bunch
of interdependencies.
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com