After describing the migration path environments for different customers, I thought it might be time to define some migration paths and their associated environments. This is a migration environment pattern I have seen in larger organizations, perhaps, with some variation, but essential variations on a theme. The definition of each environment is in the table below.
|Development (DEV)||The Development environment is used for developing the application and the submission of baseline code to the source control system.|
|System Integration Test (SIT)||System integration testing is high-level software testing process in which testers verify that all related systems maintain data integrity and can operate in coordination with other systems in the same environment. The testing process ensures that all subcomponents are integrated successfully to provide expected results.|
|Software Integration Test (SWIT)||Software Integration Test is where software module or component subset testing occurs to verify the functionality and/or usability of a module or component and interaction with associated software models and components.|
|End-To-End (E2E) Testing||End-to-End Testing exercises a complete production-like scenario of the software system, it also validates batch and data processing from other upstream/downstream systems (interfaces).|
|System Acceptance Testing (SAT)||System Acceptance Testing is to simulate the business environment, security, and regression tests. System Acceptance Testing is conducted to gain acceptance of all functionality from the user community and meets user requirements, as specified.|
|Production (PROD)||The production environment is the final release environment, where the system will begin its Initial Operating Capability (IOC).|
|Control (CTRL)||Control is the ‘Gold’ standard baseline environment from which migrations and new environments are provisioned. This environment houses base configurations and metadata. It is not used for testing.|