LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (September 2003, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Sat, 13 Sep 2003 09:08:01 +0100
Reply-To:   Roland <roland@RASHLEIGH-BERRY.FSNET.CO.UK>
Sender:   "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:   Roland <roland@RASHLEIGH-BERRY.FSNET.CO.UK>
Organization:   Universe Monitors
Subject:   Re: CRO start-up?

I have a testpack for every macro on my web site that I consider might run in a production environment. The test packs test out most of the options in the macros. I compare the output with what I am expecting the macro to do. HOWEVER, the process of "validation" must be done by the users themselves according to FDA rules. So all these testpacks have been disabled using a endsas; statement in the first line. This stops users just assuming they have been validated. The testpacks need a tester id added and date and need the endsas; line removed and it is then up to the tester to add or change that test code until they themselves conclude the macro is functioning correctly. I could spend an absolute age testing those macros and write vast amounts of code to test them but that would not make them validated as the USER has to validate them. Those are the rules. I think my test packs provide a useful start but it is no more than a start in the process of validation. But having said that, I don't think it would take very long at all for a user to put them through this process of validation. Maybe as little as a week if working on it full time. Maybe two. Only a few of the 114 macros there (or whatever - I've lost count) are large and need extensive testing. And if a new department or a CRO start-up used that code then those two weeks validating them would repay itself many times over. But bottom line is - the USER has to validate them. The rules say so.

"TAXQA" <tax_qa@yahoo.com> wrote in message news:390eccb7.0309121020.532cc332@posting.google.com... > Hi Roland, > > Could you describe how do you validate your macros? > > Thanks > > A SAS user. > > "Roland" <roland@rashleigh-berry.fsnet.co.uk> wrote in message news:<bj723b$smn$1@news6.svr.pol.co.uk>... > > Is your company a CRO start-up? Are you thinking of putting in place some > > code for standard safety reporting? Some sort of sophisticated system with > > titles and footnotes handling? But this will cost BIG money, you think, and > > will take a long time and maybe more than one attempt to get it right? > > > > Well, if you answered "yes" to those questions then I have come to your > > rescue. I have such a system on my web site plus much more. And it is all > > FREE. Nearly 6 man-months work is there. 110 sas macros plus a number of > > unix/linux utilities. There is maybe in excess of $50,000 worth of code > > there and I am giving it away. My friends think I am mad to do this and I > > think they are right. You could become a CRO start-up millionaire and not > > give me a penny (cent) of it. You don't even have to tell me you are using > > it, let alone pay for any of it. I have donated it all to the public domain > > so it is now yours as much as mine. So point your technical person at my web > > site and save yourselves a fortune. > > > > http://www.datasavantconsulting.com/roland/


Back to: Top of message | Previous page | Main SAS-L page