Re: How to document test procedures?

Subject: Re: How to document test procedures?
From: Randall Raemon <rlr -at- HAL -dot- COM>
Date: Sun, 8 Jan 1995 12:22:22 -0600

In message <9501062003 -dot- AA24099 -at- hal -dot- com>
Sue Heim writes:

> Oh joy!! I have been assigned to a committee whose charter is to
> write the process and procedures for testing our software (both
> upgrade and new releases). Does anyone know of any books, or other
> information, that is available that I could use as a foundation?

Some references for you:

Testing Computer Software
Kaner, Falk, and Nguyen
Van Norstrand Reinhold, 1993
ISBN 0-442-01361-2
about US$33.00

In the various software testing books that I used, this is the most
comprehensive and readable. There is discussion on the full range of
things: test techniques, problem tracking systems, tools, and legal
aspects.

Depending on what kind of formality your site has, then the
following IEEE standards might be useful:

Std 829: Software Test Documentation
Std 983: Software Quality Assurance Planning
Std 1008: Software Unit Testing
Std 1063: Software User Documentation

If you consider getting more than 2-4 standards, then it is more
cost effective to get the Software Standards Collection. The 1994
edition was published about mid-94.

IEEE Software Engineering Standards Collection, 1994 Edition
Product Number SH-94213 US$124.50

IEEE stuff can be ordered from their publications dept. Contact is
1-800-678-4333 or 1-908-981-1393. There are discounts for IEEE
members.

Disclaimer: I don't work for IEEE. I'm a software grunt and I've
found the IEEE stuff to be extremely useful.

Good luck...

--
Randall Raemon
rlr -at- hal -dot- com work
delta1 -at- netcom -dot- com personal
0005650778 -at- mcimail -dot- com elsewhere


Previous by Author: Windows help files
Next by Author: Re: What Technical Communicators Do
Previous by Thread: How to document test procedures?
Next by Thread: SIGNOFF


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

Sponsored Ads


Sponsored Ads