Skip to main content

EA Community of Practice

Today, I attended a meeting of the UCISA EA Community of Practice, at Manchester Metropolitan University (MMU).  The focus of today's meeting was on data architecture, and I contributed with a talk about our data warehouse plans at the University of Edinburgh.

The first presentation of the day was from the University of Birmingham, who are using data architecture techniques to support the upgrade of their Finance and HR systems to a new ERP system.  This was a good example of the benefits that enterprise architecture can contribute to service transformation projects.

Next was a talk about the HEDIIP Data Capability Toolkit for the HE sector.  This sets out the case  that we can make data a tangible asset, capable of adding value to our universities.  The programme is effectively taking an EA approach, mapping the as-is state and defining the target to attain, all mapped to a data strategy.  From the talk, it sounds like the toolkit has some elements which will be very helpful and I will take a look to see which ones I can use in my own work.

My talk seemed to go well and I got some useful feedback from the questions.  That is one of the benefits of giving a presentation to a group that includes several experienced architects; it's a cheap way of getting consultancy!

The final presentation of the day was from the team at the host University (MMU), who are preparing to replace the interfaces from their student record system.  They are planning to use Azure API Management to present all their APIs, which looks to be a useful system (if your data is on Azure, that is).  It provides a browsable catalogue for users, a request process that lets owners approve or deny requests, and management information about which systems are using which APIs.  It basically fulfills all the functions of a traditional Enterprise Service Bus.

UCISA, for those readers who don't know, is the organisation for supporting & representing University & College IT departments.  The EA Community of Practice, as the name suggests, is formed of enterprise architects (and data architects, business analysts, solution architects) from approximately 80 universities.  In addition to the data architecture sessions, we spent some time reflecting on how to better support each other and build our community.  Several ideas surfaced and I hope to see them taken forward.  One idea was for local meetups and I'd be open to organising some meetups in Scotland.

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…