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.
Subject:Re: Need examples of system documentation From:Janice Gelb <Janice -dot- Gelb -at- Sun -dot- COM> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Sun, 28 Sep 2008 20:12:18 +1000
deltaskye wrote:
> I am returning to IT system tech writing after an absence of four years. My client wants me to document a system that is already in place; the engineer who designed it did not write anything down!
>
> I will be working with a new engineer to try to document the system (not for end-users, for the company's internal/engineering use). The engineer will be the technical SME and I will be the scribe and desktop publisher. The system is used by staff to register new customers for a service, document customer service calls, and transmit each day's activities to another system.
>
> The engineer has asked me to provide him some examples of what the documentation might look like. I have all kinds of stuff generated when other customers followed an organized SDLC as they were designing a system. I'm looking for ideas on how to frame the documentation as the engineer and I try to document a system that someone else designed (and who is no longer available).
>
> I don't know if the following is helpful, but here are some of the topics the engineer has suggested:
>
> External data interfaces
> Oracle database management system
> BEA configuration
> System backup/restore
>
Funny you should ask... I've been combing the web
lately for system administration documentation for
a paper I'm giving at the Usenix LISA conference
(called "WTFM: Documentation and the System Administrator").
It's the most nervous I've ever been about presenting
at a conference because my audience won't be tech writers
and I haven't actually worked in a sys admin environment.
(If anyone has examples of bad internal sys admin docs.
please let me know - I promise to remove all company
identification :-> )
But enough about me. Try searching for:
system administrator internal documentation
documentation system
documentation server
***********************************************************
Janice Gelb | The only connection Sun has with
janice -dot- gelb -at- sun -dot- com | this message is the return address
ComponentOne Doc-To-Help gives you everything you need to author and
publish quality Help, Web, and print content. Perfect for technical
authors, developers, and policy writers. Download a FREE trial. http://www.componentone.com/DocToHelp/
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-