Skip to main content

Episode IV: A New Hope


Since the beginning of this academic year, I have taken on the full-time role to establish an Enterprise Architecture capability at the University.   For the past few months, I have been working out roles and relationships, principles and processes.  I have given presentations to several groups, first within IS and now moving beyond.  I have recruited an experience contractor to help the University along this new path.  And as the new calendar year begins, we are in the position to start producing results that people can see.

A key part of this role is communication – explaining what EA is about, listening to people’s concerns, sharing knowledge of resources new and old, discussing what needs to be done, and disseminating decisions.   I am reviving this blog as one strand of this communication.  Over the years, I have been a pretty poor blogger.  I haven’t always had things to say, and sometimes I have lacked the time to write them.  With the importance of communication in this new role, I hope to do better.

There are other channels besides this blog.  I am arranging regular meetings with other sections of IS, with the colleges, and with other support units.  There will be an Architecture Repository with links to resources – including high-level documents such as principles and architecture overviews, as well as more technical artefacts such as data models, interface descriptions, technology life-cycles, and procurement standards.  And I welcome any questions from anyone who wishes to know more or to raise a concern.

Architecture is a subject dear to my heart.  During my time as Head of Development Services I did try to introduce some architecture ideas and practices, which is very difficult to achieve with basically no funding. My new role, to which I am seconded for the current academic year, gives me the opportunity to put proper foundations in place.

Comments

Post a Comment

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 .
Post a Comment
Read more

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-de...
2 comments
Read more

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...
1 comment
Read more