next up previous contents
Next: Troy Pearse Up: Beta Correspondence Previous: Beta Correspondence

Initial instructions

Conditional Compilation Analyzer ( CCA ) Beta Tester Instructions

Unpacking:

These instructions accompany the beta version distribution file for CCA.
The name of this file is "cca.BETA\_1.tar.Z".  There is also a readme file
available with the distribution file.  This readme file provides simple
instructions for unpacking the distribution file, accessing the man page, and
running the program.

Project schedule:

  Beta-Release                       : November 14, 1996
  Last day for beta-tester responses : December 3rd
  Final walkthrough with customer    : (to be determined)
  Final product release              : December 9th

Instructions to the beta-tester:

Primarily, we would like you to simply play with this utility - mess with it,
give it odd input, do strange and unnatural things to it.  If it does
something unexpected, make a note of it.  If you get tired of those games,
then give it the most complex C code you know of, or write your own twisted
code to try to choke it.  Please find a way to break our code, then tell us
about it.  

When you do find something, take note of the peculiarities of the situation.
Let us know what the input looked like, if applicable.  Better yet, we'd love
to be able to actually get our hands on any particularly deviant code, if
that can be arranged.

Please include the following information in your responses:
 
  Name :
  Computer -
    Processor :
    OS version :

  Version of Perl :
  Version of GhostScript :

  Comments on the command-line, man page, usage statement, README file:

  Comments on the output format, both textual and graphical:

  Description of any bugs / errors found:

  Additional comments, criticisms, suggestions, or information which will
  help us improve this product:

Specific things to look at:

Can you get the program to run ?
Is the man page helpful / readable / complete ?
Do you understand the command line switches ?
Is Perl installed on your system ? Does it complain ?
Can you generate a graphical output file ?
ghostview should display it, does it?
If so, 
  ** Is it correct (as far as you understand it ) ? **
  ** Will a postscript capable printer print it ?? **
  (We're particularly concerned with these issues)	
Does the graphical output make sense to you ?
Can you find any errors in the output which we haven't caught?  

Positive responses are welcome and encouraged, but, realistically, the
criticisms and complaints will motivate the greatest improvement in this
tool.  We want your opinions, especially if you don't understand or don't
like something.    

Response times:

We would like to have your feedback no later than Dec. 3rd, 1996, as shown in
the schedule above.  This will give us just 1 week to make changes to the
code before its final release.  If you do manage to bring the program to its 
knees with something it ought to handle (in your opinion), please let us know
immediately as it may require extra time to fix.

Responses can be sent via e-mail to jone9333@cs.uidaho.edu .
Handwritten feedback can be placed in Paul Oman's mail box in the CS office.