TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
We have a similar development cycle - 3-4 months. Each release contains some
major new functions/modules and bug fixes. In a release we have a definite
System Test Phase (at least 5-6 weeks), and I find that the main
Documentation work can happen at this time as well. We deliver online
documentation only, so I don't need any hardcopy publishing time. Prior to
day 1 of System test, we can do our planning, and for major new features we
can start the background work. During testing there is often a new minor
build, but there is always access to the product.
This works for me.
Cheers,
Margaret - x5590
-----Original Message-----
From: Vlad Dracul [mailto:vladvampiredracul -at- hotmail -dot- com]
Sent: Wednesday, 24 September 2003 3:40 PM
To: TECHWR-L
Subject: Documentation Phase in Software-Development Life Cycle
<snip>
I want to know the following:
* Is such a situation normal in a software company? Are there examples of
other companies that work in such a fashion?
* How does one produce good documentation in on schedule in a setup such as
this?
* Are there any documentation methodologies that lend themselves to this
manner of working?
Suggestions and comments would be much appreciated.
---
This email and any files transmitted with it are solely intended for the use of the addressee(s) and may contain information that is confidential and privileged. If you receive this email in error, please advise us by return email immediately. Please also disregard the contents of the email, delete it and destroy any copies immediately.
Computershare Limited and its subsidiaries do not accept liability for the views expressed in the email or for the consequences of any computer viruses that may be transmitted with this email.
This email is also subject to copyright. No part of it should be reproduced, adapted or transmitted without the written consent of the copyright owner.
NEED TO PUBLISH YOUR FRAMEMAKER CONTENT ONLINE?
?Mustang? (code name) is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to Web, intranets, and online Help.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! See a live demo that
will take your breath away: http://www.ehelp.com/techwr-l3
---
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.
