Skip to main content

Artistic and computational thinking

On the rare occasions when we computer folk get to collaborate with artists, I'm always fascinated by the different ways we approach design.  I first noticed this back when I was working for the National e-Science Centre and an art project used our video conferencing system for a live performance project.   During the performance the video system started to glitch.  Instead of stopping and fixing the problem, the musicians and dancers started to incorporate the glitch into the work.  That was neat.

More recently, some of my colleagues have worked with artists on a couple of web applications.  These collaborations have exposed wide differences in the ways people think.  For one project, we did our usual approach of producing wire-frame outlines of the user interface, with the aim of letting sample users step through a draft design.  To our surprise, the users couldn't handle this sort of abstraction.   They needed to see a completed graphic design - to see the full picture in the literal sense.

In another case, our collaborators did the drawing for us.  They expressed their requirements as pictures of what the screens should look like.  And they looked good.  Then we asked about the paths users should take through the system and what the objectives of the system should be.  Then they are we talked past each other - it proved very difficult to understand each other.  We think in terms of processes and outcomes.  They seem to think in terms of pictures.   We each have something to contribute - a good graphic designer can transform the user experience of a system, as can a good information architect - but sometimes we seem to need a translator to help us communicate!


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…