Overview

Background

This project is for the planned annual upgrade of Learn VLE platform.

Learn is the main centrally supported Virtual Learning Environment, and is used to underpin over 4500 courses, including campus based, and wholly online Masters level courses.

As Learn is a top priority service for the University we aim to have an uptime of 99.7% (combined planned and unplanned availability). A key part of ensuring that the platform reaches the availability target is making sure that we are on a stable and supported version. The supplier recommends keeping up to date with service packs to reduce performance issues.

Scope

Annual upgrade of Learn platform to stay on supported version. Takes place in Semester 2 for delivery into production in July to fit with teaching pattern.

The project will:

• Upgrade the Learn platform to v 9.1 Q4 2017  plus cumulative updates (if any) applied

  • There will be a further release coming out early 2018 but the actual date is still unknown. However because it is full of attractive features LTW would like to move to this version if at all possible.
  • LTW will monitor when the next release will happen and if timescales allow we will update to this version
• Check if Spring and Java require updating and update as necessary
• Update the Custom Building Blocks

• Test and fix any UoE Building Blocks that do not work with the upgrade
• Test and fix any issues with data feeds (excluding Timetabling who manage their integration)
• Test and fix any issues with the MyEd uPortal Learn Channel

• Production will run a security scan on the application for vulnerabilities

The set-up of environments will be done in parallel with the Building Blocks development work.

Not in scope

• The cost of updating the building block for Timetabling. The cost of this will be met by Timetabling but the building block will be tested at the same time as the other building blocks and has to be planned in.
• Upgrading servers from Centos 6 to Centos 7 - End of life is 2020 however we should be aware of when our teams will end support. This will be clarified with ITI.

• Learn moving to the Cloud - not at a stage to currently consider – will not be pursued as part of this project.

Objectives & Deliverables

The deliverables are prioritised using the MoSCoW prioritisation method:

M=Must Have; S=Should Have; C=Could Have; W=Want

• (M= has to be satisfied for the final solution to be acceptable in terms of delivery dates, compliance, viability etc.
• S= high-priority requirement that should be included if possible -workarounds may be available
• C= a nice-to-have requirement
• W= want but will not be part of this project)

Benefits

Success Criteria

• A successfully upgraded and integrated Learn platform to v 9.1 Q4 2017 (or the 2018 release) with cumulative updates (if any) applied
• All bespoke Building block working with the upgrade
• All data feeds and uPortal channel working with upgrade
• Application successfully scanned for vulnerabilities
• Infrastructure reviewed and meets service requirements

Project Milestones

(Please copy and paste from Milestones log)

Note:

• A security scan will be completed on both Test and Live environments
• The Test environment needs to be available at least one month prior to Live deployment as LTW need to update for documentation and to carry out UAT

There is a hard delivery milestone date as the system has to be ready for the start of the academic session 2018/19 and the window for non-teaching is very narrow. The entire Learn community was consulted to agree the deployment date and to agree to a change of date, any communications of a change of deployment would have to be done ASAP and preferably 6 months in advance.