Laserfiche WebLink
Performed after software installation to demonstrate to the City that core product functionality is in place <br />and use of the software can begin. <br />.1.10.2 Static Environment Testing (SET) <br />This is performed once the City has made preliminary Best Practice decisions. The purpose of the test is <br />to provide an early opportunity to the City for validation of business process decisions in the actual <br />application, without the complication of converted data. This pristine testing environment allows <br />decision- makers to focus on process flow without the potential impact of converted data. A key part of <br />the test is to conduct a "five -day" transaction test, during which all activities that take place in a standard <br />week are duplicated and tested. This testing is a key milestone that dictates whether Core User <br />Documents can be written and data population can begin. <br />D.1.10.3 Validation <br />This is performed after each pass of converted data is loaded into a testing database. Use of control <br />reports, filtering techniques, comparison reports and visual inspection are all part of this process. The <br />purpose is to identify all issues with data, whether due to mapping inconsistencies, source data issues, <br />data submission content or conversion programming errors. Acceptance of conversion programming <br />must be completed long before the pre -live period so that final conversion submissions have little or no <br />risk of data or conversion programming issues. Final acceptance is necessary prior to live processing as <br />the last step before data is loaded in the live database and live processing begins. This testing is part of <br />pre -live assessment. <br />D.1.10.4 o d <br />This is performed in an isolated environment once modifications are delivered. The modification is unit <br />tested first to ensure compliance with specifications and to validate the performance of the coding. Once <br />unit testing is completed successfully, the modification is tested for integration performance as part of an <br />overall process, paying special attention to any impact on touch points throughout the product. After <br />successful integration testing, modifications are exposed to setup data and converted data by replicating <br />the fully populated databases in the test environment. After successful testing, authorization is requested <br />to load the modification into the production environment. Testing continues throughout the balance of the <br />project to ensure the integrity of the modification. This testing is part of pre -live assessment. <br />1 <br />This is first performed in a test environment at Tyler, prior to delivery of forms to the City, using sample <br />data extracted during the Static Environment Test. Once Form design has been accepted and forms are <br />loaded on the City's server, testing continues throughout the balance of the implementation. The goal, at <br />a minimum, is to print forms as part of training (Core and End User) so that both the content and process <br />are validated repeatedly. Submission of forms to banks must be completed and acceptance received a <br />minimum of thirty days before live processing. This testing is part of pre -live assessment. <br />1 I �r, <br />CITY OF SAN MARCOS, TX PAGE 44 OF 62 <br />ERP PROJECT- FINAL SOW <br />