AQUA-METRIC SALES COMPANY (2) - Laserfiche WebLink

Home Browse Search

vo Iry 011, �� 1 I, II Y„!�o-�/��11, �'�l�o�. PI �l� �I� ��U/1� ',�`I'k,N,7f 7� Ilf S The estimated duration to implement the SmartWorks Software within scope is approximately 6 months. The actual duration and scheduling of project activities will be evaluated during the Initiation and Build phase and a detailed baseline Project Plan will be jointly created at that time. A baseline plan will be delivered within fourteen (14) calendar days of the project Kick Off Meeting allowing Customer an opportunity to review the Project Plan over the next ten (10) business days. If Customer does not agree to the proposed Project Plan, Customer and SmartWorks will work collaboratively to develop a mutually agreeable plan within a reasonable timeline. The Project Plan will include a project completion date (the date where project is completed based on the criteria in section 5.7 Project Completion Criteria). The Project Plan will be reviewed periodically during the project and may be revised. Changes to the project completion date may require a Change Order if it is mutually determined that the delay in completion is the fault of the Customer or Customer's third -party vendors. 5A. Valid ion I esting A III road, Systems Testing is an activity that is addressed through all Phases of the SmartWorks Software Implementation Methodology but is the focus of the Testing Phase. To ensure that a quality Solution is delivered to Customer, the Testing Phase focuses on validating that the configured and developed Customer Solution performs per agreed upon requirements for each module. This includes three (3) main testing activities: • Functional Testing to test the core Solution components (Configuration, Interfaces, Reports, and Modifications) against agreed upon requirements as defined in the Functional and Integration Requirements Document based on the test cases and scenarios developed during the Development phase. • Integration Testing to test the end -to -end process based on business processes and scenarios developed during the Development phase. • User Acceptance Testing to provide Customer the opportunity to validate that Solution behaves per agreed upon requirements as defined in the Functional and Integration Requirements Document based on the test cases and selected scenarios collaboratively developed with Customer during the Development phase. User Acceptance Testing sign -off per agreed upon criteria is necessary to move to Deployment phase. The progress for performing the three (3) testing activities will be logged into TeamSupport. At a minimum, the Tea mSupport will include the following information: • The test name • The objective for performing the test • A Description of the steps required to perform the test `Test Script" • The expected result that will demonstrate the test is successful `Test Acceptance Criteria" City of Santa Ana—SmartWorks Statement of Work 25H-77 Page 70