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.
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). Read more
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.
In this blog post, we discuss the value of an integrated approach to managing risk, compliance and security in the enterprise, using enterprise architecture as a backbone.
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. Read more
On June 14, The Open Group launched the new version of the ArchiMate modeling language for enterprise architecture at the Enterprise Architecture Conference 2016 in London. This is a new step in the development of a standard that started in Netherlands, but in the meantime has received broad international acceptance.
In theory, an ArchiMate® model can be created using just pen and pen, or a whiteboard and markers. There are also software platforms that provide an ArchiMate modeling environment, which come with many automated capabilities and analysis functions.
However in this post, we will focus on an important element in maturing into an advanced, mission critical modeling capability: the model repository.
Changing regulations, business strategies and compliancy standards require new business policies to be developed constantly. Consequently, new decisions will be made which need to be managed properly. However managing these new decisions is (of course) not without challenge. The field of decision management has steadily become more popular – first focusing on it being a better way to manage business rules, but lately shifting its focus to predictive analytics.
Be honest, do you consider yourself a great decision maker? I believe, with a few exceptions, that many people are not able to make optimal decisions. Why you might ask? Well, the answer is quite simple: people don’t have the time to collect and analyze all the available data and information from information systems in your organization, suppliers, customers and other external sources.
During Business Process Management trainings, people often ask me about the best modeling technique: How to model a process model? Where do I begin? Top-down or bottom-up process? Questions that many of you have asked yourselves when beginning to design a process model. In this blog I would like to take you along with me to the world of top-down or bottom-up modeling. Let me start by clarifying some frequently used terms. Then, I will share several personal experiences and my preferred method of working.
The Open Group Architecture Framework (TOGAF) is the most popular framework for developing an enterprise architecture (EA). It is an open standard and may be used freely by any organization wishing to develop an enterprise architecture for use within that organization. BiZZdesign believes in an EA approach that is based on open standards and frameworks. We combine and pre-package frameworks and standards like TOGAF and ArchiMate as an accelerated approach to jump-start customers’ EA programs. In this blog we will explain how we use TOGAF as framework, apply it in practice, with the goal of doing business-outcome-driven EA.
Over the past years many organizations have been working with an Agile method for software development, providing the design team and development team with a particularly important role. Within several projects in which I was involved I had the chance to experience this from up close. In this blog I would like to share five top tips to help a design team efficiently and effectively perform within an Agile environment. Read more
Until quite recently, IT security was exclusively the domain of security specialists. However, in the last couple of years, organizations have started to realize that IT-related risks cannot be seen in isolation, and should be considered as an integral part of Enterprise Risk and Security Management (ERSM). ERSM includes methods and techniques used by organizations to manage all types of risks related to the achievements of their objectives.
In my previous blog post on Enterprise Architecture at BiZZdesign in 2014, I described how the true value of architecture lies in its relationship with other disciplines within the enterprise.
In my previous blog posts, I discussed the way I see strategy work and the types of models that can be used, and how the business model canvas should be the focal point for architecture work. In this blog post, I will show that enterprise architecture is the tool to go from strategy and business model to execution.
The Decision Model (TDM) is a rapidly growing framework for modeling and executing the business logic behind business decisions. When I first read the book “The Decision Model – A Business Logic Framework Linking Business and Technology” by Larry Goldberg and Barbara von Halle, I was impressed with how TDM models the business logic behind operational business decisions. Read more
The Decision Model (TDM) is a new and rapidly growing methodology and framework for modeling the business logic (business rules) behind business decisions, using a powerful graphical notation, that is easy for both business and IT to understand and implement.