Skip to main content

Meeting: Science & Engineering Computing Professionals

Last week I gave a short presentation about my EA work to the Computing Professionals Advisory Group in the College of Science and Engineering (CSE).  Each academic school in the college has one representative in the group, so these meetings are a good way to find out what is happening across the college.  Representatives from IS attend in order to share our news and to hear what issues are being raised in the schools.

My contribution on this occasion was to give a brief overview of the plans and intent for the EA practice.  I chose to show some example artefacts from our work and from elsewhere, and to highlight some of the existing catalogues that we could incorporate into the planned architecture repository.  I added an appendix to the slides listing our draft EA Principles, for comment, but I did not talk through those in the meeting.

The CSE computing professionals are very keen to have access to download and update data on central systems.  They queried my applications architecture diagram, which shows arrows leading from central systems to the portal, apps and school systems but not the other way around.  The diagram reflects the work we are doing at the moment to build lightweight APIs, which are mainly conceived as supplying data from central systems and less concerned at present with updating them in response.  It was a good point to raise.

I agree that we should provide the capability for local systems to update central systems.  This would help keep centrally held data up to date and would allow the applications in the presentation layer to give a joined-up view of relevant data.  The draft EA Principles do support this, in tension with the corresponding principles that business processes should be standardised and that central systems should be used wherever local needs do not require extra support.

However, the implementation of this idea goes well beyond the technological questions of designing appropriate APIs and authorisation systems.  It runs into the problem I blogged about last week: you can only create reusable business components when your organisation has reached an appropriate level of agreed understanding.  Business processes need to be designed from the ground up to be fully online – the current buzzword for this is “digital first”.

The technology underlying these processes also needs a certain level of maturity, and several of the HE-specific software systems supplied by vendors are built on rather old technology.  So while I support the idea of two-way APIs, we need to recognise that we have limited capability in this regard and that other areas of work may need to take precedence.  As the HBR analysis noted, we have to develop our capability one phase at a time.

This is one of many talks and presentations that I am giving to different groups in the University.  I spoke to the equivalent group in the College of Humanities and Social Sciences in December (before I rebooted this blog) and I will attend the meeting of the corresponding group in the remaining college, Medicine and Veterinary Medicine, at the end of the month.  I intend to post short notes about these and other meetings here on this blog.


Popular posts from this blog

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 …

"No more us & them"

WonkHE recently posted an interesting opinion piece with the title Academics and Administrators: No more ‘us and them’. In that post, Paul Greatrix rebutted criticisms of professional services (administrative) staff in Universites from some academics. To illustrate his point, he quoted recent articles in which administrators were portrayed as a useless overhead on the key tasks at hand (teaching and research).

This flows both ways, as Greatrix himself points out. As Enterprise Architect, I work with Professional Services colleagues and I have heard some of them express opinions that clearly fail to understand the nature of academic work. Academics cannot be treated as if they were factory workers, churning out lectures on a treadmill.

I think these comments reveal a fundamental clash of ideas about how a University should work. Some people who come into management positions for other sectors tend to frame the University as a business, with students and research funders as customers t…

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…