Dec 012014
 1st December 2014  Posted by at 2:38 pm No Responses »

We’re pleased to announce the release of Archi 3.1. This is a maintenance release that fixes a number of bugs and introduces some small, new features. The focus of Archi 3.1 has been to improve the user interface response time when using large models, and to implement stronger integrity checking when loading and saving models to disk.

Archi 3.1 is available at the Download page.

We’ve also created a new Plug-ins Page where we will be able to offer additional functionality to Archi. The first plug-in available is an implementation of The Open Group’s ArchiMate Model Exchange File Format (Phase 1). This plug-in will be updated as the implementation progresses.

Sep 292014
 29th September 2014  Posted by at 2:34 pm No Responses »

Archi 3 is here! It seems to have taken a long time to arrive but we’re pleased to be able to release it in time for the Autumn. We’ve worked hard to bring you a new version that is built on the latest version of the Eclipse platform. This ensures that Archi will continue to work on the latest versions of Windows, Mac OS X, and most Linux distributions.

New features include support for a new look and feel, import and export to CSV, an improved Magic Connector, find/replace, export image to PDF and many other features and fixes.

I’d like to thank all our users for their support and encouragement these last few months, and to Jean-Baptiste Sarrodie for his incredible support, encouragement, evangelism, contributions and vision. I’d also like to say a big thank-you to those people who have kindly donated by Paypal. These donations have kept the wolf from the door and encouraged me to continue developing new features.

Aug 182014
 18th August 2014  Posted by at 2:31 pm No Responses »

We’re pleased to announce our new Archi User Forums. The Google Groups that we had been using before were proving difficult to use and to navigate. We hope that the new forums offer a better experience in sharing your discussions related to Archi and ArchiMate.

The new forums will allow you to upload screenshots, share models, and open polls. We invite you to register as a member!

Jul 302014
 30th July 2014  Posted by at 1:38 pm 2 Responses »

The Open Group recently published an interesting case study on their blog, ArchiMate, An Open Group Standard: Public Research Centre Henri Tudor and Centre Hospitalier de Luxembourg. In 2012, the Centre Hospitalier de Luxembourg allowed the Public Research Centre Henri Tudor to experiment with an access rights management system modeled using ArchiMate. According to the article, the Public Research Centre needed to find an architecture modelling language that met their stringent requirements for this project. After evaluating some modelling languages, they chose ArchiMate to help them visualize the relationships among the hospital’s employees. The Case Study is interesting in itself, but what struck a very loud and resonant chord with me was the following statement:

…the Public Research Centre also chose ArchiMate because it is an open and vendor-neutral modelling tool. As a publicly funded institution, it was important that the Public Research Centre avoided using vendor-specific tools that would lock them in to a potentially costly cycle of constant version upgrades.
“What was very interesting [about ArchiMate] was that it was an open and independent solution. This is very important for us. As a public company, it’s preferable not to use private solutions. This was something very important,” said Feltus.

In referring to “vendor-specific tools” versus “an open and independent solution” it is not clear whether Christophe Feltus is referring to ArchiMate the language itself as a “tool”, or whether he is referring to an open source ArchiMate software tool, perhaps Archi. My inclination is to infer the latter, particularly as he refers to “a potentially costly cycle of constant version upgrades” and also because some of the diagrams in this document look suspiciously like they were created using Archi:


However, the important thing here is that this is yet another example of public organisations and government bodies choosing to use open source software and open data formats to ensure open data interoperability and to avoid costly vendor lock-in.

Last year, the City of Munich rejected Microsoft’s Office and Windows software in favour of open source alternatives. Munich says the move to open source has saved it more than €10m. And very recently, the UK Government chose the Open Document Format, the OpenOffice-derived file format, as the best solution for all government documents. The Minister for the Cabinet Office, Francis Maude, said:

I want to see a greater range of software used, so people have access to the information they need and can get their work done without having to buy a particular proprietary brand.

And the same thing is now happening in Enterprise Architecture with the Open Group’s ArchiMate language and the open source ArchiMate modelling tool, Archi. Archi is used not just by individuals, it is used as a core tool by many large organisations – banks, telecoms companies, insurance companies, you name it. I was recently asked, “Which companies use Archi?” I replied that it would be better to ask “Which companies *don’t* use Archi?”. Archi is, to the chagrin of some EA tools vendors, annoyingly ubiquitous.

Having had several years experience working in the domain of open interoperability standards in the UK and in Higher Education, I welcome this move to open standards and open software. This brings me to the main point of this blog post…

For some time, The Open Group has been engaged in a project to design and implement an open and vendor-neutral interoperability file format for the exchange of ArchiMate data. I have been involved in this initiative since it began, and it pleases me greatly to see that good progress is being made.

This is important for organisations who are currently engaged in Enterprise Architecture and who use the ArchiMate language. Organisations will not have to concern themselves with the headache of migrating sensitive data to another free, or less expensive, tooling solution. Organisations can be assured that their data can be safely imported and interoperate with a variety of software solutions. As the Public Research Centre in the Open Group’s case study found, there are viable open alternatives to expensive and non-cross platform software. OSS Watch, the UK-based independent advisory service maintains a comparison matrix of open source options for education. But this list is not limited to the UK, or to education. Here is an example.

