In the first part of this blog post, we discussed in general how the structure of the ArchiMate modeling language matches the structure of both component and feature teams. In this second part, we want to go a bit deeper into this topic.
In the most recent post in our ongoing series on agile and architecture, I argued why architecture models are valuable for agile organizations. That post concentrated on the ways in which you can use these models to foster business agility at the enterprise level. In this post I want to zoom in a bit and discuss how architecture models and ArchiMate in particular can support agile teams. Read more
Recently, the Banking Industry Architecture Network (BIAN) published version 8.0 of its financial industry reference architecture (https://bian.org/servicelandscape-8-0/). This provides a comprehensive model of the business capabilities, business scenarios, service domains and business objects used in banking and other financial services. Read more
Schaeffler is a globally acting component supplier for the mechanical engineering and automotive industry employing around 89,000 people. Facing the challenges and opportunities of digitization and transition from combustion engines to fuel-cell and electric vehicles, the business processes and underpinning application landscape and technology use are in an ongoing transition; generating a strong need for Enterprise Architecture. In this blog we outline the nature of EA at Schaeffler and tool support by BiZZdesign’s solution, focusing on architecture modeling quality. Read more
In the past, I have written extensively on the combination of enterprise architecture and agile development, most recently about the notion of intentional architecture. It is clear that for any organization or system of some size, a solid architecture practice is needed next to agile ways of working.
BIAN, the Banking Industry Architecture Network, is offering banking industry a Financial Reference model that can be used to help Banking Architects create their organization-specific Banking Architecture, based on standardized building blocks provided by BIAN. This webinar illustrates the practical use of the Financial Reference Model inspired on a real-life case using TOGAF , ArchiMate and a professional EA tool.
By Marc Lankhorst & Patrick Derde
ArchiMate® 3.1 Concepts and Overview
Download our ArchiMate® 3.1 Concepts and Overview poster. This poster shows you the ArchiMate 3 framework with all concepts and their definitions. Print it large and hang it on your wall.
On November 5th, 2019, The Open Group published a new version of the ArchiMate standard: ArchiMate 3.1. ArchiMate is an open and independent modeling language for enterprise architecture. It provides instruments that enable enterprise architects to describe, analyze and visualize the relationships among business domains in an unambiguous way.
This version takes the improvements made in ArchiMate 3.0.1 forward and sees the introduction of a significant number of corrections and clarifications to the standard. The language has also been enlarged thanks to several new additions, e.g. Value Stream, a new Strategy element.
To help you with designing, assessing, and communicating the consequences of decisions and changes within and between business domains and to make sure you use the latest version of the ArchiMate standard correctly, BiZZdesign has created the ArchiMate 3.1 Quick Reference Card, which you can download for free using the button below.
At the Open Group conference in Amsterdam in November 2019, the latest version of the ArchiMate modeling language for enterprise architecture was released. Version 3.1 is an update to the previous major version 3.0 (released in 2016). Despite being ‘just’ a minor version update, it holds a number of useful additions and improvements for EA practitioners.
Our recent blog post on abstraction levels in architecture models resulted in a lively discussion on LinkedIn. As part of that discussion, the notion of layering was questioned, and in particular the layers that are built into the ArchiMate language. In this post I want to clarify the thinking behind the language structure.
One of the biggest challenges in making Enterprise Architecture successful is ensuring proper communication with business stakeholders. Enterprise Architecture is quite often perceived as a discipline of the IT organization (where unfortunately also many EA teams are operating), and the traditional EA diagrams are not always the best visualizations for business stakeholders. To create better alignment with the business organization, it is important to create business-friendly visualizations, both from format and content perspective. This will help in improving the maturity of your EA practice and establish it as an enabler of strategic decision making and continuous change.
Organizations today are faced with an ever-increasing speed of change. To enable faster transformation, they implement agile methods, which impact the whole enterprise. Obviously, change need to be communicated, but one cannot document all the details because otherwise they would be outdated the next week, or perhaps the very next day. Read more
In my previous blog post on using the ArchiMate modeling language together with the Scaled Agile Framework (SAFe), I briefly mentioned the need for modeling the intent of the enterprise. In an agile context, this notion of intent and intentional architecture is quite important. In this blog, I want to explore that further.
How Does Enterprise Studio Support ArchiMate?
Enterprise Studio is the only EA management suite that provides genuinely native ArchiMate support. This means that, by default, our platform is built with an ArchiMate meta-model and the modeling language we use is ArchiMate. The platform enables users to execute a wide range of analyses on top of the dynamic ArchiMate models, as well as identify and visualize insights to support business decision making. Importantly, BiZZdesign plays a leading role in the development of the standard. As such, we concentrate a considerable amount of expertise in house. This helps us offer customers a superior product and exceptional consulting services, e.g. Enterprise Studio is regularly the first product to implement new versions of ArchiMate and be accredited by The Open Group.
ArchiMate provides a powerful language to visually describe the architecture of an enterprise at different layers – from strategy to implementation. Read more
In previous blogs, we have written about the combination of structure and data to create novel insights into your enterprise, and about how this can support creating a Digital Twin of your organization. To reiterate, a digital twin is a digital representation of a real-world entity or system.
Business Architecture with ArchiMate
Business architecture is a growing discipline. The TOGAF® ecosystem has recently seen the addition of Guides on topics such as business capabilities, and the TOGAF Standard Version 9.2 (a standard of The Open Group) has added useful guidance on business architecture. The BIZBOK® (Business Architecture Body of Knowledge) continues to rise in popularity as well. The ArchiMate® modeling language has also improved its support for business architecture.
ArchiMate® 3.0 (a standard of The Open Group), was released in 2016 and comprises a number of concepts that specifically target this domain. With these concepts, ArchiMate models can be used in various analysis and design techniques for business architecture. This offers business architects a solid basis for their efforts and helps them create a line of sight between strategic decision making and the operational enterprise.
In this webinar, Marc Lankhorst, who has led the team that developed the standard, will describe the business-oriented concepts in ArchiMate and provide practical examples of their use for business architecture. The presentation will show the use of ArchiMate in techniques such as stakeholder analysis, strategy mapping, capability-based planning, ecosystem modeling, business outcome journey maps, and more. Marc will also give a sneak peek into the next version of the standard, which aims to offer even more support for business architecture.
All over the world, retailers seem to be having a hard time lately. In the UK, for instance, over the last several years, their woes have become part of the national narrative, alongside the lack of housing, or an underfunded NHS. Whether in the local paper, online or on television, one hears about retailers’ troubles regularly – at times it seems the only thing disappearing faster than retail stores in Britain are the polar ice caps.
Today, organizations need to move at speed and adapt their business to a volatile environment, while at the same time dealing with many inside and outside stakeholders and influences, ranging from customers and partners in the ecosystem to regulators, competitors, and the uncertain effects of politics (viz. Brexit or the US-China trade war). To be an adaptive enterprise, business architecture is an indispensable discipline. Without an architectural approach to your business, you will quickly get mired in the myriad changes and effects, without a clear path forward.
Much of what we do in the world of enterprise architecture and business process management is based on pre-defined analysis and design techniques, like a game that has a well-defined set of rules and operates within a bounded, predictable universe. You know what the aim of the game is (check-mate your opponent, or reduce the cost of your application landscape, for example) and follow the rules to get the optimal outcome.