Have you ever been on in a compliance effort, where things were a little frantic? Although it’s nice when projects are organized, deliverables are clear, and everybody’s moving nicely to schedule, sometimes it doesn’t work that way.
The key to surviving audit analysis is knowing how to transform your data, and the key to transforming your data, is knowing how to use Toad to write transformation procedures, and Quest Code Tester to test them. For instance, you may have a segregation of duties control, that states that people receiving payments shouldn’t be the ones applying them to the open accounts receivable balance. If you have a cleanly organized database, then you have no problem. How many databases have you seen like this? More than likely, you have a simplicity-challenged database, that’s not organized for auditing. A simple SQL statement won’t do, so you’ll need to build a transformation.
In this technical brief, compliance expert, John Weathington, will show you how to build a transformation, using Quest Code Tester, Toad, and Test Driven Design (TDD), a method popularized by the agile community.