Laserfiche WebLink
interfaces are developed, a rigorous testing plan will be executed. This scope includes time and cost <br /> associated with integrations via APIs. If it is determined that a less time intensive solution is identified this <br /> option and associated savings will be discussed with the City project manager prior to proceeding. Upon <br /> successful completion of this User Acceptance Testing (UAT), the interfaces are then ready for <br /> deployment. <br /> • Planning— Planning is comprised of a workshop(s)where the implementation team iteratively <br /> works through the reasons for the integration, what data needs to flow back and forth (or <br /> sometimes in one direction), and how best from a technical perspective of how to achieve this <br /> integration (developing requirements). The team then develops these requirements, using <br /> cases/stories and designs the necessary workflows that depict the transfer of data between <br /> systems. The workshop will typically result in the need to engage the target system vendor, either <br /> to procure items such as a database design/schema diagram up to and including engaging their <br /> assistance in designing and developing the integration itself. <br /> • The Build phase of the integration process is here the team develops sprints that are <br /> approximately 'I to 2 weeks in duration that iteratively reflect the use cases/stories and <br /> methodology developed during the previous Planning step. During sprint execution the team <br /> develops code and automated tests simultaneously using techniques such as Test-Driven <br /> Development(TDD), pair <br /> programming and continuous <br /> integration. Once the interfaces qua <br /> ,42 <br /> are developed, a testing plan will x� <br /> be executed. Upon successful <br /> completion of this User <br /> Acceptance Testing (UAT), the HI Requirements <br /> interfaces are ready for Review .Y i <br /> • Training—Our team then works <br /> with the appropriate <br /> User Acceptance <br /> stakeholders to train them both <br /> at the end user level and also to resting <br /> train one or more stakeholders <br /> • <br /> in how the integration was <br /> developed and the management <br /> requirements to keep the t <br /> � is <br /> integration working correctly. *:; . • � 2.4 <br /> • Production Deployment—After <br /> the integration has peens <br /> developed (and tested 4 gym'.; <br /> throughout the development)we <br /> move on to deploying the <br /> integration into the production <br /> environment. Timmons must <br /> provide production deployment cross-training and documentation to Information Technology staff. <br /> • Postproduction System Review—Once the integration is in production the team verifies that the <br /> integration was successful against the requirements defined during the Planning step. Any <br /> identified problems will be addressed and corrected. <br /> 25I Page <br />