You don't have to "Test", you make that functionality part of the bid process.  The vendor needs to demonstrate that the system you are buying has that capability.  They should also be able to connect you to other users of that system who are using the system.  You can also work this out ahead of the need by pre-qualifying vendors of system products.  Dick King, University of Arizona

-----Original Message-----
From: Records Management Program [mailto:[log in to unmask]] On Behalf Of Link, Gary
Sent: Monday, January 9, 2017 7:31 AM
To: [log in to unmask]
Subject: Testing Compliance in Applications

So, let's say - (strictly hypothetically speaking and not at all a real world issue I'm having) - that you're working with your IT folks to have data retention requirements compliance functionality written into the requirements documents and design review process for new computer applications. And the IT folks say, "Fine, we'll put the data retention requirements compliance functionality in our requirements documents and design review process for new computer applications. But, being IT folks, we don't put anything into requirements documents and design review process for new computer applications that we can't test. So tell us, Mr. Records Manager, how do we test for retention compliance for a new computer application while it is in design and/or QA?"

How would I,  er, I mean, how might one answer them?

Thanks,
Gary Link
Pittsburgh, PA
[log in to unmask]

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]