V18 Upgrade Timeline for Task Groups
November/December 2006
- ITD meets with ExLibris Project Manager for initial V18 discussions
- New groups are formed (AV18, Tech, PDQ)
- ITD prepares test server for installation
January 2007
- ITD prepares testing environment:
- test upgrade process
- test Oracle database upgrade to V10
- determine roadmpa for migrating to oracle data (tables, indexes, triggers)
- begin review of upgrade instructions, manually adjust tables, html, xsl as needed
- begin planning STP process/timing
- ITD test basic functionality and connectivity
- V18 release notes posted to web
- PDQ Test group formed
February 2007
- Communication/reporting methods developed for reporting test results
March 2007
- March 16: ITD completes setup of V18 Testing Room (McKeldin BO111A)
- March 16: Testing groups can begin scheduling Testing Room (contact larnhold@umd.edu).
- March 16: Task Groups receive charges from AV18
- March 19-30: Test groups prepare testing scenarios (complete before expert testing in April).
- ITD packages test clients for distribution via Campus Contacts
- ITD performs initial testing of environment including loaders and extracts
April 2007
- Reload full test database
- April 12: ITD releases test client
- V18 test environment released to testing groups (2 weeks)
- April 16: Expert testing begins
- PDQ Critical Path
- PDQ has two weeks to level one decision: Will PDQ work for USMAI?
- continue with testing PDQ?
- move to PPH testing?
- split group to PDQ and PPH testing
- Phase 1 is directed testing by expert testers (Task Groups), test new adn customized functionality (i.e. PDQ)
- April 27th: Testing Groups complete testing
- April 27th: PDQ Critical Path Decision level 1 to AV18
- April 30th: Testing Groups submit testing reports to AV18
May 2007
- May 1: AV18 reports to CLD on PDQ status
- May 7: ITD releases test clients via Campus Contacts
- May 14: General Testing begins
- May 14: Experts support General Testing
June 2007
- June 4: General Testing completed
- ITD releases live clients, campus staff install for all staff who will use ALEPH live
- June 4: Expert re-testing begin if necessary
- All year-end close outs perfomred before moving to V18.
July 2007
- Bring V16 down
- Perform V18 upgrade
- Release V18
- Begin parallel indexing (if necessary)
 = password protected |