Skip to main content

EDUCAUSE - Anticipating the future

Several EDUCAUSE sessions tried to guess how changing trends in both society and in IT will affect the future of Higher Education.  One such was the second keynote session, which combined two presentations and a discussion on the theme of how the worlds of academia and work combine for students.  The point was made that only a third of post-secondary education takes place in universities (in the USA), with the other two-thirds happening in the corporate world.  On a more prosaic note, it was also noted that many students have to work just to support themselves during their degree, which can constrain when they are able to engage with their courses.  Both speakers suggested that a more flexible model of education may be needed, sometimes (often?) in collaboration with corporations.

I wonder what my academic friends would say to this notion.  Many of them are strongly opposed to the idea that university education should primarily about preparing people for the world of work.

Other "big picture" sessions looked at the impact of MOOCs.  I caught the one about Stanford's Coursera, which is the company that the University of Edinburgh is working with. (Edinburgh has a long-standing relationship with Stanford).  I was interested to see not just the impact on the wider world but also the effect within Stanford, encouraging more interest in methods for online pedagogy and assessment.  There was also an addendum by the CIO of another university, presenting the impact from the IS side.

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…