Schedule F User Acceptance Testing.docx

SCHEDULE F

User Acceptance Testing The parties agree as follows:

Definitions. For purposes of this Schedule, the following terms have the meanings set forth below. All initial capitalized terms in this Schedule that are not defined in this Section 1 have the respective meanings given to them in the Contract.

“Acceptance” has the meaning set forth in Section 3.5 of this Schedule.

“Acceptance Tests” means such tests as may be conducted in accordance with Section 3 of this Schedule and the Statement of Work to determine whether the Software meets the Requirements.

“Defect” means any failure or failures of the Software, or any API, to conform to the Requirements, and any applicable specifications set forth in the Documentation.

“Integration Testing” has the meaning set forth in Section 3.1(c) of this Schedule.

“Requirements” means the State’s business and technical requirements regarding the features and functionality of the Software, which are set forth in the Statement of Work.

“SUITE” means the State Unified Information Technology Environment, which was designed and implemented to standardize methodologies, processes, procedures, training, and tools for project management and systems development lifecycle management.

“Test Data” means Contractor’s or the State’s test data and testing scripts for use in Acceptance Testing during UAT.

“Test Environment” means the operating environment created by Contractor for purposes of UAT.

“Testing Period” has the meaning set forth in Section 3.1(b) of this Schedule.

“Test Results” means the results Contractor or the State expects to be achieved by processing the Test Data using the Software.

“UAT” means User Acceptance Testing.

“UAT Plan” means Contractor’s written plan outlining the UAT schedule, procedures for logging Defects and tracking corrections and re-testing status.

Parties Obligations for UAT.

Contractor Obligations. Contractor will complete the following tasks as part of UAT:

Install, configure and deploy the Software into the Test Environment;

Install, configure and deploy all API and related Equipment necessary for the Software to fully function in accordance with the Requirements;

Create and provide to the State sufficient Test Data and Test Results to adequately test the Software end-to-end, including testing of any APIs, Hosted Services, and Equipment for purposes of Integration Testing;

Review any State-created Test Data and provide necessary feedback to the State;

Assist the State with completing any necessary SUITE documentation;

Communicate to the State that the Testing Environment is ready for use prior to initiation of Acceptance Tests;

Create a written UAT Plan;

Train State staff on how to perform Acceptance Tests using the UAT Plan.

Correct Defects in Test Results in accordance with Section 3 of this Schedule, which are identified by Contractor or the State during the testing Period;

Conduct regular status meetings during UAT to assess Test Data and Test Results; and Provide a tracking system for Contractor and the State to log Defects and track corrections and re-testing status.

State Obligations: The State will complete the following tasks as part of UAT:

Create its own Test Data for use in UAT;

Develop and add approved tests to the UAT Plan;

Execute tests and report Test Results to Contractor in accordance with the UAT Plan;

Participate in regular testing status meetings;

Enter defects from Test Results into the Contractor-provided issue tracking system. Details to be entered include a minimum of: (i) detailed description of the problem (include screenshot(s) if applicable); and (ii) steps needed to reproduce the issue;

Perform regular retest of Contractor resolved defects based on mutually agreed schedule; and Work with Contractor to prioritize issues that arise during UAT.

Acceptance Testing; Acceptance.

Acceptance Testing.

Unless otherwise specified in the Statement of Work, upon installation of the Software and direction from Contractor that the Software is ready to be tested by the State, acceptance tests will be conducted as set forth in this Section 3 to ensure the Software conforms to the requirements of the Contract, the Statement of Work, and the applicable Requirements.

All Acceptance Tests will take place at a designated State facility, with remote access to the Software, commencing on the Business Day following Contractor’s notice that the Software is ready to be tested by the State, and be conducted diligently for up to thirty (30) Business Days, or such other period as may be set forth in the Statement of Work (the “Testing Period”). Acceptance Tests will be conducted by the State, and if requested by the State, Contractor will make suitable Contractor Personnel available to assist or guide such Acceptance Tests. Contractor is solely responsible for all costs and expenses related to Contractor’s performance of, participation in, and observation of Acceptance Testing.

All APIs and Equipment must be delivered at the same time as the Software, and Acceptance Tests will also be performed on the integrated Software, APIs and Equipment as a whole to ensure full operability, integration, and compatibility among all elements of the end to end system (“Integration Testing”).

The State may suspend Acceptance Tests and the corresponding Testing Period by written notice to Contractor if the State discovers a material Defect in the tested Software or part or feature of the Software. In such event, Contractor will immediately, and in any case within ten (10) Business Days, correct such Defect, whereupon the Acceptance Tests and Testing Period will resume for the balance of the Testing Period.

Notices of Completion, Defects, and Acceptance. Within fifteen (15) Business Days following the final completion of all Acceptance Tests, including any Integration Testing, the State will prepare and provide to Contractor written notice of the completion of the tests. Such notice must include a report describing in reasonable detail the tests conducted and the results of such tests, including any uncorrected Defect in the tested Software.

If such notice identifies any Defects, the parties’ rights, remedies, and obligations will be as set forth in Section 3.3 and Section 3.4 of this Schedule.

If such notice identifies no Defects, such notice constitutes the State’s Acceptance of such Software.

Failure of Acceptance Tests. If Acceptance Tests identify any Defects, Contractor, at Contractor’s sole cost and expense, will remedy all such Defects and re-deliver the Software, in accordance with the Requirements. Re-delivery will occur as promptly as commercially possible and, in any case, within fifteen (15) Business Days following, as applicable, Contractor’s receipt of the State’s notice under Section 3.2, identifying any Defects.

Repeated Failure of Acceptance Tests. If Acceptance Tests identify any Defect in the Software after a second or subsequent delivery of the Software, or Contractor fails to re-deliver the Software on a timely basis, the State may, in its sole discretion, by written notice to Contractor:

continue the process set forth in this Section 3; or deem the failure to be a non-curable material breach of this Contract and the Statement of Work and terminate the Contract for cause.

Acceptance. Acceptance (“Acceptance”) of the Software (subject, where applicable, to the State’s right to perform Integration Testing) will occur on the date of the State’s delivery of a notice accepting the Software under Section 3.2(b) of this Schedule.