RE: Writing a Developer's Guide

Subject: RE: Writing a Developer's Guide
From: Shea Michael EXT <Michael -dot- Shea -dot- extern -at- icn -dot- siemens -dot- de>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Mon, 2 Dec 2002 10:59:26 +0100


This is a good question, but the fundamental question you have to ask is what are your readers supposed to do with the book? You can ask yourself:

1. Who is going to reed the book
2. What are they going to accomplish with it

Put the important stuff first.

Michael Shea
XpressLink Documentation
c/o ICN AS BA ST2
+49 89 722-52589
michael -dot- shea -dot- extern -at- icn -dot- siemens -dot- de

--------------------------------------------------------------------
Michael Shea
ROSEMANN & LAURIDSEN GMBH
Am Schlossberg 14, D-82547 Eurasburg, Germany

Phone: +49 8179 9307-19, Fax: +49 8179 9307-12
E-Mail: shea -at- r-l -dot- de, Web: www.r-l.de
--------------------------------------------------------------------






From: Dick Margulis
Subject: Re: Writing a Developer's Guide



Sarah,

I suggest you start with information that will help users localize their concern of the moment. In other words, begin with an overview of the system architecture (diagrams help), the general flow of transactions around the system, and a brief description of what each chunk of the system is and does. Key this overview to chapter numbers. Then, in each chapter, address one of the chunks you've identified--hardware, software, dataflow, interaction with other chunks.

That's how I've approached such systems in the past, and it has always been well received.

Dick

"Payne, Sarah" <sarah -dot- payne -at- eircom -dot- net> wrote:

>I have been tasked with writing a developer's guide for one of our internal
>systems. The system is large and complex and I'm a bit stumped as to how I
>should organise the information.
>
>I know that I need to include detailed code descriptions, architectural
>information, how data flows around the system and other hardware and
>software information. The guide is aimed at our developers and technical
>staff.
>
>How would you go about organising the information so that it is easy to find
>stuff?


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Check out SnagIt - The Screen Capture Standard!
Download a free 30-day trial from http://www.techsmith.com/rdr/txt/twr
Find out what all the other tech writers, including Dan, already know!

Order RoboHelp X3 in November and receive $100 mail in rebate, FREE WebHelp
Merge Module and the new RoboPDF - add powerful PDF output functionality
to RoboHelp X3. Order online today at http://www.ehelp.com/techwr-l

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



Previous by Author: RE: Apology to Sharon
Next by Author: RE: Hackos' minimalism seminar -- some insights
Previous by Thread: Re: Writing a Developer's Guide
Next by Thread: RE: Writing a Developer's Guide


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


Sponsored Ads