My WebLink
|
Help
|
About
|
Sign Out
11
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2008
>
120208
>
11
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/25/2008 12:20:57 PM
Creation date
11/25/2008 11:09:15 AM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
STAFF REPORTS
DOCUMENT DATE
12/2/2008
DESTRUCT DATE
15 Y
DOCUMENT NO
11
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
40
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
EXHIBIT A-2 <br />Approach, Tasks and Deliverables <br />2.1 Approach <br />1. The project will be implemented based upon the following phases: <br />A. Project Kickoff, Business Process Review and Project Plan <br />B. Hardware 8c Software Acquisition, L~statlation and Configuration <br />C. Software Integration <br />D. Application Deployment <br />E. Internet Deployment <br />F. Project Closure and System Acceptance <br />1. Project phases will be conducted concurrently when possible. <br />2. Active will use industry standards to implement its solution and apply the same <br />industry standards to a113rd Party products included in the ACTIVE solution <br />3. The City shall conduct a series of Functional Tests at the conclusion of each project <br />phase which meet the conditions stated in the Acceptance Criteria. The tools used by <br />the City for testing functionality may include Test Scripts, demonstrations and/or <br />industry standards for verifying hardware configuration, software installation, etc. <br />a. The City shag provide Active Network with copies of all test scripts and advise <br />them of test results, errors or "bugs" encountered during testing and any <br />variations in system perfonmance. <br />b. These Functional Tests shall not be deemed successfully completed until: <br />i. Variations between System functions and System documentation have <br />been corrected or deemed not critical to the deployment and are to be <br />fixed in a future release; <br />ii. Errors or "bugs" in System functions have been corrected or a <br />reasonable work around hae been implemented. <br />c. In the event that the System does not perform as required during any of the <br />Functional Tests, as per the Acceptance Testing, of the master agreement, and <br />Active Network Js unable to,Jlx any reported problems that failure shall be <br />governed by the terms and conditions agreed to by both parties in the master <br />agreement. <br />4. ACTIVE and the City shall execute a Signoff Process at the successfiil completion of <br />each project phase. <br />2 <br />
The URL can be used to link to this page
Your browser does not support the video tag.