Laserfiche WebLink
!`' SMARTWORKS <br />• The actual result observed after performing the test `Test Result" <br />Prior to commencing Functional Testing and Integration Testing activities, the Test Scripts and Test <br />Acceptance Criteria will be documented in TeamSupport by SmartWorks using Test Scripts that have been <br />defined by SmartWorks. <br />While performing testing activities, the tester will update the TeamSupport with the Test Result and will <br />make a determination as to whether the result meets the Test Acceptance Criteria. <br />Functional Testing and Integration Testing will be performed by SmartWorks. User Acceptance Testing <br />will be performed by Customer with support from SmartWorks. <br />5.4.1. User Acceptance Testing Procedure <br />Once Functional Testing and Integration Testing have been completed, and Customer staff has received <br />Functional Process Training, Customer staff will have the necessary tools to perform User Acceptance <br />Testing. <br />Prior to commencing User Acceptance Testing activity, the Test Scripts and Test Acceptance Criteria will <br />be documented in TeamSupport by SmartWorks collaboratively with Customer. <br />Customer will have its own instance of The SmartWorks Software, loaded with its data, to train and test <br />on. The Application SmartWorks assigned to Customer will provide the documents and training of the <br />system to the staff. Training will be conducted onsite and using WebEx sessions, phone calls and <br />documentation as needed. <br />Customer will have a defined period of time to perform User Acceptance Testing on the Solution (including <br />testing in a live production environment) (the "Acceptance Testing Period"). The length of the Acceptance <br />Testing Period will be defined in the Detailed Project Plan. This User Acceptance Testing Period will begin <br />upon formal written notification from SmartWorks to Customer that the SmartWorks Software has been <br />configured and is ready for testing. During such Acceptance Testing Period, both Parties shall work <br />diligently and dedicate the appropriate resources to conclude the evaluation in a timely and efficient <br />fashion. <br />If the Solution substantially meets the Functional and Integration Requirements Document, and <br />substantially satisfies the testing criteria set forth in TeamSupport (together the "Solution Acceptance <br />Criteria"), Customer will provide SmartWorks with written acceptance notice thereof, and the date of <br />such notice to be the "Actual Solution Acceptance Date". <br />In the event Customer determines that the results of a test do not meet the Solution Acceptance Criteria, <br />following the initial User Acceptance Testing cycle, Customer will provide SmartWorks with written notice <br />thereof, specifying in reasonable detail how the Solution failed to meet the Solution Acceptance Criteria. <br />If Customer delivers to SmartWorks such notice of retesting, SmartWorks shall make all necessary <br />corrections, repairs, fixes, modifications, or additions to or replacements of all or any part of the rejected <br />SmartWorks Software as well as integrations for which SmartWorks is responsible so that it conforms to <br />and performs in accordance with the Solution Acceptance Criteria. SmartWorks will have a defined period <br />City of Santa Ana—SmartWorks Statement of Work <br />25H-/ v Page71 <br />