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.
Have you seen JoAnn Hackos' book, "Managing Your Documentation
Projects?" It's published by Wylie and I hear it's out of print,
though others say no. It's invaluable and EXACTLY what you need.
Jane Bergen
jbergen1 -at- earthlink -dot- net
----- Original Message -----
From: Humbird, Len - CFC <Humbird -dot- Len -at- cfwy -dot- com>
To: TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com>
Sent: Wednesday, September 22, 1999 1:11 PM
Subject: Taming the Wild, Wild I.S.
> Hi,
>
> I'm contracting for a company that was recently spun off, and is
having
> difficulty managing their own I.S./I.T. department. There is
virtually NO
> formal process to manage, coordinate or control software projects
and
> resources here! So... I am looking for *samples* of the following
types of
> standard internal documentation to implement:
>
> * Proposal for new/updated software development project
> * Requirements Specification Template
> * Design Specification Template
> * User Interface Standards (for Windows/PeopleSoft applications)
> * QA Methodology Standards
> * Test Plan Template
> * User Acceptance/Signoff Template
>
> The IS/IT department provides information resources and services for
the
> rest of the company. It is mostly a PeopleSoft environment.
>
> Can someone point me in the right direction for some ideas on the
format and
> layout of these templates and standards?
