RE: 3rd party software documentation

Subject: RE: 3rd party software documentation
From: "Spreadbury, David" <david -dot- spreadbury -at- tellabs -dot- com>
To: <csouther -at- mindspring -dot- com>, <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Mon, 15 May 2006 08:21:33 -0500

We have a similar situation with one of our applications. What we have done is to include the vendor's documentation on the CD, with the vendors agreement, and those procedures that actually use the vendors software, reference the vendor docs but include the steps to perform the procedure. The vendor documentation covers it's use 'in general'. Our procedures take it a step further and direct the user in what to enter when answering prompts.

-----Original Message-----
From: techwr-l-bounces+david -dot- spreadbury=tellabs -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+david -dot- spreadbury=tellabs -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of csouther -at- mindspring -dot- com
Sent: Monday, May 15, 2006 7:56 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: 3rd party software documentation


My companyÃââs software is increasingly becoming more Web-based, which means there are lots of different 3rd party applications (mostly Microsoft) that it requires and whose options you need to tweak.

My VPÃââs take on this is that if it affects the use of our applications, then we need to document how to configure these 3rd party applications.

My take is that someone else has already done the work, letÃââs just note the requirement and include a link (and check it periodically to ensure it remains active) to the original vendorÃââs configuration documentation. I donÃâât want there to be any hint of plagiarism and I figure the original designers know it best, so let them handle the docs.

IÃââm just curious how others handle this challenge.



Chris Souther
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs

WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!.

Doc-To-Help includes a one-click RoboHelp project converter. It's that easy. Watch the demo at

You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit for more resources and info.

Previous by Author: RE: Using SnagIt to capture long drop-down list
Next by Author: RE: Restricting PDF copying
Previous by Thread: 3rd party software documentation
Next by Thread: re: 3rd party software documentation

What this post helpful? Share it with friends and colleagues:

Sponsored Ads