BiZZdesign Blog

Education and inspiration for business transformation

 
 
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.




Combining ArchiMate® 3.0 with Other Standards – UML / SysML / ERD

posted by Marc Lankhorst & Joost Niehof on Sep 8, 2016

As we stated in the introduction to this blog series, ArchiMate models can usefully be combined with models in other techniques, in order to zoom in on specific aspects of your enterprise. If these models are tied in to an overall enterprise architecture model in ArchiMate, an integrated model of the enterprise can be constructed that relates (sub)models from formerly separate domains in a meaningful way.




Combining ArchiMate® 3.0 with Other Standards – BPMN

posted by Marc Lankhorst & Joost Niehof on Sep 6, 2016

As we explained in the first blog of this series , the ArchiMate language is not intended to replace other standards and modeling approaches. For many domains, there are languages and techniques available that provide more detailed descriptions.




Combining ArchiMate® 3.0 with Other Standards – BMM / BS / BMC

posted by Marc Lankhorst & Joost Niehof on Sep 1, 2016

As we have described in our previous blog , the ArchiMate language is not intended to replace other standards and modeling approaches, but rather to connect them. In this blog, we will focus on relating ArchiMate to several management-oriented techniques: The Business Motivation Model, Balanced Scorecard, and Business Model Canvas.




Combining ArchiMate® 3.0 with Other Standards – Introduction

posted by Marc Lankhorst & Joost Niehof on Aug 30, 2016

The ArchiMate language is not intended to replace other standards and modeling approaches. For many domains, there are languages and techniques available that provide more detailed descriptions. Those languages, such as UML, BPMN and others, have a narrower scope (e.g. UML for specifying software, BPMN for business processes) than ArchiMate, but they lack concepts for relating these to other domains.