Package Implementation Testing
The methodology that ensures successful implementation of packaged solutions for business critical applications
- Reduces the cost of testing and implementation by up to 25% and the time of testing by up to 40%
- Ensures packages operate in the existing system correctly and deliver expected results
- Ensures customer/user requirements are delivered
- Ensures control is retained by the business by delivering effective reporting and metrics
More commonly, businesses are buying 'off the shelf' packages that are developed by 3rd party companies and sold as executable software. This means that the application code is not available to the customer/user and cannot be changed, although with some applications it is possible to manipulate the use and results in controllable ways. Often customisation is implemented to more closely match the business requirement.
The role of the tester is very different in this methodology. There is no fit for use testing such as Unit Testing or Integration Testing undertaken as the package manufacturer carries all this out at development stage. The testing that needs to be completed is Discovery Testing, which mediates the customer/user requirements with the constraints of the packaged application and tests that custom options are operating correctly. System Integration Testing, followed by User Acceptance Testing and Operational Acceptance Testing.
Training for staff on the use of the new package, customisation or upgrade is a vital part of UAT and should be supplied as part of the testing project.
Live Support Testing should be carried out by the Testing Team in conjunction with the package supplier. Mediation between the package supplier and the customer/user becomes a very important activity during the execution of this methodology, a function that SIM/SQS perform as an independent mediator with the customer's initial requirements forming the basis for acceptance.
Mediation between the supplier and the business is essential to ensure that the package delivers as specified. Differentiation between the problems of the system and the package problems is vital for clear identification of the methods to employ to achieve optimisation. Data conversion from the old system to the new needs to be tested for reliability and completeness. Testing to ensure the new data actually works with the new system is also vital for the business.
The new upgrade must then be Load & Performance tested to ensure that the system operates at maximum efficiency.
 |
Why use Package Implementation Testing?
Package Implementation Testing empowers those in charge of implementing packaged solutions and their testing to ensure that all critical systems perform as required to remove any business risk from the software package implementation.
A Test Management Control Panel reports in a clear and concise manner the ongoing effect that the testing project is having and shows the reduction in time taken to identify and correct faults and the cost savings accrued.
Deliverables
- The potential risk to the business of either implementing packages or insufficiently tested systems is removed.
- The cost of any outsourced requirement can be fully justified and a return on investment calculation proves that cost reductions and time reductions will be achieved.
- The Test Management Control Panel reports the ongoing successes of the programme so that management can see the improvements achieved and the resulting savings accrued. Fault discovery trends and reducing costs of implementation together with time saved are presented as easily understood graphical reports.
- As part of a Test Optimisation Programme designed to improve core business processes, Package Implementation Testing delivers guaranteed cost and time savings and allows management to effectively manage the development and implementation of packaged solutions within critical business processes.
