Skip to main content

AHM 2008

I was pleased by our workshop on research opportunities this week. Our speakers met several people who were interested in their work and might contribute to taking it further. It's hard to measure the outcomes of these events, because the collaborations that we are aiming to catalyse may take months to firm up and then may take much longer to produce actual results, but the first impressions are positive.

Some of the networking happened outside the workshop itself, of course. That is the advantage of face-to-face meetings; sometimes all you need is to bring the right people together for the first few minutes. Also, you can follow serendipitous links, such as when a colleague pointed me at the workshop on declarative data centres that Microsoft Research Cambridge and HP Labs organised earlier this year. I think the UK is building a critical mass in data centre management and I hope this can be encouraged to the point where it becomes a viable industry.

Beyond our workshop, there was plenty of interest in the wider AHM conference. I chaired one "regular" session in which most of the papers were about the use of social networking tools and similar systems for supporting science teams and similar projects. There is a lot of potential here and several people are taking advantage of it.

One limitation of this year's event was simply the large number of parallel sessions, which meant that individual sessions were quite small and that you couldn't follow even half of what was going on. But I think this was offset by he bringing together of several different communities, which should bear fruit in later years.


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…