1 / 30

The New MyUCLA An Integrated Web Experience for Student Services

The New MyUCLA An Integrated Web Experience for Student Services. Arun Pasricha Christian Spreitzer Praveen Dugar Donny Morada. August 5, 2014. Agenda. Objectives Approach and Architecture Governance and Management Structure Demo of MyUCLA Questions.

dylan
Télécharger la présentation

The New MyUCLA An Integrated Web Experience for Student Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The New MyUCLAAn Integrated Web Experience for Student Services Arun Pasricha Christian Spreitzer Praveen Dugar Donny Morada August 5, 2014

  2. Agenda • Objectives • Approach and Architecture • Governance and Management Structure • Demo of MyUCLA • Questions

  3. The Need for Integrated Web Experience • Rich functionality broken along organizational lines • Dated and fragmented web presence • Each organization’s website with a unique user interface Student Experience

  4. The Need for Integrated Web Experience • Transactional workflows required multiple websites to complete my.UCLAClass Planner RO Schedule of Classes URSA Enrollment

  5. The Need for Integrated Web Experience • Student concerns over lack of unified web presence (Daily Bruin Editorial, April 14, 2005) “The fragmentation is hardly useful and, as the pace of Internet innovation has quickened, UCLA looks painfully stuck in 1997” • Multiple Student Focus Groups had raised similar concerns Rated #3 institutional IT priority by campus in January 2007

  6. The new MyUCLA – An Alternate Approach • UCLA has a highly distributed development model • Integration using portal software or a centralized website disruptive • Integrate while maintaining current architecture and hosting • Minimal changes – shorter turnaround times • Faster adoption across campus • Cost effective

  7. The new MyUCLA – An Alternate Approach • Unify functionality using • New consistent, seamless presentation tier • New global navigation menu • Existing single sign-on (SSO) capability URSA my.UCLA my.FAO my.Housing Consistent Presentation Tier and Navigation New User Experience At UCLA

  8. The New MyUCLA Phase 1 Kicked Off – November 2011 Successfully Deployed – October 2013 MyFAO Shutdown on April 15, 2014URSA Shutdown on May 12, 2014

  9. The new MyUCLA – Scope of Phase 1 • Setup Governance Structure • Integration of MyUCLA, URSA and MyFAO • Development of: • Consistent presentation tier components • Common infrastructure components • Template for integration of additional Student Services

  10. Governance Structure Steering Committee Student AffairsIT Services Gorden Monroe – AVC Andrew Wissmiller – AVC Arun Pasricha – Director SAIT Edith Celestine – Director, Student Apps Frank Wada – University Registrar Shan K. – Director, Architecture, IT Services CollegeGraduate Division Betty Glick – Associate Vice Provost Sam Bersola – AVC Chris Spreitzer – Director UIT Chris Testa – Director IT, Grad Division Technical Architecture Team Student AffairsIT ServicesCollege Arun Pasricha Albert Wu Chris Spreitzer Praveen Dugar Shan Kandaswamy John Hirning Donny Morada Jinnah Sultan Bruce Dumes

  11. Presentation Tier – Page Element: Header • Common Header • Global navigation menu • Organizational Logo for branding • Message Link with # of Messages • Action Items • User Name, Login Status • Search Bar

  12. Presentation Tier Page Element: Content Area • Various options forcontent area layout • Information/function in content area is a “feature” • Feature specific menuin content area Option 1

  13. Presentation Tier Page Element: Content Area • Split Pane View:Right pane availablefor Quick Links, Overview or Images Option 2

  14. The New MyUCLA – Modern Interface

  15. The New MyUCLA – Consolidated Functions • Consolidated View of Functions from MyUCLA, URSA and MyFAO

  16. Presentation Tier – Design Repository • Online Repository for MyUCLA Design Elements (https://studentweb.it.ucla.edu/iwe/home.html)

  17. Common Infrastructure Components • Roles delivered from Enterprise Directory via Shib (IT Services)–defined and maintained by role owners • Menu Service (College) – web service returns list of supported features to build Mega-Menu • Notices & Alerts (Short term: College; Long term: IT Services) – supports various types of messages delivered and tracked • Profile Service (IT Services) – returns common user attributes

  18. Common Infrastructure Components • Auditing Service (IT Services) – logs consistent business use of features • New Enterprise Directory Instance in QA(IT Services) – allow impersonation for testing • Class Search (Student Affairs; IT Services) • New Enrollment Workflow (Student Affairs; IT Services; College) • Common Code Repository – Use TFS with Git

  19. Service Oriented Architecture • Defines functionalities as accessible services • Easily provides frequently used data and functionality • Enterprise Service Bus (ESB) Integration • Middleware component required for SOA • Provides consistent interface to access services • Used to provide synchronized menu data to all organizations

  20. Service Oriented Architecture • Enterprise Service Bus (ESB) Integration

  21. Role Definitions • Define roles and source of data - managed by role owner • Define Enterprise Roles versus Local Roles • Use roles to provide customized view of features • Available in Enterprise Directory via Grouper

  22. Sample Roles

  23. Default Home Feature – Landing Page • Site/content based on user persona (roles) – core to the entire development and integration • Default (home) feature for different user roles • Hierarchy based on roles and default landing pages are by highest rank for role. Note that users can customize their default landing page which trumps this. Students3rd PartyEmployees New Admits Parents FacultyContinuing Guardians StaffAlumniSummer SessionExtension

  24. Integrated Notification and Messaging • Personalized alerts based on roles and permissions • Notices • Feature Alerts • Action Required Widget

  25. Student Lifecycle in MyUCLA

  26. MyUCLA Demo

  27. The New MyUCLA – Campus Impact “The start of Spring Quarter is great thanks to the new MyUCLA format. It’s nice that everything is on a central platform. It’s very efficient and makes things a lot easier for me. Thank you!” “Website looks great! Kudos.” “The changes to the study list looks great! Clean and well laid-out of information makes it easier to read… Thanks for the overall great look!” “The integration of URSA into MyUCLA is great” “Wonderful!!!! This no-nonsense and less graphic interface is amazing. Thanks for paring this down to something more usable.”

  28. Questions? • Contact Information: • Arun Pasricha (apasricha@sait.ucla.edu; 310-825-9475) • Christian Spreitzer (cspreitz@college.ucla.edu; 310-206-7223) • Donny Morada (dmorada@sait.ucla.edu; 310-825-3327) • Praveen Dugar (pdugar@sait.ucla.edu; 310-206-5085)

  29. The New MyUCLA – Integrated Workflows Class Selection Apply Search Filters Class Planner + Enrollment

  30. The New MyUCLA – Integrated Workflows

More Related