Skip to main content

Web 2.0, e-Science and Innovation

Last week the e-Science Institute organised a "think tank" to review the state of e-Science and suggest opportunities for research. A major emphasis of the debate was the recent trend to use Web 2.0 tools to support scientists. Dave de Roure gave several examples he saw at recent conferences, including wikis and blogs such as Open Wetware and Useful Chemistry, as well as various data mashups. Tony Hey gave a public lecture on e-Science and Digital Scholarship which presented a similar story, including the use of utility computing (which now seems to be called cloud computing - you've got to love the constantly changing buzzwords in IT). Among the discussions, people mentioned the combination of Web 2.0 tools with semantic web technology, and the combination of structured queries and semi-structured information as in DBpedia.

This growth of e-Science 2.0 (to coin a buzzword of my own) has mainly seems to have occurred largely in the life sciences, perhaps because they're not centrally organised like the physicists and astronomers. Perhaps they also have more smaller-sclae experiments. One interesting point is that the adoption of these tools has been driven by the scientists making use of commonly-available tools. It isn't the result of existing "road maps" for e-science. It's another case of innovation occurring at the boundaries between communities; where ideas meet and produce new ideas. Sometimes this sort of innovation can be planned (or at least encouraged); sometimes it happens anyway.

This suggests to me that whenever an organisation runs a roadmapping exercise, it pays to include people with a broad mix of backgrounds and some wild ideas. Many of the ideas produced won't germinate, but some of them may grow into something useful.

Comments

Popular posts from this blog

Webinar: Powering your business with Cloud Computing

On October 14th, I will be hosting a Grid Computing Now! web seminar on the topic of Cloud Computing. We have lined up two very interesting speakers who are using Cloud now to make businesses work. Ross Cooney had a good technological solution to sell but couldn't make it economic until Cloud Computing allowed him to pay for his computation only when he needed it. He will discuss the instant benefits and long term impact of cloud computing to the development, competitiveness and scalability of your application. Alan Williamson created the BlueDragon Java CFML runtime engine that powers MySpace.com. He advises several businesses and will give an overview of the different types of services available and how to avoid being locked-in to a single supplier. You can register for this event here .

Business Model Canvas

A Business Model Canvas is a tool for mapping the core functions and capabilities of an organisation.  Compared to the Core Diagrams that I described in an earlier post , the business model canvas attempts to present more aspects of the business, starting with the value proposition – a statement of what the organisation offers to its users (in the business world, to its customers).  It shows the activities and resources, as Core Diagrams do, but also shows user relationships & channels, and also benefits and costs.  I’m not aware of any universities that have used this tool but you can find examples from elsewhere on the web. We are considering business model canvases as a tool for mapping the strategic capabilities of units at the University of Edinburgh.  Phil Taylor, our EA contractor, sketched an outline of what a business model canvas might begin to look like for HR: This is only intended to be suggestive: the real canvas would need to result from in-depth discussions abo

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 iterat