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. 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. (If applicable, describe UAT stage) Testing should include: (Describe any testing) (Describe any testing) Ricoh will assist UAT as follows: (Describe any UAT assistance) (If applicable, describe rollout)
6. Support Deliverable: Checkpoint: [Option 1 - IF SOFTWARE SUPPORT IS INCLUDED AND SUPPORTED BY Ricoh:] Support Services Software Maintenance Coverage Customer Roles and Responsibilities Customer Roles Project Manager End User Representative System Administrator Technical Support Facility availability Customer General Responsibilities Customer Technical Responsibilities Other Customer Responsibilities Completion Criteria Acceptance Criteria Change Control Project Assumptions Payment Schedule Budget Notes
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.
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. 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. Within the time frame specified in the applicable Task Order Schedule, Contractor shall deliver to Client a UAT Plan for pre-live testing, including regression testing (“User Acceptance Testing”) of the Software Deliverable that is delivered upon completion of each Task Order (“Task Order Deliverable”), which shall be based upon and incorporate the applicable Acceptance Criteria for each Deliverable included therein. The UAT Plan is a Deliverable subject to Evaluation and Acceptance pursuant to Section 6.2(c)(i). With respect to each Task Order, Contractor shall deliver (or, as applicable, provide access to) the Task Order Deliverable to Client for User Acceptance Testing. Client shall Evaluate such Task Order Deliverable in accordance with the applicable UAT Plan and report, in writing, to Contractor either (A) its Acceptance of such Task Order Deliverable; or (B) its rejection of such Task Order Deliverable setting out in reasonable detail the Defects that constitute the basis for rejection, to the extent that such Defects are discovered upon Evaluation. If Client rejects such Task Order Deliverable, Contractor will Resolve (1) all Severity Level 1 Defects, (2) all Severity Level 2 Defects, provided that with respect to such Task Order Deliverable for which Client identifies a Severity Level 2 Defect, Client may permit Contractor to implement a Workaround until Initial Acceptance at which time Contractor must have permanently Resolved all such Severity Level 2 Defects, and (3) any other Defects, other than Severity Xxxxx 0 Xxxxxxx xxx Xxxxxxxx Xxxxx 0 Defects, identified by Client in accordance with its Evaluation of such Task Order Deliverable that, individually or in the aggregate (x) have a material adverse impact on any use or operation of the Integrated System and/or any member of the user community’s interface with the Integrated System, or (y) arise as a result of a failure of such Task Order Deliverable to conform in all material respects to the applicable Acceptance Criteria, provided that with respect to such Task Order Deliverable for which Client identifies such other Defects, Client may permit Contractor to implement a Workaround until Initial Acceptance at which time Contractor must have permanently Resolved all such other Defects, each as identified as the basis for rejection within the timeframes specified in Section 6.2(d) below, and re-deliver the revised Task Order Deliverable to Client within the timeframes specified in Section 6.2(d)...
User Acceptance Testing. (UAT)
1. Initial Test – a timeboxed phase where the Health District runs through every test script and logs all issues in the issue tracker.
2. Issue Remediation – a time for Accela to remediate all Critical and High issues found during Initial Test, related to the Civic Application solution or tailored configuration. During this time the Health District will remediate all Critical and High issues related to development of custom components (reports/integrations), as they are expected and encouraged to begin taking ownership of the solution in preparation for post go live.
3. Remediation Testing – the phase where the Health District validates that all Critical and High issues have been resolved. The Health District will lead the UAT activities outlined in the UAT Plan. The Health District will test and validate the solution and its readiness to be migrated to production for active use. All test cases should be completed prior to UAT. At completion of Initial Test, Accela and Health District will create a Punch List and agree to Critical and High issues required for remediation before Go‐Live. The Punch List then becomes the focus of remediation and remediation testing. The Punch List will contain issues responsible by both Accela and the Health District, based on which party was responsible for the original configuration/development. The Health District and Accela agree to two (2) rounds of User Testing with the following durations:
Round 1: Initial Testing 2 weeks Remediation 1 week Remediation Testing 1 week Total Duration for Round 1 of UAT 4 weeks Round 2: Initial Testing 2 weeks Remediation 1 week Remediation Testing 1 week Total Duration for Round 2 of UAT 4 weeks It is critical that the Health District devote ample time and resources to this effort to ensure the system is operating per onboarding scope and ready for production. The testing effort will require a significant time investment by the Health District, and the commitment of resources is key to success. Any extensions to User Testing durations will require a change order. If the Health District does not devote adequate time and staffing to User Testing to completely test the solution, Accela may opt to postpone Go‐Live at the Health District’s expense. Accela will work diligently with the Health District to ensure this does not occur and provide several opportunities for the Health District to add additional staff and time to this effort before recommending a postponement or delay. Addition...
User Acceptance Testing. (UAT) 59
User Acceptance Testing. (UAT) Go LIVE and Go LIVE Support Fairfield Responsibilities Engagement Completion Criteria
