User Acceptance Testing. (If applicable, describe UAT stage) Testing should include: (Describe any testing) (Describe any testing) Ricoh will assist UAT as follows: (Describe any UAT assistance) Deliverable: Checkpoint: Production Rollout (If applicable, describe rollout) Deliverable: Checkpoint:
User Acceptance Testing. Following implementation of a new software version or Equipment Configuration services. Philips and Customer will perform user acceptance testing. Philips will provide Customer with an electronic copy of the resultant configuration files and reports.
User Acceptance Testing. It is the responsibility of Client to produce the User Acceptance Test Plan (“User Acceptance Test Plan”), which will contain details of the tests that will be carried out in order to confirm that the site configuration performs in accordance with the Configuration Requirements Matrix. Client will have business days to complete User Acceptance Testing (“User Acceptance Testing Period”). StarCompliance will provide guidance to Client regarding creation of acceptance criteria and will review Client test plan and associated test scripts upon request. Client will provide sign-off upon completion by signing the User Acceptance Testing Certificate.
User Acceptance Testing. After non-production deployment, the Release Update will be available for Customer to test for a typical duration of thirty (30) days. This testing time frame will be evaluated with each targeted Release Update, dependent on the level of changes contained within. For any Release Updates that contains significant changes, the Customer testing window in the non-production environment will be extended appropriately to allow for additional testing and validation time. Failure of Customer to sufficiently test all Release Updates prior to production deployment will result in suspension of Service Metrics under Section 3.A.5. DocuSign Envelope ID: 9A44F8A5-9F7F-4DFD-B487-1BAEA5E5B7DB CGI ADVANTAGE360® SOFTWARE AS A SERVICE AGREEMENT EXHIBIT A STATEMENT OF WORK FORM
User Acceptance Testing. All platform deliverable products must pass the user story acceptance and sprint DOD criteria which includes all testing phases for compliance to customer requirements. The following test activities include: Ensure acceptance criteria is associated with each user story Validate acceptance criteria is used to inform the creation of test scripts Confirm negative testing is included in the suite of test scripts Warrant the status of the test facility and hardware and software to support the testing Ensure the availability of test personnel Identify the limitations of testing Schedule of testing activities and milestones Conduct testing in alignment with schedule The Review Team will make a final assessment as part of user acceptance testing to the delivery readiness of each platform deliverable.
User Acceptance Testing. (UAT) This deliverable is comprised of the assistance Accela will provide to allow the Agency to accept that the solution meets the requirements as documented in all the deliverables. Accela will assist the Agency in the testing and validation of the solution and its readiness to be migrated to production for active use and will assist in transferring the solution and any required data from Support to Production. Accela will provide of support for training, oversight, answering questions and addressing issues discovered in User Acceptance Testing. It should be noted that it is critical that the Agency devote ample time and resources to his effort to ensure that the system is operating per signed specifications and ready for the move to production. The testing effort will require a significant time investment by the Agency, and coordination of resources is critical. At this point in the implementation process, the Agency should test individual components of functionality of the solution (i.e., functional and/or unit testing), and also test to ensure that the interrelated parts of the Accela Civic Platform solution are operating properly (i.e., integration testing). Accela will provide assistance to the Agency as needed by providing User Acceptance Testing (UAT) support and a defined testing process. Accela will address and rectify issues discovered during the UAT process as Agency staff executes testing activities. Accela will work with the Agency to develop a test plan and deliver up to 5 sample test scripts, as well as an issue log to track the progress of testing. It should be noted that Accela will plan for a maximum of 8 weeks to complete this deliverable. If the Agency does not devote adequate time and staffing to UAT in order to completely test the solution, Accela may opt to postpone go-live at the Agency’s expense. In terms of specific output, the following will be executed for this deliverable: Resolution of issues resulting from Agency User Acceptance Testing Fully tested system that is ready to move to production for go-live Accela Responsibilities: • Provide recommendations on testing strategy and best practices. • Lead the Agency in up to 8 weeks of User Acceptance testing effort and the validation of the system configuration and its readiness to be migrated to production for active use. • Resolution of issues as a result of User Acceptance Testing activities. Agency Responsibilities: • Provide timely and appropriate responses to Accela’s ...
User Acceptance Testing. 1. Contractor in junction with the HCA project team shall develop test scripts consistent with the requirements as described in the SOW. Contractor shall work with the project team to conduct a User Acceptance Test to ensure that HCA users are able to successfully use the system and that all modified workflows, policies and procedures are consistent with it. HCA users shall assist in the actual test and shall be responsible for final approval of user acceptance test recommendations.
User Acceptance Testing. The client will conduct multiple cycles of acceptance testing (“User Acceptance Testing/ UAT”) in relation to the TCS Application System for the functionalities defined in the signed off Business Requirement Document (“BRD”), For UAT client will: • Ensure dedicated team to conduct multiple cycles of UAT. UAT team members must have participated in the Business Requirement Workshop, signed off on Business requirement document and attended UAT training and are key business users representing business users across different departments. • Provide data for UAT before start of UAT as per the timelines defined in project plan • Prepare and execute UAT test cases and scenarios as per BRD. The UAT test cases shall be provided to TCS before the start of UAT • Prepare and execute test cases and scenarios for integration and system testing during the UAT cycles. • Record and provide UAT feedback in TCS provided file format. The feedback shall be categorised as defects or enhancements and provided daily on mutually agreed time. Any error due to which the actual results deviate from expected results as defined in the signed off BRD shall be considered as defect. Any addition to the signed off BRD shall be considered as enhancement.
User Acceptance Testing. (UAT) User Acceptance Testing (UAT) is formal testing by the Health District to validate the system is working per the project scope. Throughout the project, the Health District is expected to test components of the system as they are completed (i.e., configuration, reports, interfaces, etc.). Prior to UAT, the teams will establish a configuration and development code freeze on the test environment. As all components should have already been tested and validated during the Define and Develop stages, UAT should focus on end‐to‐end testing of the Health District’s full business processes as they would perform in production. User Testing includes the following distinct phases:
User Acceptance Testing. UAT 79 9.1.6 Mocks & Rehearsal 79 9.2 INCIDENT REPORTING PROCESS 79 10. CHANGE CONTROL PROCEDURE 81 11. KNOWLEDGE TRANSFER 82 12. FACILITIES 82 13. ASSUMPTIONS 83 13.1 PERSONNEL 83 13.2 PHYSICAL ENVIRONMENT 83 13.3 BACKUP & RESTORE (ON-PREMISE) 84 13.4 PROJECT SPECIFIC ASSUMPTIONS 84 13.5 PROPOSED PAYMENT MILESTONES 84 14. APPENDIX 85 14.1 MIGRATION ACTIVITIES 85 14.2 MIGRATION DELIVERABLE 86 15. ATTACHMENTS 1&2 FUNTIONAL REQUIREMENTS MATRIX 87
