Skip to main content

Drupal for the Enterprise

For the past few months we have been investigating whether Drupal might be a suitable CMS for our university's web presence.  Several people in the university already use Drupal for smaller sites and we use it ourselves in that way.  It is popular and highly flexible.  It has been used for a number of highly visible sites around the world and so would likely handle the number of page hits that our central web site receives.

The big question for us was whether the large number of modules that are available for Drupal could be managed in a consistent way across our large, devolved, institution.  The university has over 500 people who can edit some part or other of our central web site and we need mechanisms for managing this access.  We want to be able to share information between different parts of this distributed information architecture, a requirement that is very different from running a more centralised operation. 

Meanwhile, Drupal modules are written and maintained by a large, devolved, open-source development community.  This can make the system very flexible and responsive but can also lead to inconsistencies between modules.  Security fixes can sometimes be bundled in with upgrades to functionality, which can make maintenance more complicated than a system provided be a central vendor.  We needed to understand how to engage with the Drupal community and how to manage an installation to provide the rock-solid service the university's users require.

We do use other open source software, such as Apache and Linux, for some of our core systems.  Those are rather different in character to Drupal - from our point of view, they could as well be a commercial product.  We download them, install them and patch them; we don't modify them or configure them from a range of different options.  Drupal will be a different experience.  The nearest we have come to this so far is probably the Moodle virtual learning environment.

I'd pleased to say that our investigation was successful.  The project team wrote a detailed report which was presented to the governance group, who gave their blessing to this initiative.  We are now progressing to the next stage, drawing up a detailed business case and implementation plan.


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…

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…

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…