Development and Test
Esri begins this stage with test planning and the configuration of appropriate development and test environments. This stage ends once all required application or system components have been tested and accepted during user-acceptance testing. It is important that we get the system right, so this stage is one of the longest.
Test Planning and Environment Setup
This includes developing a test plan and test scripts and installing and configuring development and test environments. Once these are configured, development and testing activities are structured to allow application functionality to be developed, tested, and validated incrementally. Esri provides interim development reviews to ensure visibility prior to formal testing cycles.
Database development typically occurs in parallel with application development and involves implementing data repositories as needed based on requirements and design specifications. Because the migration of existing data to new data schemas is often complex, Esri's approach involves developing extract, transform, and load (ETL) and/or data migration specifications, followed by a pilot migration.
The pilot migration exercises the database design and initial data migration procedures using your actual data to help identify any issues with the source data. Once issues are resolved and the final database design and migration procedures have been accepted, development or migration of the full database occurs.
Testing and Stabilization
System components are tested incrementally using regularly scheduled builds. Results are reviewed by the project management team to evaluate the completion status of the release and to define appropriate corrective actions, if needed.
Once system components are functionally complete and pass the required internal review, Esri may conduct two formal testing cycles to verify that system components meet specifications. These consist of an end-to-end Internal Acceptance Test conducted by Esri, and the User Acceptance Test conducted by you. Ideally, these tests will be conducted in a test environment that mimics the planned production environment.
The type and format of system documentation will vary depending on the type of project, and on the target audience for an application. Esri typically expects to develop a System Installation and Configuration Guide, an Operations & Maintenance Guide, and a User Guide (typically online) as standard system documentation deliverables.