3rd party software documentation
Spreadbury, David
david.spreadbury at tellabs.com
Mon May 15 07:21:33 MDT 2006
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.spreadbury=tellabs.com at lists.techwr-l.com [mailto:techwr-l-bounces+david.spreadbury=tellabs.com at lists.techwr-l.com] On Behalf Of csouther at mindspring.com
Sent: Monday, May 15, 2006 7:56 AM
To: techwr-l at lists.techwr-l.com
Subject: 3rd party software documentation
All,
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.
Thanks,
Chris
Chris Souther
www.mindspring.com/~csouther
============================================================
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
============================================================
More information about the TECHWR-L
mailing list