Difference between developer guide content and reference information

[rachna_bhutani -at- yahoo -dot- com]

Hi All,

I have to create a developer guide and a product reference (guide?) for
the same product. These documents will enable developers to create
applications based on the product. However, I am unclear about the type of
content that should be included in each guide. I would appreciate inputs
on how to decide what should go into a developer guide, and what should go
into a product reference document.

According to me, a developer guide should have an architectural overview,
information about key system components, steps in developing an
application, configuration and security information. However, I have
looked at various books, and the reference books also seem to have the
same topics. Both also have code examples. The only difference I noticed
was that the reference books contained a great deal of code examples to
explain the usage and functionality of the functions/methods, classes,
fields etc, whereas the developer guides didn't have as many code
examples.

Suggestions on what kind of information to include in each document would
be most helpful.

Thanks in advance,

Rachna


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo:
http://www.webworks.com/techwr-l

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.