Hi Tracy, Given your industry, I can readily imagine you need that paperwork. I don't think such a formal document exists, but I do believe perl's QA routine is sufficiently robust that it would pass through that.
I suspect we'd know the answers, but not the questions in this matter. We don't know how to write those documents, even if we do know how our system works. Could/would you be able to write it by asking us questions about it? Leon On Wed, Jul 31, 2013 at 10:46 PM, Tracy Radel <tracy.ra...@shinemed.com> wrote: > Hi Dag, > > > > It is more an issue of documentation of how quality assurance is done for > Perl. Our procedures for QA require that when doing QA on a model or > program we have created (my ultimate goal), any software used by that > program must also have gone through a sufficiently rigorous QA process. For > other programs I have been able to find documentation on their QA program > that includes standard practices, problem reporting, code control, records > management, etc. They also have documentation describing the V&V tests > performed with tolerances and results outlined. > > > > I understand that an open source product works differently than a product > developed by a single entity, but I have no way to get my QA Manager to sign > off on use of Perl without some documentation for the QA practices used. > > > > I personally believe that the testing done on Perl is far more extensive > than on most software, but I need to be able to prove that with > documents…this is my problem. >
