RSSP R4 UVT Approach Highlights

1. RSSP R4 UVT Approach Highlights May 23, 2007 Ray Lafser

2. Objectives of UVT • Verify that working systems provide the functionality to enable the business users to complete the work processes required in their day to day jobs. • Validate that users are ready to go live with the new systems and processes, and are comfortable that the functionality will allow them to perform their day to day jobs • Validate that the security profiles assigned to different user roles are sufficient

3. UVT Scope • DART and GSS? • UVT scope will test many business processes which use systems that have been changed by RSSP R4 including the following: • Aspen (Logistics) • Customer Self Service Ordering (CSS) • DJP Franchise Reports and Planograms • Pricebook • QuickBooks • S2K • Royalty • SAP & Home Office Information – BW • Tax & Accounting • WOR Settlement

4. Not in UVT Scope The following elements are not in UVT scope as they will be tested in Integration Test (IT): • Checking that requirements are met • Functionality testing • End to end interface testing • Performance and stress testing

5. UVT Entry Criteria • UVT is expected to begin shortly after the completion of Integration Test Cycle 2 or Cycle 3. The following criteria, which are the exit criteria for IT, apply as entry criteria for UVT: • 90% of Test Scenarios and conditions have been successfully executed in Integration Test • Any open urgent or high priority defects have an agreed workaround or defect resolution date • List of open medium and low priority issues has been acknowledged by the business and the project has been approved to move forward • Integration Test Closure document prepared and agreed (or IT fix 2 phase complete)

6. UVT Entry Criteria (continued) • Additional criteria that are not required for Integration Testing, but are required for UVT include • Test phase scope is agreed and signed off by business • Test scenarios have been agreed and signed off • Test conditions and expected results are agreed and signed off by business • Test scripts to be used in UVT have been identified, agreed, and executed in Integration Testing • UVT approvers, who are expected to be the FRD approvers or their designates, have been identified • UVT Approach document has been signed off • UVT test execution plan has been completed and signed off • Number of UVT test cycles is agreed • UVT testers have been identified, agreed, recruited, and trained

7. UVT Exit Criteria • 90% of Test Scenarios and conditions have been successfully executed in UVT • Any open urgent or high priority defects have an agreed workaround or defect resolution date • List of open medium and low priority issues has been acknowledged by the business and the project has been approved to move forward No urgent and high priority defects are open without agreed workaround or defect fix date • User Verification Test Closure document prepared and agreed by UVT approvers

8. Test Cycles • UVT could be third cycle of integrated testing • Two cycles – one week each • First week - test 75-80% of the test scripts • Second week - test any scripts not tested in the first week and retest any scripts which did not pass in the first week of testing

9. UVT Roles and Responsibilities • UVT Test Lead • Defect Manager (same as for Integration Test) • Change Request Manager (same as for IT) • UVT Approvers - expected to be FRD approvers or their designates • Testers • Elite • Headquarters staff (Business team and extended Business team) • Franchise Consultants • Selected Franchisees • Technical teams – run interfaces and load data to support tests

10. Assumptions

11. Risks and Mitigations