WebVista Version 3 to WebVista Version 4 Upgrade Roadmap

Test version 4.

5/10: Notify community of upgrade plan and roadmap.

5/11: Test X.500 authentication.

Give UTELL access to test instance of version 4 when X.500 authentication is in place.

Update name to WebVista.

Prepare scripts for performance testing.

Determine full communication plan by 5/18.

6/15: Test course management tool.

6/15: Test PowerLinks.

Test portal integration.

Test autofetch.

Support UTELL and early adopters.

Move content to version 4 test cluster as requested for testing.

Upgrade administrative procedures and forms.

Finalize upgrade date for WebVista B.

Test production server.

Open production version, when available, to faculty and designers.

8/10-12: Support upgrade of WebVista B to Version 4

Work with systems staff on WebVista B upgrade.

Facilitate upgrade.

Create version 4 sites for fall 2007 after upgrade date.

Assist faculty and staff with upgraded sites.

Carry out communication plan and communicate with individual departments.

Update support documentation and 1-HELP and support Web sites (beginning with instructor/designer support).

Participate in upgrade beta program.

Integrate X.500 authentication by 5/11.

Install powerlinks on test cluster by 6/15.

6/18: Begin to prepare production cluster hardware based on results, preliminary and ongoing, of performance testing.

Determine new archive/restore methodology.

Upgrade course management tool.

Integrate portal.

Integrate autofetch.

Begin performance testing against both migrated and “clean” data.

8/10-12 Perform upgrade of WebVista B to version 4.

Develop in-house upgrade tool.

Compare version 4 with version 3.

Deliver face-to-face classes (beginning in June): Orientation, Basics, Gradebook.

Update training materials.

Access and use version 4 test environment as available.

Assist faculty with decision making and adjustment to version 4.

Work with support staff to address specific technical requirements.

Provide feedback to OIT.

Access and learn version 4.

Provide feedback and assist with testing.

Update internal documentation.

Work with faculty and designers on version 4 application of new tools, design decisions, and teaching and learning issues.

Incorporate version 4 into faculty development programs.

Learn and communicate how new tools in version 4 provide new ways to promote and assess learning.