The take-home from this blog post is this – if you want to future-proof your processes and your data then ensure that your organisation uses open data together with open source solutions such as Archi.

Jul 252014
 25th July 2014  Posted by at 8:42 am 4 Responses »

If you know ArchiMate, there’s a good chance that you know Gerben Wierda‘s post series “What is wrong with this picture?”. This blog post is both a tribute to his work and an attempt to explain the importance of why you should be aware of the difference between core relations and derived ones.

In his book Mastering ArchiMate, Gerben presents several beginner’s pitfalls and especially the (bad) use of derived relations. I can only recommend that you follow his advice, and I will explain why, but let’s start at the beginning…

Core vs derived relations

When reading the ArchiMate Specification you might notice that the relationship tables contain a lot more relationships than those described in the metamodel pictures (such as this one for the business layer). The latter are the “core” relationships. In a detailed ArchiMate model, you could just use only these ones. But in real life, you will certainly have to create some high level views hiding some elements and using derived relationships.

In general, ArchiMate tools implement all of the possible relationships based on the tables in the Appendix of the specification, but don’t tell you which kind of relation you are creating, core or derived, and this may lead to problems.

Infrastructure Service used by Data Object

Today I was working on a model for a new project. For this, I used our standard pattern for a database:


This pattern basically shows a shared server which hosts several databases. In order to be able to move one database from this shared server to another one in the future without having to reconfigure applications using it, each database is accessed though a dedicated DNS alias pointing to the real server name (for those who know Oracle, we assume the service name and the port will not change).

Following our pattern, I then added some additional elements from the application layer, notably a Data Object realized by an Artifact. As I am testing the Archi 3 Early Access Preview, I played with the new Magic Connector functionality and found the following possible relationship – Infrastructure Service used by Data Object…


Wait a minute! What does “Infrastructure Service used by Data Object” actually mean? In natural language it seems to be OK because, after all, my database is managed/presented through the “DB1 (Infrastructure Service)” and therefore relies on it, so I could use it. But let’s examine this situation more closely first.

The first question to ask is whether it is a core or derived relation. That’s the easy part, the Application-Infrastructure Alignment Metamodel clearly shows that it’s not (only Realization from Artifact to Data Object is permitted). So it turns that it must be a derived relation, and we need to find it.

In order to understand what this Used By relation means, let’s start at the endpoint – the Data Object. Only a few core relationships are defined – Realization from Artifact, and Access from both Application Function and Service. A Used By relationship can only be derived from relationships having a strength at least equal to Used by, so this excludes the Access relationship.

After some time checking the Infrastructure Layer Metamodel, I ended up with the following (derived relation in blue):


“DB1” used by “Shared DB server”? Not what I intended to show, and clearly false in my case (there’s nothing on my database server that make use of the DB service).


All this came about because I used a helpful and nice feature in Archi – the Magic Connector. This can really help you a lot and shows you all allowed relationships between concepts, but it doesn’t tell you which relationships make more sense in a given context. As it is, I know ArchiMate well enough to ask such questions, but what if I were new to ArchiMate? I would have kept the Used By relationship and never have understand its real meaning, a common beginner’s pitfall.

So what can we do? As an Architect, I can make sure that I really understand what I’m doing by learning (and Gerben’s book is perfect for that). As an Archi contributor, I can suggest to enhance the Magic Connector to show me whether it is proposing a derived relation or a core one. We could also envisage that Archi could warn me when I manually create relations or reveal their nature (as with the “Show Structural Chains” option). Adding such a feature would really help a lot of Architects master ArchiMate.

Just for fun, re-examine some of your models and take 5 minutes to see how many derived relations you use, and then check their exact meaning. Do you find some strange things?

Jul 212014
 21st July 2014  Posted by at 2:33 pm 1 Response »

I think most people in the world of Enterprise Architecture, and especially ArchiMate, are aware of Archi as an approachable and ubiquitous tool that not only provides an easy entrance into ArchiMate modelling, but also has just enough functionality to keep you happy in your modelling requirements. Many individuals and organisations start with Archi, intending to move onto a more expensive solution but stay. Perhaps for these users the price point is right, or perhaps Archi provides just enough functionality?

What we are hearing from our many thousands of users is that whilst they love the elegance and simplicity of Archi they would love to have model repository support, more advanced reporting, and more flexibility in the presentation of the ArchiMate diagrams.

We agree. And we intend to bring you these features.

Let’s consider Archi’s existing feature set as a starting point. Archi is relatively young, and therefore the feature set will grow and improve. Over the last year we have already introduced some exciting new features that have vastly improved Archi. Late last year we brought you the option of setting colour schemes so that you could use Archi right alongside Gerben Wierda’s fantastic ArchiMate learning resource, Mastering ArchiMate. In January, we released version 2.6 with some great improvements to the diagrams, including better line and fill colour options, and better connections. In March we kept up the pace and brought you version 2.7 with greatly improved support for exporting diagrams as images, as well as SVG format, a popular request from many of our users.

