1. Class Schedule Project Update
ACNS and Registrar’s Office staff

2. Agenda Background & Project Timing Status & Issue
Options Going Forward
Discussion
4/21/2014
UTFAB Presentation

3. Project Background
UTFAB-funded applications developer hired Oct (E. Burr)
Class schedule redesign determined top priority
Enhancement to complex commercial software
Other small projects done in parallel
Original scope for project
Class schedule interface redesign, wishlist
Included extensive input from UTFAB
Logical enhancement, and perceived within reach
Quick (one-button) registration from wishlist
4/21/2014
UTFAB Presentation

4. Project Timeline Fall 2012 Requirements gathering
4/21/2014
Fall 2012
Requirements gathering
Deeper understanding of vendor delivered self service (SSB) architecture
Began development
Spring 2013
Development and testing
Additional considerations
Advisors, RO usage of the initial class schedule application
Extensive user testing
UTFAB Presentation

5. Project Timeline (cont’)
October 2013 ‘soft launch’ during low volume time
Extensive testing continued in production environment
RO staff and 200 students
Safari ‘feature’ discovered, application pulled from production after 1 week
Detailed debugging continued from October to February
Involved RO and ACNS developers, Ellucian and original author of authentication method
4/21/2014
UTFAB Presentation

6. The Issue Application works extremely well with one exception…
When using Safari
Registration works the first time, subsequent submissions for registration log the user out
Cookie management/access issue
Firefox development roadmap includes same cookie management strategy; problem will get larger over time
In April of 2014, 1/4 of logins into RAMweb come through Safari
4/21/2014
UTFAB Presentation

7. Options Going Forward
#1 - Move forward with full release of application, including registration
Could notify safari users upon login and warn them of the issue (new development effort)
Could divert safari users to existing system (new development effort)
Inconsistent experience for students
Legacy class schedule will have to be kept in operation
Navigation confusion with two systems in production (new development effort)
‘Return’ function from registration
Releasing software with known defect and no fix
Implementation costs
Final deployment and testing
Ongoing support (updates, bug fixes)
Absorbed by ACNS/RO staff
4/21/2014
UTFAB Presentation

8. Options (cont’)
#2 - Launch as standalone ‘class planning’ service without registration functionality
New class schedule search interface and wishlist (new development effort)
Students will need to transfer course information into legacy registration system
Works with all browsers
Navigation confusion with two systems in production (new development effort)
‘Return’ function from registration
Implementation costs
Similar to #1, but somewhat less because of no registration component
#3 - Hit the ‘pause’ button in favor of Banner XE vendor-delivered application
18-24 months out
Direct resources toward future as window of opportunity narrows
None for now, weaved into later overall XE deployment
4/21/2014
UTFAB Presentation

9. New Ellucian Registration
4/21/2014
UTFAB Presentation

10. Discussion!
4/21/2014
UTFAB Presentation