Purpose
The purpose of this deliverable is to install a viable, correctly configured technical quality assurance (QA) environment that is available for use by for the project teams to perform integration tests, volume tests, and stress tests against production-class data. As part of the defined system landscape, the QA environment SAP systems but also initial technical configuration, such as project team user Ids and installed printers. Change requests that have been unit tested in development are imported to complete the initial QA configuration.
How should it be produced
The following steps are required to install and configure a quality assurance (QA) environment ready for all integration test operations.
· Obtain and install all hardware required for the QA system and successfully load and configure all SAP software targeted for use in this system.
· Import all unit tested change requests from the development environment into the QA environment and load the appropriate application data for test operations.
· Import user role and authorization change requests from the development environment to the QA system for test operations.
· Define and configure all output devices, including printer, faxes, barcode printers and other devices to accommodate any operation within the QA environment.
· Load all appropriate master data and test data for test operations.
What if it is not done
A careful and well thought out quality assurance environment is validity and viability of all objects, processes and procedures that would be introduced into the production system. Without which, possible errors and critical deficiencies might be introduced into the production system which would disable or negatively alter critical production processes.
Source of
Input (Deliverable/Other) |
Input
|
Technical Requirements and Design |
· (All deliverable outputs) |
Project Standards and Procedures |
· Project team system authorization standards · CTS standards and procedures for project members |
Outputs
Refer to the breakdown of the deliverable in the roadmap structure.
None.