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. 




6 Ways to Organize Your Architecture Models (Part 2)

posted by Marc Lankhorst on Apr 4, 2018

In the previous installment of this architecture organization series, I wrote about organizing your model repository according to business, information and technology domains. I also explained the need to create separate current- and future-state models, and the separation between and model content and views. In this part of the series, I have a few more things to add on the topic of naming and modeling conventions, as well as advice on how to set up governance and quality assurance structure around your models. 




6 Ways to Organize Your Architecture Models (Part 1)

posted by Marc Lankhorst on Mar 22, 2018

If you have some experience in modeling real-life, full-size architectures for large-scale organizations – preferably in the ArchiMate language, of course – you have likely come across the challenge of organizing your models in logical and manageable ways. In this two-part series, we’re going to share our top 6 ways to organize your architecture models. These six methods should help you keep your models neat and tidy while also supporting better outcomes for your strategic initiatives.




Using the TOGAF Enterprise Continuum to Classify Architectures Descriptions

posted by Bernd Ihnen on Mar 7, 2018

Previously, I wrote about  the need to digitize change capabilities and how enterprise architecture can support and provide value to your organization. I also discussed how to categorize architecture descriptions along different levels of abstraction. But there is one dimension I didn’t dive into: How generic or specific is the architecture description compared to your organization?  

Over the past decade, reference architectures have been developed and many have been published. They are a very useful start describing an enterprise, and the architectures are more or less specific to our enterprise. I don't want to lose myself in academic discussions about what should be classified as what, so I will focus on the big points of the idea behind.




7 Key Strategy Views in Enterprise Studio (part 2)

posted by Marc Lankhorst on Feb 15, 2018

In my previous blog post, I described how Enterprise Studio supports the Business Model Canvas, Ecosystem maps, Balanced Scorecards including SWOT, PESTEL and Five Forces analysis, and heatmaps to highlight salient information for your organization. Now, I want to focus on more advanced views and analyses that help you evaluate the viability of your strategy and business models and then take steps towards their implementation.




7 Key Strategy Views in Enterprise Studio (part 1)

posted by Marc Lankhorst on Feb 8, 2018

A survey conducted by The Open Group in cooperation with BiZZdesign and other partners found that the largest difficulty in strategy process (for over half of the 500+ respondents) is bridging the gap between strategy development and implementation.




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.




The Business Architect’s Toolbox: Information Mapping

posted by Marc Lankhorst & Tim Vehof on Aug 22, 2017

Business Blueprints are an essential instrument in every business architect’s toolbox. The Guide to the Business Architecture Body of Knowledge (BIZBOK Guide®) defines four core business architecture domains: Value Streams, Capabilities, Organization and Information.




The Business Architect’s Toolbox: Organization Mapping

posted by Marc Lankhorst & Tim Vehof on Aug 10, 2017

As discussed in the introduction of this blog series, the maturation of the business architecture discipline makes the role of model-based support for design, analysis and decision-making increasingly important. Therefore, we introduced you to several useful techniques for business architecture modeling and how they are supported by BiZZdesign Enterprise Studio. In this blog, we will discuss an approach to modeling a blueprint of one of the core domains of business architecture: Organization Mapping.