Skip to main content

Views from the schools

This week I had several meetings with computing and e-Learning staff from the academic schools.  I find these meetings really useful to learn what matters to people who are using (or in some cases not using) IS systems in conjunction with their own applications. 

First up was the Technical Peer Group for the university web site.  Here I gave a short summary of our preliminary investigation of whetheer Drupal would be a suitable CMS for the university's central web presence.  I'll write more about that another time.   We also had a presentation about how the university is adapting to the new law on cookies and privacy.  The meeting finished with a short discussion about getting central university data in order to create staff profile pages on school web sites.  We have yet to provide a supported API for this, so some enterprising school staff have found their own way to access the data they need.  This illustrates why a centrally supported interface is a food idea - it would mean a single, guaranteed way of accessing data, rather then multiple ad-hoc approaches that might break if IS change the central system.

Then I had two requirements gathering workshops for the Data Hub project that I blogged about recently.  Several useful strands of discussion suggested ideas to explore in more detail.  Several people were keen to access information about enrolment on tutorial groups, which is something we are just beginning to investigate.  In addition to the technical discussions, I also got some good recommendations of other people who I should talk to, including some of the academic staff who are making good use of e-learning technologies.

Finally I attended a meeting of the Computing Professionals Advisory Group in the College of Science and Engineering, as the IS Applications rep. I gave them an update on various projects and they asked a number of questions.  We were interested in each other's work with Drupal.  They are looking at the possibility of a college shared Drupal service and are wrestling with several of the same issues that we encountered with our preliminary investigations.  I'll be joining their mailing list on the topic, which should be a good opportunity for us to share ideas and experiences.


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 brief summary of our major initiatives

I notice that in 2016 I wrote 34 posts on this blog.  This is only my fifth post in 2017 and we're already three-quarters of the way through the year.  Either I've suddenly got lazier, or else I've had less time to spend writing here.  As I'm not inclined to think of myself as especially lazy, I'm plumping for the latter explanation.

There really is a lot going on.  The University has several major initiatives under way, many of which need input from the Enterprise Architecture section.

The Service Excellence programme is overhauling (the buzzword is "transforming") our administrative processes for HR, Finance, and Student Administration.  Linked to this is a programme to procure an integrated ERP system to replace the adminstrative IT systems. 

Enabling Digital Transformation is a programme to put the middleware and architecture in place so that we can make our processes "digital first".  We're implementing an API framework, a notification…