Skip to main content

VLEs and other student systems

This time of year is always busy for Development Services.  By the end of July, we have to install any new systems needed for the start of the new semester in September.  This gives us a month of "normal running" which we can use to fix any unexpected problems, before the students start using the systems in earnest.  Our aim is to give the students the best service possible - ideally they should barely even notice all the IT that is making their life easier.

Each year brings its own particular focus for us.  Two years ago, the emphasis was on student administration systems, adding extra functionality alongside the new student record system.  Last year, we were busy integrating IT following the merger of the University and the Edinburgh College of Art.  This year, the focus is on the systems that students actually use directly.

Chief among these is the upgrade of the main Virtual Learning Environment.  We have run WebCT for several years.  Now we are replacing WebCT with Learn, the latest system from Blackboard (who acquired WebCT back in 2006).  This should give a welcome refresh to the experience of using the VLE and we are getting positive vibes back from many of the academic staff who have started to use it.  Distance Learning courses have the option of using our new Moodle VLE as well.

The university is also launching a major revamp of its student support.  We are currently developing some basic IT support for the first year of this new system.  Next year, we will work on a major project to significantly enhance the technical underpinnings of this new initiative.

The university portal, MyEd, is also being upgraded.  Like the VLE, the version we are currently running is a little long in the tooth and the new version should be a significant improvement.  Later in the year will we replace the student e-mail and e-diary system with Microsoft's Office 365, which will also give students the ability to use web versions of Word, Excel and Powerpoint, with storage space for their documents.

More is in the pipeline for next year.  The next phase of the Shared Academic Timetabling project will give each student their own personal timetable, direct to their e-diary.  This may sound straightforward; the hard part is actually setting up the timetabling system itself.

All these new tools should give a much better service to students.  Hopefully, after the initial period of getting used to the new systems, they will be able to ignore the IT and just use it to help their studies.


Popular posts from this blog

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:

I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…

2016 has been a good year

So much has happened over the last year with our Enterprise Architecture practice that it's hard to write a succinct summary.  For my day-to-day experience as enterprise architect, the biggest change is that I now have a team to work with.  This time last year, I was in the middle of a 12-month secondment to create the EA practice, working mainly on my own.  Now my post has been made permanent and I have recruited two members of staff to help meet the University's architectural needs.

I have spent a lot of the year meeting people, listening to their concerns and explaining how architecture can help them.  This communication remains vital, the absolute core of what we do and we will continue to meet people in this way.  We also talk to people in other Universities in order to learn from what they are doing and to share our own experience back.  A highlight in this regard was my trip to the USA last January.

Our biggest deliverable for the past year was the design of the data wa…