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

2016 has been a good year

So much has happened over the last year with our Enterprise Architecture practice that it's hard to write a succinct summary.  For my day-to-day experience as enterprise architect, the biggest change is that I now have a team to work with.  This time last year, I was in the middle of a 12-month secondment to create the EA practice, working mainly on my own.  Now my post has been made permanent and I have recruited two members of staff to help meet the University's architectural needs.

I have spent a lot of the year meeting people, listening to their concerns and explaining how architecture can help them.  This communication remains vital, the absolute core of what we do and we will continue to meet people in this way.  We also talk to people in other Universities in order to learn from what they are doing and to share our own experience back.  A highlight in this regard was my trip to the USA last January.

Our biggest deliverable for the past year was the design of the data wa…

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…

New staff for the EA team

I'm delighted to welcome Jason Murphy, who joins us as our CRM Architect, and Wilbert Kraan, our new Data Architect.  Both Jason and Wilbert have worked as consultants for several years and bring new skills and considerable experience to IS.  They both know more than I do about their respective fields, which is how I like to hire people.

So the Enterprise Architecture practice now comprises the three of us, instead of me working on my won, which means we have more capacty to guide the University's IT architecture.  We can offer a greater range of skills and can bring a wider range of experience to bear.  I'm really excited about the opportunities this presents.

As his job title implies, Jason will focus on contact relationship management, working to build a user community and to create a strategy for managing and improving the University's relationships with prospective students, research partners, community organisations, and other parties - to give them all a better …