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.
My company, DST Systems, Inc., is beginning to develop OO applications. I
read an article in December 1994 issue of Technical Communication (I
think) that described the process for documenting the objects.
DST will be developing this type of documentation. However, we are also
trying to determine how our process for developing client documentation
will change as more and more applications are developed in OO. I
would be interested in hearing how you have changed your process when
documenting OO applications. Our chief concern is that with the reuse
of objects we will have less time to develop the documentation. So, how
have you structured your documentation so that you are also reusing
Principal Technical Writer
Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net