Joan Cadenhead, Ph.D.

Align | Confirm | Configure | Deploy | Realize User Acceptance Test Plan Event Summary Final Document Owner: Information Classification: [TriZetto User] Confidential Copyright Notice Confidential and Proprietary. Copyright © 2010 The TriZetto Group, Inc. All rights reserved. Limited Rights Notice (Month YYYY) (a) These data are submitted with limited rights under Government Contract. These data may be reproduced and used by the Government with the express limitation that they will not, without written permission of the Contractor, be used for purposes of manufacture nor disclosed outside the Government; except that the Government may disclose these data outside the Government for the following purposes, if any; provided that the Government makes such disclosure subject to prohibition against further use and disclosure: None (b) This notice shall be marked on any reproduction of these data, in whole or in part. Trademarks TriZetto, the TriZetto Triangle logo, Facets, and Healthweb are registered trademarks, and Powering Integrated Healthcare Management, NetworX Suite, QNXT and Treatment Cost Navigator are trademarks of The TriZetto Group, Inc., or its subsidiaries. Other company and product names may be trademarks of the respective companies with which they are associated. The mention of such companies and product names is with due recognition and without intent to misappropriate such names or marks. Align | Confirm | Configure | Deploy | Realize Document Revision History The End User Acceptance Test Plan document was first published in Month YYYY. The following table lists subsequent changes made to the document. Date Description YYYY-MM-DD Initial Draft YYYY-MM-DD Updated Draft of document YYYY-MM-DD Final Draft of document Copyright © 2010 The TriZetto Group, Inc. Confidential All rights reserved. Confidential and Proprietary. d:\dell inspirion 11 3000 series\freelance samples - of work completed\process for user acceptance test plan sample.docx - Page 2 of 5 Align | Confirm | Configure | Deploy | Realize Description This event outlines the plan for End User Acceptance Testing for a system implementation or upgrade. The purpose of the End User Acceptance Testing plan is to outline the business testing approach that will be employed to demonstrate that the core system, ancillary components and related interfaces meet the business and operating requirements necessary to support the business once the system goes live. Key Outcomes The Key Outcomes associated with completing this Event are as follows. 1. 2. 3. 4. 5. Testing Scope Testing Schedule Testing Resource Plan Testing Processes Entrance and Exit Criteria Required Sign-offs The following require sign-off as a result of this Event. 1. User Acceptance Test Plan Key Inputs The following artifacts are critical inputs required to complete this Event. {List all artifacts that are key inputs to this Event. List the specific artifacts in the TZAF that are required inputs to completing the tasks associated with this Event. If the artifact is a new artifact, denote this by putting “(new)” after the Document Name. In addition, denote in the Description which Event in the TZAF produces this new artifact. } Document Name {Name of artifact} Master Test Approach Resource Management Plan Functional Design Document Technical Design Document Description {Brief description of this artifact if it is new and not already included in the TZAF Artifact inventory} Critical for Release 1? {Is this artifact critical and to be ready for 1/11} – yes or no? Yes Yes Yes Yes Copyright © 2010 The TriZetto Group, Inc. Confidential All rights reserved. Confidential and Proprietary. d:\dell inspirion 11 3000 series\freelance samples - of work completed\process for user acceptance test plan sample.docx - Page 3 of 5 Align | Confirm | Configure | Deploy | Realize Document Name Description Business Standard Operating Procedures Defect Management Approach Critical for Release 1? No Yes Key Outputs The following artifacts are the primary outputs resulting from completion of this Event. {List all artifacts that are key outputs to this Event. List the specific artifacts in the TZAF that are called out in the ESD’s as well as any new additional artifacts that are critical and not currently reflected in the TZAF artifact inventory. If the artifact is a new artifact, denote this by putting “(new)” after the Document Name} Document Name {Name of artifact} Description {Brief description of this artifact if it is new and not already included in the TZAF Artifact inventory} User Acceptance Test Plan Defect Management/Issues Log Document (spreadsheet) with all test results, issues and final statuses of defects. Critical for Release 1? {Is this artifact critical and to be ready for 1/11} – yes or no? Yes Yes Copyright © 2010 The TriZetto Group, Inc. Confidential All rights reserved. Confidential and Proprietary. d:\dell inspirion 11 3000 series\freelance samples - of work completed\process for user acceptance test plan sample.docx - Page 4 of 5 Align | Confirm | Configure | Deploy | Realize Work Breakdown Summary The following outlines the specific tasks that need to be completed in order to complete the Event and its associated Key Outcomes (artifacts). {List each step in the process required to complete the event. Keep the steps clear and to the point. Number the steps to reflect the order that the steps (or tasks) are to be completed. Identify where each Key Output (artifacts) is produced (i.e. at which step in the work breakdown summary). Provide any necessary clarifying description for each step. Note, this information will be used to generate the master MS Project Schedule as well as explain to the end user ‘how’ to complete this Event. Be sure to clearly reflect any differences in the process/steps to complete this Event for an implementation versus an upgrade as well as a licensed versus hosted project}. Task # Name {Brief description of this artifact if it is new and not already included in the TZAF Artifact inventory} 1.0 1.1 Requirements review sessions Master Test Approach 2.0 Business Requirements Document 3.0 Functional Design Document 4.0 4.1 Technical Design Document User Acceptance Test Plan 4.2 User Acceptance Test Cases Description {Provide any necessary description to clarify this step for the end user. If this step is unique to a licensed vs. hosted project, state as such in the description. If this step is unique to an upgrade vs. implementation, state as such in the description. The alternative is to have a separate work breakdown summary table for the unique situation} Review requirements to create master test approach and strategy TZG or TZG and Client collaborate to develop a document which defines the overall scope, approach, resources, phases, environments, tools and timelines for testing. Signed and completed documentation of review sessions, defined business rules (requirements) as described by the client. Illustration of the hardware and software design for the application, used to identify dependencies, interfaces and other effects of the software to be implemented. Provides basic overview of software codes’ paths via algorithms. Plan (approach) developed based on the following documents – Business Requirements; Functional Design; and Technical Design. High-level test cases created to address the function of the application and the interactive modules as well as Data converted, and business use cases deemed critical to go-live and system optimization.