In my previous blog post (https://bizzdesign.com/blog/a-pattern-for-sizing-archimate-diagrams) I described why it is useful to reduce complexity when creating architecture diagrams. It supports the architect by guiding the creation of diagrams and it supports the reader by not creating overly complex diagrams (too many different types of concepts). Each viewpoint addresses a specific concern, e.g. a capability map to show what the capabilities of a company are. In this blog I will focus on the application layer to provide practical examples using the viewpoint creation pattern described in the previous blog post. The examples are quite generic. They are meant to be used as a starting point for professionals looking to learn more on the subject so they appeal to a large audience.
Kevin Wallis (MOD ISS) & Marc Lankhorst (BiZZdesign)
In the previous instalments in this series, we discussed common drivers for architecture in defence and industry, commonalities between the architecture practice in defence and the civil sector, and why the ArchiMate language was chosen as a recommended standard for expressing architectures in the NATO Architecture Framework v4. In this final instalment, we discuss the work that still needs to be done for using ArchiMate in the context of NAF v4.
Kevin Wallis (MOD ISS) & Marc Lankhorst (BiZZdesign)
In the previous two instalments in this series, on drivers for architecture in defence and industry and on comparing defence architecture practice with the civil sector, we described the common drivers for architecture in defence and industry. We also discussed the commonalities between the architecture practice in defence and civil sectors. We noted that collaboration and interoperability in networks of organizations is an increasingly important driver for architecture, and we highlighted the growing use of commercial “off-the-shelf” products in both defence and civil organizations. Where architecture practice is concerned, we also explained how processes are largely similar (as captured, for example, by TOGAF’s Architecture Development Method), that architecture artefacts play an increasingly important role in public procurement and other arenas, and that both worlds are increasingly using reference models to capture commonalities and share knowledge.
Previously, I have blogged about stakeholder management and showed you some useful techniques to support this important part of enterprise architecture. In this blog post, I want to address different ways to share architecture information with different types of stakeholders involved in changing your enterprise.
Artificial Intelligence (AI) seems to be a buzzword lately, promising techniques and tools that could influence our lives, our work and the way we do business. For many designers and enterprise architects, the question becomes: What would be the role of designers on all levels (strategic, EA, BPM, data, technical) in incorporating AI in a company? There are even ethical questions that may arise when instituting AI in a company, which you must take into account before making the change.
In my recent blog series, I highlighted the importance of communication for strategic transformations. This affects several functions and various roles in your organization by asking different questions, such as:
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 standards. In this series, I 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.
In the previous installment of this architecture models 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.
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. Read more
Adaptive Enterprise – We are currently living in an interesting time. The digitization of all business capabilities has reached a new level and has had a huge impact on virtually every industry. Business models are being redefined and new companies have emerged to become global players. Today, companies must be more agile than ever before and the speed of change will only continue to increase.
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.
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.
In today’s turbulent business environment, organizations need to be excellent at designing and implementing change. The ‘Digital Enterprise’ requires continuous innovation, which means that organizations are in a constant state of flux. At the same time, they need to stay in control. They have to deal with regulatory pressure, financial constraints, and the risk of disturbing their going concern while implementing major change.
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.
Information Mapping – 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.
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.
Dependency Analysis – In my previous blog post, I outlined the value of using analysis techniques to get more business value out of your models. I described one of the most common analysis techniques, impact analysis, and showed how color views and heat maps can be used to depict, for example, the use of applications to support capabilities.
In recent years, we see the audience and attention for business architecture steadily increase. A business architecture provides a business-oriented abstraction of the enterprise in its ecosystem, which helps the organization in decision-making and direction-setting. This maturation of the business architecture discipline makes the role of model-based support for design, analysis and decision-making also increasingly important. In this series of posts we will introduce you to useful techniques for business architecture modeling and how they are supported by BiZZdesign Enterprise Studio. Read more
Strategists, architects, process experts, software developers, data managers and other professionals involved in changing the enterprise often put substantial effort in creating all kinds of useful models of their designs. In many cases, such business models, enterprise architecture models, business process models, software models, data models and more are only used to specify some design, i.e., to describe what should be built. But there is much more value to be had from these models, by using powerful analysis techniques to create new insights. Read more