Development, testing, acceptance and production
||This article may require cleanup to meet Wikipedia's quality standards. The specific problem is: Poor English in DTAPS section, and article needs context for lay-readers.. (September 2013)|
This is the sequence:
- The program or component is developed on a Development system. This development environment might have no testing capabilities.
- Once the developer thinks it is ready, the product is copied to a Test environment, to verify it works as expected. This test environment is supposedly standardized and in close alignment with the target environment.
- If the test is successful, the product is copied to an Acceptance test environment. During the Acceptance test, the customer will test the product in this environment to verify whether it meets their expectations.
- If the customer accepts the product, it is deployed to a Production environment, making it available to all users of the system.
The set of environments used for a DTAP cycle is often called a DTAP street.
The S who stands for Swerve location can also be added to DTAP. If a certain application requires a high uptime guarantee, in advance a Swerve location can be configured as standby. After testing and deploying any application change also in this environment according DTAPS, the continuity of the application is more guaranteed.
- Evans, Cal (2009), Professional Programming: DTAP – Part 1: What is DTAP?
- Wiggers, Steef-Jan (2009), DTAP Strategy: Pricing and Licensing