Development, testing, acceptance and production
- The program or component is developed on a Development system. This development environment might have no testing capabilities.
- Once the software 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 set of environments can be smaller or larger, depending on the demands of the project. Examples of other steps are:
- Education – This extension of the DTAP-street is a training environment for the users of the production environment.
- Backup – The Backup site is used for Disaster recovery.
Though the methodology is called DTAP, some projects might use DTAPB, DTP, DTEP or any other variant addressing the project needs.
- Evans, Cal (2009), Professional Programming: DTAP – Part 1: What is DTAP?
- Wiggers, Steef-Jan (2009), DTAP Strategy: Pricing and Licensing