Skip to main content

Interlude: New opportunities for user interfaces

In my previous entry, I promised some thoughts on presentations at OGF20. Since then you will have seen nothing from me. This is not because I lost interest; unfortunately I've been in hospital and then recuperating. Now I'm well again, back to work and the proud owner of a heart pacemaker. I still plan to blog some thoughts arising from OGF20, but for this entry I will deal with a different topic.

I've just read and been inspired by Chris Mairs' 2006 Turing Lecture on Inclusion and Exclusion in the Digital World. Chris takes what could be a dull (albeit important) topic and makes it very interesting by showing the big picture. He's talking about accessbility, which previously I tended to associate with detailed guidelines about which colours to use on web pages and how to tag HTML images with meaningful "Alt" tags. I did consider it important - I'm now old enough to hate small fonts - but I didn't find it inspiring.

Chris's lecture looks both at technologies that help to overcome disabilities (including pacemakers!) and at technologies that are hard to use for disabled people. He gives mobile phones as an example of the latter, as their use of soft keys means that they were practically unusable by blind people - of which Chris is one. He notes that this is not just a matter of a particular technology but has major social implications, as people now tend to use mobiles to navigate their social lives. Similar concerns apply to the World Wide Web.

Now, however, Chris sees many opportunities for improved interfaces - to benefit all sorts of users, disabled people included. To continue with the example of mobile phones, these are now powerful computers with many input and output devices (including microphones, speakers, displays, cameras, GPS, ...). Just as important as the hardware is the software environment: most phones are now extensible platforms with development kits available. This allows third parties to develop specialist interfaces. The next step is to send the data in multiple forms, so that different interfaces can process it differently. For example, a phone choice menu might be sent both in sound ("Press 1 for new sales, press 2 for...") and in XML (" 1: New sales ... ").

What I found inspiring was Chris's optimism and sense of opportunities. The use of open platforms and cool technology could benefit lots of us in many different ways. I recommend the article. Unfortunately you may have to pay to read it - it's online at http://comjnl.oxfordjournals.org/cgi/content/abstract/50/3/274.

Comments

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…

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…