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 two (2) weeks 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. (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. 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. 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. This deliverable is comprised of the assistance Xxxxx will provide to allow the Agency to accept that the solution meets the requirements as documented in all the deliverables. Xxxxx 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. Xxxxx will provide 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 Automation solution are operating properly (i.e., integration testing). Xxxxx will provide assistance to the Agency as needed by providing User Acceptance Testing (UAT) support and a defined testing process. Xxxxx will address and rectify issues discovered during the UAT process as Agency staff executes testing activities. Xxxxx will work with the Agency to develop a test plan, as well as an issue log to track the progress of testing. It should be noted that Xxxxx will plan for a total of 1 week to complete this deliverable. Xxxxx will work diligently with Agency to ensure adequate time and staffing to UAT in order to completely test the solution and provide several opportunities for the Agency to add additional staff and time to this effort before recommending a postponement or delay. 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 Xxxxx has allotted up to 40 hours for this effort Xxxxx Responsibilities: Provide recommendations on testing strategy and best practices. Lead the Agency in up to 3 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 acti...
User Acceptance Testing. All Product #1 deliverables 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 Product #1 deliverable.
User Acceptance Testing. Contractor shall 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. Contractor shall develop test scripts and data for this test and shall be responsible for final approval of user acceptance test recommendations.
User Acceptance Testing. (UAT) • NorthStar will provide Fairfield UAT test plan and the mCare 6 User Guide for User Acceptance testing. Upon completion of testing Fairfield will submit a signed copy of the UAT test plan confirming all areas of mCare 6 have been successfully reviewed as a prerequisite for NorthStar to schedule the Go LIVE activities. • Fairfield will have two weeks to complete the initial round of User Acceptance Testing. During that two week period NorthStar will work with Fairfield to remediate all priority 1 issues. Fairfield will then have one week of final Acceptance testing prior to scheduling Go LIVE. • If a project delay is encountered due to external factors outside of NorthStar’s control, and User Acceptance Testing needs to extend beyond the initial two week and subsequent one week windows for UAT remediation testing NorthStar and Fairfield will analyze the results of this external factor on the project timeline to determine if there is a need for a change request to reflect a substantial change to the project plan, budget, or timeline. Go LIVE and Go LIVE Support • NorthStar will deploy mCare 6 to production; including clearing the mCare database and repointing to NorthStar production database. • NorthStar will create a copy of the mCare 6 instance which will become mCare TEST. • NorthStar will provided dedicated support for ten (10) business days post Go LIVE before transitioning to NorthStar Support Services. Fairfield Responsibilities Following are the key responsibilities of Fairfield under this agreement: • Purchasing MS-SQL license – if required. • Mobile devices ready to run mCare Field App. • Installing and configuring mCare Field App • Ensuring NorthStar has direct, dedicated remote technical connection capabilities with administration access to any server that the NorthStar applications reside on for the duration of the mCare 6 project • Ensuring that underlying infrastructure for mCare is acquired and installed by the required time per agreed upon project plan (Note: minimum specifications for servers and workstations should be discussed and agreed upon at commencement of project) • Installing server with appropriate network connectivity • Installing operating system and partitioning disk space • Installing database software • Creating users at the operating system level • Installing VPN connection • Configuring back up and maintenance routines for new database • Testing hardware components and environment • Conducting mCare Acceptance testin...
User Acceptance Testing. (UAT) 59
