Skip to main content

EA at the University of Lincoln

Last week, Allister Homes from the University of Lincoln gave a presentation to the UCISA EA group about how Lincoln have set up their Enterprise Architecture practice and where they are now in using Enterprise Architecture. The presentation is online and you can see it here:

Enterprise Architecture at Lincoln

Do take a look. 

I found Allister's talk both interesting and reassuring.  Lincoln's EA practice is 12-18 months older than ours, and as a result it is a bit more embedded into university culture and processes than us, as one might expect. But we're on a similar path and not too far behind.  EA seems to be delivering good results at Lincoln, which bodes well for us.

Both practices are based in our IT departments and are reaching out to the business areas.  We are working with similar principles (because we both used the same set of TOGAF principles as our starting point).  Lincoln have an established design authority which reviews all projects; we have put in place processes that do the same and are planning to create a formal design authority.  Lincoln have a set of architecture requirements that all procurements and developments must adhere to; we have a similar set of standard procurement questions, which we are about to review and formalise further.

Allister has made good use of the BizzDesign modelling tool.  We are just in the process of finalising our choice of modelling tool.  We're a bit behind in developing EA models but people are seeing the benefits of those we have produced.  Getting the tool and repository in place will accelerate us down this part of the EA path.

The occasional meetings and presentations run by the UCISA EA community are a really useful way of sharing experience and information among UK universities.  I recommend joining the mailing list if you are at all interested.

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…