Just an idea, although I have to confess it scores precisely 0 hits on Google.

"This DTAP principle means that you have 4 different environments (physically separated), each with their own purpose within the change/release process. The D stands for Development, T for testing, A for Acceptance and P for Production. Every new release of software (and hardware) should follow this 'lifecycle'. Something new or a change to existing software should be developed in the D environment, Tested in the T environment (by the developer). Acceptance by the user and the administrators is done in the A environment, where all kinds of (pre documented) tests are performed. Here you can perform enduser tests, performance stress tests, integration tests, installation tests, test the fall back plan and so on. When all test results 'give a go' then the change can be implemented as planned. When tests fail, you go back to the D-environment and the cycle restarts."

http://forums.datamation.com/archive/index.php/t-595.html

(OTAP seems to be more common as an acronym in Dutch than DTAP is in English, so you may need to spell it out in your translation).