|
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
|
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.