Skip to main content

Initial reflections on OGF20 / EGEE User Forum

So that was OGF20 and the 2nd EGEE User Forum. I was so busy there that I didn't have time or energy to blog. So much happened in such a short time that I'd have been hard put to keep up.

This turned out to be the best-attended GGF/OGF meeting ever, narrowly beating GGF5 (which was held in Edinburgh in 2002). We had over 900 people attend during the course of the week and a significant number stayed for all or most of the week. I haven't had feedback from all the sessions but I believe the workshops were well attended and I know the Grids Mean Business and the EGEE-specific sessions went very well.

A notable aspect of the week was the good interaction between the different communities. In particular, the colocation of the OGF and EGEE events has helped to show both sides where standards can apply or are needed. The commercial delegates helped to guide the requirements for standardisation work as well as sharing information on best practice. The exhibition space had a particularly good showing of EC-funded R&D projects as well as the EGEE demos, which certainly gave me a better picture of what these projects aim to achieve, in addition to stands from industry sponsors and UK e-Science.

Tony Hey and Peter Coveney gave stimulating keynote speeches, each worthy of its own blog entry. Mark Linesch, Ian Bird and Mario Campolargo gave overviews of OGF, EGEE and of the latest round of EU funding opportunities. Many other presentations raised interesting ideas and experiences. I was (of course) particularly pleased with the Grids Mean Business sessions, which were well attended and full of interested presentations, even though I say so myself. Gillian Law has written reports of these sessions which you can find on the Grid Computing Now! web site.

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…