An Institutionally Secure Integrated Data Environment (INSIDE) By University of St Andrews & University of Durham Original Aims –the development of a sustainable model of both Universities information flows and processes based on analyses and formal modelling –the generation of user-centric portals for staff based on their institutional roles and responsibilities –the piloting of value-added services based on the analyses of existing processes –cross institutional comparisons leading to generic models

(Moderately) Revised Aim Revised Statement of Aim –introduce advanced MLE functionality while respecting the devolved and distributed management structure of academic institutions Objectives –value-added services –user-centric portals –high-level reference model –abstraction and articulation of generic features across Institutions Methodology –model, analyse, improve –introduce change by deploying value-added services as high profile pilots –derive genericity through comparative studies

Progress to Date Value-added services: –module comparison generator: checks local records against those held by Student Records and generates reports on differences –staff-operated portal for module enrolment: allows staff to enrol students at School level for any module – this is essential for School purposes of allocating tutorial groups, lab slots and similar –student portal for module enrolment: the student is authenticated by ITS user id and password. A page displays part of their record, and also questions and information specific to the module such as tutorial and lab times. This effectively lets the student enrol from any browser. Inter-institutional work-in-progress on generic features –rationalisation of vocabulary within and between institutions –XML-based representation of the student record –record of processes and tools used for modelling –security culture investigation

Success and Problems Successes: –elimination of several paper trails –card-based authentication of students enrolling for modules at the School-level –automatically checking for module pre-requisites –allowing students access to their own record via the web, with the opportunity to submit corrections –electronic reconciliation of module lists maintained by Student Records and the School –elimination of redundant data maintenance and duplicate data entry Problems : sustainability/accuracy of reference model

Findings & Recommendations What works –targeting problem areas, modeling and then piloting improvements –UML can be used successfully –involve all stakeholders What doesnt –the big picture changes faster than it can be captured in a model maintained by one group (INSIDE) Essentials for change –having the right mix of roles, expertise and authority on the project management group –building trust between key players –lead by doing - people pay attention to managed learning software that works!