Business Requirements

Functional Requirements

NoRequuirement
1Upgrade the portal software for the Learning Management System (LMS) in line with the latest release of software on the new infrastructure (please note the new infrastructure is running SQL Server 2008 SP3 and Cold Fusion 9)
2Update the new site to use SSL.
3The three environments for Dev, Test and Live must be separated to allow separate authentication methods for the three environments.  In line with the current model the proposal is that Dev is authenticated with Dev EASE while Test and Live will use Live EASE.  This will allow for all current users access to Test when testing or training is required.
4Update the integration method for moving data between the EUCLID EUGEX feeds, ideally moving away from the FTP site using CSV.  Please note that no changes will be required to the feed just the transfer mechanism.
5If possible a new read only account should be created for Application Support to allow users to view the portal without having permissions to make changes.  This will ensure segregation between being able to diagnose problem and being able to affect the system.
 Non Essential Priority Requirements
6

Improved error handling: better messages to users and errors emailed to support or logged where they can be viewed. At present if an error occurs in an ajax requested page, the user will probably see no indication other than an unresponsive page, or blank screen.

7

Extra controls for site admin in assessment to manage submissions and release of feedback, allowing changes made by staff or students to be reversed if required. Some extra screens may be required, e.g. to allow site admins to see assessment for all projects.

8

Allow log in as any user for selected Administration and Support users. A new role should be created for this because it’s not suitable to allow all admins to have this feature

9Create a "Read All" account for Application Support so that they can log into the system and view information without affecting any change.  This will allow more people access where they need to view information but should not affect change on the system.

   

Non-Functional Requirements

AreaRequirement
Performance

It is expected that the performance for the new infrastructure will be different from the existing portal due to the separation of application and database.  Load testing must be carried out to ensure that performance is not degraded beyond a 20% increase in times when the system is not under load:

Current Times under zero load: Log in = 1.3s Page view with normal CMS content =  550ms Main E section – news thumbnails =  859ms News item page =  766ms News manager page =  4.41s Staff – my projects page (small amount of projects)  = 672ms Staff – project view  = 500ms Staff – launch project editor =  485ms Staff – save project  = 78ms Student – project view  = 3.52s Student lists – retrieve all students for 2011/2  = 1.23s

Any degradation beyond a 20% increase will need to be evaluated by the stakeholders for approval.

SecurityThe current security model must be retained, with the potential addition for "Login as any user" and a Read All account for Application Support.
BackupThe new portal must be backed up and allow for recovery within 3 days given that it is currently a priority 2 system.
PatchingPatching for the database and application will move completely to IS Applications given that the portal will run on IS Applications infrastructure.

 

Project Info

Project
ECA Portal Infrastrucuture
Code
ECA001
Programme
Z. ECA Portal and LMS (ECA) (closed 2012/13)
Project Manager
Craig Middlemass
Project Sponsor
Jared Taylor
Current Stage
Close
Status
Closed
Start Date
20-Oct-2011
Planning Date
n/a
Delivery Date
n/a
Close Date
02-Aug-2013