1. web Trnsport – Beta Testing and Implementation TUG Roundtable Discussion Elizabeth Rodgers Info Tech, Inc. October 9, 2007

2. Topics Web Trnsport Preconstruction Release Schedule Preliminary Release Beta Testing Beta Testing – Pre-install Checklist Beta Testing Tasks Beta Testing Time Frame Agency Implementation & Migration Tasks Helpful Links and Contact Information

3. Preconstruction Release Schedule ReleaseContent Preconstruction Release 1 (“Pre-Production Release”) September ’07 sprint results Preconstruction BetaFebruary ’08 sprint results Preconstruction Release 2 (“Full Production Release”) June ’08 sprint results Actual release dates are dependent on TRT and TTF approvals of sprint results and release deliverables.

4. Preliminary Release (Pre-Production) Evaluation license available to all agencies –No evaluation fee for Release 1 –Provide standard level of evaluation licensee support Early feedback prior to Beta and Production release is important Agencies should contact a TTF member –ttf@cloverleaf.net

5. Beta Testing 3 month beta period (March through May 2008) Beta site mobilization complete at least one sprint in advance Beta begins with February 2008 sprint results –At least 85% of planned business functionality complete March and April sprint results provided to sites –100% planned business functionality in April results –Will also include beta issue resolutions

6. Beta Testing – Pre-install Checklist Agency has the latest client/server Trnsport releases installed for interface testing Agency Cloverleaf access to download software. Agency Team Track access for beta issue reporting. ITI has access to test and development database and web servers.  Validate required client/server interface environment.  Have agency review instructions for the prior sprint in order to identify possible issues with the release sprint

7. Beta Testing Tasks Database install Data migration Web server install Acceptance test execution Agency customizations ‘Day-in-the-life’ testing of base product functionality Interface testing Application of sprint updates

8. Beta Testing Tasks - Detailed For full testing, two concurrent complete installations will be used: Test and Development –Test Delivered Acceptance test validation area –Development Agency specific web Trnsport validation area NOTE: Each database and web site can be set up on the same computer, or separate as needed to follow an agency’s standard environment.

9. Beta Testing Tasks - Detailed For migration testing, only one database will be used; the web server environment won’t be used –‘Migrating to Trnsport’ document will be located on Cloverleaf and will cover database requirements. –The migration process will occur on the Development environment.

10. Beta Testing – Ongoing Activities Testing Issue reporting Resolution validation Status meetings via webinar/conference call between agency and Info Tech (include TTF or TRT as needed)

11. Beta Testing – Primary Resources Required Database Administrator (DBA) Internet Information Services Administrator (IISA) Trnsport Managers and Users

12. Beta Testing – Detailed Resources/Tasks Database install –DBA – creating, modifying, and executing database scripts Data migration –Trnsport data manager – running migration, resolving data issues –DBA – on call Web server install –IISA – perform install and configure server Acceptance test execution –IISA – perform install and execute tests –DBA – on call

13. Beta Testing – Detailed Resources/Tasks Continued… Agency customizations –Users Trnsport system manager Trnsport business manager IISA – if needed to provide access to server –Changes Page layout Data validation Report customization

14. Beta Testing – Detailed Resources/Tasks Continued… ‘Day-in-the-life’ testing of base product functionality –All types of Trnsport users –IISA – on call –DBA – on call Interface testing (standard interfaces to other Trnsport modules) –Trnsport data manager

15. Beta Testing – Detailed Resources/Tasks Continued… Application of sprint updates –DBA – apply database updates –IISA – apply web server updates and run acceptance tests –Trnsport users – end user testing

16. Beta Testing Time Frame Phase 1 – Agency acquire and install hardware and software required for beta testing –February 2008 timeframe Phase 2 – receive sprint –March 2008 timeframe – beta testing begin Web Install Database install Migration testing Application testing TTF requests beta site volunteers by November 16, 2007

17. Agency Implementation & Migration Tasks

18. Implementation and migration planning Technical training, if required Acquire, install, & configure hardware and software Install web Trnsport Configure system (workflows, installation options, etc.)

19. Agency Implementation & Migration Tasks Continued… Migrate data from existing system Create new required data (e.g., new code tables) Customize user interface and reports Apply existing agency customizations Testing throughout the installation and migration process

20. Agency Implementation & Migration Tasks Continued User training –web Trnsport should be easier to train new users –Encourage the use of web Trnsport online help –web Trnsport and PES/LAS client/server differences document is included with the software –Info Tech services are available Parallel testing Production

21. Helpful Links and Contact Information Email TTF: –ttf@cloverleaf.net http://www.cloverleaf.net/NGT –web Trnsport logical architecture paper –web Trnsport preview site –Summary of changes between web Trnsport and client server –Preconstruction product backlog –Hardware and software requirements Info Tech Demo Room –Located in the Lewis & Clark room –web Trnsport overview document Including beta requirements guide

22. Questions?