Re: Y2K testing

[Glenn Ericson <Glenn-Ericson@xxxxxxx>]

Steve :-
Keep a  good  log of   all  activities and dates. This  should include the
plan, process, and  results which shows an audit trail..  Hopefully  you
will not be in court. BUT  should that arise bring  what  you need

Glenn
=-=-=-=-=-=-==-==
At 10:23 PM 9/24/98 -0400, you wrote:
>    We are about to start final Y2K testing out our company.  We have
already made all the database and programming changes we think are
necessary, tested them, and implemented them in our production environment.
 The question we discussing is what documentation should be produced out of
this process for legal, auditing, and customer purposes.  We are a
manufacturing company.
>    On one side of the discussion, there is the belief that we need a
document for each of our applications, describing what processes were
tested, the results, and proof that the testing proved ok(ex. printouts),
on the other side of the discussion is the belief that a general
description of the method of testing, the applications tested, the general
results, but no detailed descriptions of the processes tested or detailed
results. 
>
>Any opinions we be greatly appreciated!!
>Steve Raisor
>
>
>Attachment Converted: "D:\EUDORA\ATTACH\Y2Ktesti"
>


Glenn
___________________________________________________
Glenn Ericson,          Phoenix Consulting                      
P O Box 701164   East Elmhurst NY 11370-3164 USA                            
Phone 718 898 9805       Fax 718 446 1150
AS/400 & Year 2000- - Solutions Specialists
 © 1998 copyright,  all rights reserved
____________________________________________________


 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---