Skip to main content

Reboot: three years on

I've decided to revive this blog, after a three-year hiatus, to post news and thoughts about my current role as Head of Development Services, in the IS Applications Division, at the University of Edinburgh.  My aim is to give some visibility to what goes on "behind the scenes" (or should that be "behind the screens"?) and to reveal the sort of issues that face IT in a Russell Group university.

My current job is quite different from my previous role at the National e-Science Centre, which was the topic of the previous incarnation of this blog.  Some issues, such as virtualisation and cloud, are common to all IT jobs these days, but the emphasis of my current job is on support and administration systems rather than research.  One important difference is that I must stress that all the posts here will not represent the official position of the University of Edinburgh in any way.

To start off, let me point you at an interesting comparison of the "student experience" at three European universities.  This posting doesn't mention IT at all - which is a little humbling.  On the other hand, perhaps this is how it should be.  People come to university to learn, not to use the IT.  People tend to notice IT most when something goes wrong, so no news can be good news.   Thanks for Guillermo Rein for noting this via LinkedIn.
http://nickybartlett.blogspot.com/2012/01/per-usual-i-must-give-recap-of-my.html .

Comments

Popular posts from this blog

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

Why the UCISA Capability Model is useful

What do Universities do?

This may seem a strange question to ask and the answer may seem obvious.  Universities educate students and undertake research.  And perhaps they work with industrial partners and create spin-off companies of their worn.  And they may work with local communities, and affiliation bodies for certain degress, and they definitely report on their activities to government bodies such as HEFCE.  They provide student services and support.  The longeryou think about it, the more things you can think of that a University does.

In business, the things that an organisation does are called "capabilities", which is a slightly strange term.  I think it is linked to the HR idea of a combination of the CAPacity and ABILITY to do a task.  Whatever the name, it is a useful concept.  A capability is more basic than a process: a University may change the way it educates students but as long as it remains a University it will educate them one way or another.

A capability …

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.


This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…