Laserfiche WebLink
2.3 Implementation Scope <br />Implementation Scope defines the product features and development items that will be <br />implemented by the project team during the City's implementation. The following elements of <br />scope are included in the sections that follow: <br />• Requirements Traceability — the purpose and associated deliverables and activities related to <br />requirements traceability are described in Section 3.1. <br />• Application Configuration - the City license agreement includes a list of Oracle Cloud software. <br />The scope of implementation services will be to license and configure the necessary Oracle <br />modules and third -party applications identified in Section 3.2 to successfully meet the <br />Requirements listed in Exhibit B of this SOW. <br />• Reporting and Dashboard Development — Section 3.3 describes the scope of Reports and <br />Dashboards. <br />• Interface Development — the City and CherryRoad have established a scope interface <br />development between the Oracle Cloud software and the City's third -party systems. Section <br />3.4 describes the scope of interfaces. <br />• Conversion Development — the City and CherryRoad have established a scope of legacy data <br />to be converted into the Oracle Cloud software. Section 3.5 describes the scope of <br />conversions. <br />• Training — CherryRoad's End User Training scope and approach is described in Section 3.6 <br />12.4 Requirements Traceability <br />The primary purpose of Requirements Traceability is to ensure that the CherryRoad responses <br />to the Citys requirements identified in Exhibit B, are validated throughout the implementation <br />lifecycle. In addition, as new requirements are identified, the implementation team will track and <br />document them. This section describes the stages and associated deliverables and milestones <br />within the implementation methodology which the CherryRoad and City team will utilize to validate <br />requirements traceability. <br />The table below lists each of the implementation stages and deliverables which are utilized as <br />gateways for requirements traceability. <br />P01 Initial Project <br />Startup <br />F03 Gap Analysis <br />PO4 Project Scope <br />Document <br />EXHIBITA STATEMENT OF WORK <br />ATTY/AGR/2019.118/CHERRYROAD ERP IMPLEMENTATION SERVICES <br />REV: 05-13-19 PR Page 29 of 172 <br />Requirements are loaded into a <br />Requirements Traceability <br />Matrix (RTM) <br />Development items are <br />identified and documented with <br />corresponding requirements <br />Revised Requirements list is <br />codified and memorialized. <br />RTM is updated. <br />A-15 <br />