Case Study 06
build User Acceptance Testing (UAT) Strategy for global organization
A worldwide consumer electronics & semiconductor company's global implementation of an User Acceptance Testing (UAT) Strategy to finalize the testing of all application installations, upgrades, fixes, and integrations.
Industry: Consumer Electronics, Semiconductor
Annual revenue: $5 billion
Region: North America
Reason for Project: quality assurance
To provide World Class UAT to validate that all components of the solution -- the business processes/activities, system functionality, requirements, and infrastructure are developed in accordance with the blueprint design and corporation policies and standards, and can be reliably delivered. Test Scripts will be documented to capture the expected and actual results of testing, and identified defects will be tracked, fixed, and re-tested.
The team designed and employed an UAT strategy and methodology to finalize the testing of all application installations, upgrades, fixes, and integrations. The business user was identified as a critical component of testing as they typically own the production system and are the most appropriate group to understand whether the system performs as expected. During the test phase, business users had involvement, as defined for each project. Business users participating in testing were required to be familiar with design and understand that testing schedule will be strictly adhered to. Business user approval was required for requirements, scenarios and test Scripts.
The team identified key phases to include:
- Release Request Process
- Authorization Workflow
- Test Planning and Estimation
- Review and Sign off Test Plan
- Testing Documentation
- Test Preparation
- Test Environment Set-up
- Change Control of Test Environments
- Test Execution
- Defect Management
- Product Change Control
- Ongoing Test Reporting
- Test Summary Reporting
- Review and Sign off Test Execution
The team was able to implement a reusable process to include workflow and real-time reporting to for all Major, Minor and Break-fix releases. Requirements were documented and mapped to the test Scripts that test the requirement. These requirements were documented business requirements located in ARIS (business process documentation tool). The mapping ensured the test Scripts covered all required functionality, business processes and activities, as defined and provided documentation on test coverage for control and validation.
This reusable UAT Strategy ensured the system requirements would meet the business needs and continue to provide quality products at go-live for all application installations, upgrades, fixes, and integrations.