Combine ArchiMate & TOGAF Standards to Support Digital Change

posted by Bernd Ihnen on Apr 13, 2018

In the first blog of this series, I explained how important it is to raise your digital change capability to become an adaptive enterprise. I also highlighted the role of effective communication, as well as approaches to categorize and visualize enterprise architecture descriptions based on the TOGAF and ArchiMate standardsIn this series, also included guidance on which approach to select for modeling Architecture and Solution Building Blocks (both are types of logical or physical components)To round out this series, I will end by discussing the connection to Deployed Solutions. 




Using ArchiMate to Visualize the TOGAF Enterprise Continuum

posted by Bernd Ihnen on Mar 30, 2018

Previously, I have written about the use of a modeling language and the practical usage of the TOGAF Enterprise Continuum to classify architectural descriptions along different levels of abstraction. In this blog, I’m going to demonstrate how the content of these descriptions can be visualized with a standard notation. While TOGAF 9.1 provides the standard architecture development method (ADM), ArchiMate is the worldwide standard to model and visualize the content of enterprise architectures. Both are a public standard of The Open Group.




Why Business Outcome Journey Maps are a useful technique for business architects

posted by Marc Lankhorst on Dec 5, 2017

Business Outcome Journey Maps are a new technique that help you focus on the key aspects of value creation in your enterprise. Here we show you what they are, why they are useful and how they are supported in BiZZdesign Enterprise Studio.




Why adding a value stream element to ArchiMate® is key?

posted by Adina Aldea, Henk Jonkers & Marc Lankhorst on Oct 25, 2017

In recent years, the concept of ‘value stream’ has become increasingly popular. It is a useful element in the toolbox of business architects, and is advocated in, for example, the Open Group Guide to Value Streams and the BIZBOK® from the Business Architecture Guild®. Though ArchiMate® has had a value mapping element since its inception, until now it does not have a value stream element. In this blog we propose to add a value stream element to ArchiMate in a way that supports approaches such as those described in the Value Stream Guide and the BIZBOK, is coherent with the language structure, and minimizes the impact on the rest of the language.




ArchiMate relationships point in the same direction as the enterprise

posted by Marc Lankhorst on Jan 24, 2017

When I give a presentation to a technical audience showing any kind of picture with an arrow in it (not necessarily an ArchiMate diagram), more often than not, someone will raise their hand and ask: “What does that arrow mean?” When I answer, they will follow up with “Shouldn’t it be the other way round?”




In case you missed it: Combining ArchiMate® 3.0 with Other Standards & Techniques – Summary

posted by Marc Lankhorst on Nov 3, 2016

Since the release of ArchiMate 3.0 last June, my colleagues and I have written a series of blog posts about combining ArchiMate with other standards, methods and modeling techniques. This post summarizes what we have shown you.




Using ArchiMate® in an Agile Context

posted by Marc Lankhorst on Oct 11, 2016

In the past, my colleagues and I have written several blogs on the combination of enterprise architecture and agile ways of working (e.g. Enterprise Architecture and Agile Development: Opposites Attract?, Enterprise Architecture and Innovation: A cultural change, Escaping the Jaws of the Project Monster). In this blog, I want to focus in more detail on the use of the ArchiMate language in the context of agile methods, in particular the Scaled Agile Framework (SAFe).




ArchiMate® 3.0 and Service Blueprints

posted by Marc Lankhorst & Adina Aldea on Sep 27, 2016

A useful technique for service design and innovation is the Service Blueprint. It is related to customer journey maps (see our previous blog) in its emphasis of customer touchpoints, but focuses more on the realization of services by underlying activities and less on the quality of the customer’s experience.




ArchiMate® 3.0 and Value Mapping

posted by Marc Lankhorst & Adina Aldea on Sep 22, 2016

In several previous blogs, we have outlined how you can use ArchiMate 3 in the context of business architecture and strategy development, such as Capability-Based Planning, and combining it with the Business Motivation Model, the Business Model Canvas and the Balanced Scorecard. In this blog, we continue with the series, looking at how you can describe value chains, value streams, and value networks.




ArchiMate® 3.0 and Customer Journey Maps

posted by Marc Lankhorst & Adina Aldea on Sep 19, 2016

A Customer Journey Map is a useful way to graphically represent the customer experience of an organization. It focuses on the touchpoints that characterize the customers’ interaction with the services of the organization and helps you to optimize this experience.