Laserfiche WebLink
• Database Crosswalk Schema Document <br /> . Conversion of Cassworks data only <br /> • Agreed upon Key data from all Cassworks Service Requests and Work Orders will be converted in this effort <br /> Phase 7,Task 22:Assumptions: <br /> • City will provide a conference room appropriately sized for the number of participants and review all <br /> documentation within 10 business days. <br /> Phase 7,Task 22:Estimated Timeframe: <br /> The conversion of the legacy data will require approximately 10-14 weeks <br /> Phase 7 Exit Criteria <br /> . Data Conversion orientation workshop <br /> . Database Crosswalk Schema document <br /> . Conversion of Cassworks Oracle database <br /> Phase 8: User Acceptance testing <br /> Phase 8, Task 23: Develop Testing and Acceptance Plan <br /> The implementation team will work with the City to develop and administer a Testing and Acceptance <br /> Plan that addresses User Acceptance Testing (UAT). Testing and Acceptance Plan objectives shall <br /> remain consistent with the application functionality detailed in the System Design and Configuration Plan <br /> and Application Design Document (for enterprise interfaces). The Testing and Acceptance Plan will <br /> address, in sufficient detail (as collectively deemed by the City and the implementation team) the <br /> elements required to support the City's testing of the Cityworks software functionality and database <br /> configuration, security matrix, documentation of application performance issues/errors experienced during <br /> the testing, documentation of the resolutions to noted issues/errors, and certification and acceptance of <br /> the final deliverable database configuration and software functionality. This will include testing for <br /> Cityworks Office, Respond and Mobile app. <br /> The test server and final production server environments will be measured against the results of the <br /> testing performed in accordance with this Testing and Acceptance Plan (for UAT only), and it is the <br /> baseline to which the scoped projects tasks will adhere. The Testing and Acceptance Plan (UAT only) <br /> shall be subject to the review and acceptance as to its reasonableness for its intended effort, which is <br /> defined herein as the ability to support the logical and thorough testing of the Cityworks application <br /> functionality, platform stability, and database configurations. <br /> Upon completion of development of the Testing and Acceptance Plan (UAT only), the Team shall submit <br /> said plan to the City for review and approval. It is important for City staff to review the draft plan for <br /> technical accuracy and completeness. Our configuration team will update the Draft Testing and <br /> Acceptance Plan, incorporating City comments and re-submit said plan as Final. <br /> Phase 8,Task 23:City Responsibility: <br /> • Review and comment on plan. (4-8 FTE Hours Per Functional Group) <br /> . Identify and assign for user Acceptance Testing(UAT) <br /> . Perform UAT <br /> Phase 8,Task 23:Timmons Group Responsibilities and Deliverables: <br /> • Testing and Acceptance Plan drafts and final. <br /> . Addressing functional requirements not met/revealed by UAT that do meet defined functional requirements <br /> Phase 8,Task 23:Assumptions: <br /> o City will review all documentation within 10 business days or mutually agreed upon timeframe. <br /> Phase 8,Task 23:Estimated Timeframe: <br /> s The development of the Testing&Acceptance Plan will require 4-6 weeks <br /> Phase 8, Task 24: Acceptance Testing <br /> Prior to Go-live there will be a thirty (30)day acceptance testing period (the acceptance period is flexible <br /> based on input from the City's Project Manager). During this period the City will test the Cityworks <br /> 33 ( Page <br />