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

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…

New staff for the EA team

I'm delighted to welcome Jason Murphy, who joins us as our CRM Architect, and Wilbert Kraan, our new Data Architect.  Both Jason and Wilbert have worked as consultants for several years and bring new skills and considerable experience to IS.  They both know more than I do about their respective fields, which is how I like to hire people.

So the Enterprise Architecture practice now comprises the three of us, instead of me working on my won, which means we have more capacty to guide the University's IT architecture.  We can offer a greater range of skills and can bring a wider range of experience to bear.  I'm really excited about the opportunities this presents.

As his job title implies, Jason will focus on contact relationship management, working to build a user community and to create a strategy for managing and improving the University's relationships with prospective students, research partners, community organisations, and other parties - to give them all a better …