And don’t forget we brought you our great new website, redesigned in a modern, clean style. We’re still working on improvements to the site and are now setting up a framework to support featured blog posts and articles.

So where now?

Since my last blog post we have not stopped. As you might have seen, we’ve now made the necessary changes to allow Archi to be built on the next generation of the underlying framework – Eclipse 4. We are working on Archi 3.0. Being built on Eclipse 4 guarantees Archi’s future within a sustainable framework. Archi 3.0 will bring the option of pluggable look and feel application themes, export and import of model data in CSV format, bi-directional support for Archi’s famous Magic Connector, Find and Replace, and many more improvements. We think it’s going to be a fantastic release.

And the incredible thing is that we’ve delivered all of these exciting features and improvements to you over the last few years for free!

We’re big fans of open source and free tools, but we can only do so much for free. In order to sustain the development of Archi and other projects we need investment in resources, particularly financial resources.

Consider an organisation’s return on investment by using Archi. I invite each company, each training organisation, each consultant that has used Archi over some time to calculate the financial savings they have made by using Archi instead of a paid-for tool. Collectively, this amounts to huge savings. Clearly, this is a good thing. But, like the goose that laid the golden eggs, we need to keep Archi alive to keep the good thing going. And this requires the co-operation of all stakeholders who have a vested interest in the future of Archi – companies, organisations, architects, consultants, trainers, and of course the developer of Archi itself. We now need to pull together to move forward.

So, we are now exploring potential business models that can support and guarantee Archi’s continuing success and its future. At this stage, there are some potential options on the horizon.

More than just tooling, our users also need support and training in the use of TOGAF, ArchiMate, EA Modelling, and of course, Archi itself. Whilst we ourselves do not currently have the resources to deliver training and consultancy, we can recommend and work with potential partners to provide you the full package for your modelling and EA needs.

“Archi” the software is still growing, it is still relatively young. And “Archi” the brand is equally as strong, with a great reputation. Archi has been a disruptive and refreshing force in the EA world, with some of our users hailing it as a “game changer”. In the last 3 or 4 years we have shown what is possible by taking a light, agile, and intelligent approach to software development and delivery. Imagine what the next 3 or 4 years could bring with investment and collaboration with like-minded partners. As Steve Jobs once said, we are thinking about where the puck is going to be, not where it has been. Currently Archi is a cross-platform desktop solution used by many thousands of architects. The scale of its global reach and impact has been phenomenal. We want to bring you tools that go beyond the desktop, providing you the means to work with your models and data in the cloud, and on your mobile devices. Archi on the desktop is just the beginning.

So, what can you do to help? If you’re happy using Archi today for free, that’s fine. Keep on modelling and enjoy Archi! We love happy users. If you think you’ve benefited from Archi either personally or in the workplace, why not make a small donation? This would be a great help towards running costs. If you are a company that uses Archi for your EA modelling, or if you are a TOGAF/ArchiMate training organisation that uses Archi for your training, you might consider investing in the tool that brings value to your organisation.

We think we can build on Archi’s great reputation to bring you better and inexpensive tools, complementary services, and advice and guidance to make your organisation more profitable and help you achieve your goals. With your help we can make it happen.

Mar 182014
 18th March 2014  Posted by at 2:27 pm No Responses »

We’re happy to let you know that today we’ve released Archi 2.7.1 which fixes a UTF-8 encoding issue when exporting diagrams to SVG.

Mar 112014
 11th March 2014  Posted by at 2:23 pm No Responses »

Spring is in the air. As we approach the Spring Equinox we often feel the need for some spring cleaning, or Khooneh Takouni. And so we’ve been “shaking the house” by revisiting some of the features of Archi that need improving and also validating the existing codebase with a full suite of unit tests. This latest release of Archi includes the ability to export your ArchiMate diagrams in SVG format. In order to do this we’ve thrown out the old 16×16 raster-based icons for each ArchiMate figure and replaced them with vector-based equivalents. This also means that you can zoom right in on your diagrams in Archi without compromising the image quality. As a bonus, you can now export your ArchiMate diagrams at a greater scale factor in PNG, BMP and JPG formats.

  Out with the old…

…and in with the new

We think that this new feature, together with the other improvements we’ve made, makes this a very solid release.

SVG export, plus many other new features, is available in Archi 2.7.

Feb 242014
 24th February 2014  Posted by at 2:20 pm No Responses »

I’m happy to announce that we can now accept donations by PayPal. Archi is free and used by hundreds of architects throughout the world. Some training organisations are already making a good return on Archi by using it in their training programmes. In order for Archi to continue I obviously need to cover running costs and, if you’ve read my recent blog post, you’ll know that this will become a concern this year. There are some great developments in store for Archi, potentially including model repository support, and I’m sure that together we can continue to turn Archi into the world’s greatest ArchiMate modelling tool.

Please show your kindness and appreciation of Archi by donating a small amount.