Orange County NC Website
Browse       Search
14 <br /> <br /> <br />ClearRisk would complete this as part of an internal validation process (not <br />listed in SOW). This process would be handled completely by Orange County <br />users as part of Data Migration User Acceptance Testing (UAT). <br /> <br />10.2 Application Quality Management <br /> <br />10.2.1 User Acceptance Testing (Application) <br />Orange County user(s) (can be a single user on behalf of the entire team or <br />many users) will be required to carry out user acceptance testing (UAT) on their <br />ClearRisk instance. UAT is comprised of multiple lists of tasks related to the <br />following sections: <br /> <br />● Module Checklist (Mandatory) <br />● Functionality Checklist (Mandatory) <br />● Webform Checklist (Only applicable if webform implementation is a part <br />of the project) <br /> <br />Once completed the Orange County users will send the document back to the <br />ClearRisk project team for review. See appendix F for an example of how the <br />UAT sheet is formatted. User acceptance testing (UAT) will not cover items <br />outside of project scope. <br /> <br />11.0 Implementation Timeline <br />Orange County’s account implementation commences once ClearRisk receives <br />the executed contract and invoice payment. A project kickoff session is <br />scheduled between ClearRisk and Orange County before the commencement of <br />the implementation. Implementations with a similar scope tend to run 16* weeks, <br />but may vary based on the following criteria: <br /> <br />● Complexity in data that results in increased manipulation and upload time <br />DocuSign Envelope ID: BD441C19-1E7C-4FDE-8321-A4585AF240A5Docusign Envelope ID: D2823CF9-24EF-4CAA-AF7E-6E5594A72609