Skip to main content

Learning Archimate

I've started to evaluate the potential of using the Archimate modelling language for our architecture practice.  As architecture is primarily about communicating ideas, I didn't want to just start using this in my team and leaving everyone else mystified by the strange diagrams we started to produce.  Also, I wanted to judge how best to use the language.  So we arranged training for people from different teams and with different roles, partly to share the knowledge and partly to evaluate which aspects of the language (if any) would suit each teams.

Image result for archimate bolton
Archimate can represent many aspects of a system, starting with the motivations, drivers and stakeholders; moving to map business services and processes; then the applications that provide those services, and finally the infrastructure on which they run. You rarely display all aspects at once; instead there are a host of views that present particular aspects of the system.  The diagram above is taken from a JISC workshop in 2012 and is a motivation view which shows how drivers, goals and principles influence the design of a business process for open days.

Because the language can tell stories that cross all these boudaries, Archimate diagrams may impact may people, including project managers, business analysts, developers, support staff, sysadmins, service owners, and in theory business owners (although in practice I'd expect to use Powerpoint for most business partners).  So for our training session, we brought together one person from each of these roles.  Some could immediately see how the language might be useful to their work.  Others, at the more technical layer, were less convinced, but at least they will be able to understand the diagrams that other people produce and to explain them to others in their team.

Archimate is widely used in the EA world and supported by most major EA tools.  (Architects reading this will probably know more about it than me). We will start by using Archi, the open source tool, to gain experience before choosing a potentially expensive commercial offering.  I plan to start by recasting some of the diagrams we have drawn for ongoing projects, comparing the results in Archimate with the originals, and then looking to see how we can take advantage of the new models to describe more aspects of those systems.  This may take a while; I'll post an update here when I have something to report.

Comments

Popular posts from this blog

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…

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 about th…