Re: Documenting A Moving Target

Subject: Re: Documenting A Moving Target
From: Stuart Burnfield <slb -at- FS -dot- COM -dot- AU>
Date: Thu, 22 Feb 1996 12:29:55 +0800

As of 4:16 PM 2/20/96, Karen Gwynn was chasing the bunny around the
greyhound track of software development:

Karen, ask your developers to give you a regular list of changes. A list
of what has changed and why would be great. A list of what lines have
changed in what files is at least something. A list of what files have
changed is better than nothing, and should only be one minute's work
for the developer even if they aren't checking source out and in.

Plan to check *every* screen dump once the software is frozen. Import
them by reference rather than copying each one into the document. That
way you don't have re-import every screen that you have to capture again.

> And, finally... When they ask you when the documentation will be
> ready to send to the printer, answer, "two weeks after the UI freezes."

Carve these words in stone.

Regards
---
Stuart Burnfield (slb -at- fs -dot- com -dot- au) Voice: +61 9 328 8288
Functional Software Fax: +61 9 328 8616
PO Box 192
Leederville, Western Australia, 6903


Previous by Author: Re: Job Descriptions
Next by Author: Re: "See" and "Utilize"
Previous by Thread: Re: Documenting A Moving Target
Next by Thread: Re: Documenting A Moving Target


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

Sponsored Ads


Sponsored Ads