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.
In my recent blog post on stakeholder communication, I described various basic forms of communication about architecture, with diagrams, tables, heatmaps and the like. What I did not touch upon in that post is how you can enrich your architecture (and other) models with additional data and display the results in various dashboards. That is the topic of this post.
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.
-Fabian Aulkemeier & Marc Lankhorst
In our previous blog post, we outlined why Enterprise Architecture and Agile/DevOps are key in becoming an adaptive enterprise. We also described several use cases where EA can strengthen Agile and DevOps practices. Now, we want to focus on the ways in which you can connect these in practice, using architecture models and appropriate tool support.
-Nick Reed and Bart Molenkamp
In today’s business landscape, effective transformation is critical for enterprises to stay competitive. By definition, transformation happens over time.
Enterprises (or some subsection thereof) have a current state which needs to change for the better. That change – however small or large – results in a different future state. With the widespread adoption of Agile working practices and DevOps-based continuous delivery, these changes can be very small and very frequent.
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.
NATO Architecture Framework & ArchiMate
-Marc Lankhorst (BiZZdesign) & Kevin Wallis (MOD ISS)
In the first instalment of this series, we compared drivers for enterprise architecture in defence and industry and found that there is are increasing commonalities: a growing focus on interoperability and collaboration in complex ecosystems. a blend of the physical and IT worlds, and the preference for “off-the-shelf” products over custom development. These commonalities also lead to increased usage of the same methods and standards for enterprise architecture. In this instalment, we’ll compare the architecture practices of defence and civil sectors.
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.
Humans have evolved to make fast decisions. For example, when a stranger approaches you, you know almost instantaneously if they represent a threat, if they are angry, friendly or happy. The cognitive processing involved is mind-boggling if we actually stopped to think about it (which we don’t).
We subconsciously process a myriad of information, such as the person’s stance and their facial expression, and make a decision in a split second about whether this stranger represents a threat or opportunity. Or, in the language of evolution, we decide “Which one of us is lunch?” and “What am I going to do about it?”
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:
Everyone remotely involved with enterprise architecture and similar disciplines knows the importance of knowing your stakeholders. Stakeholder management is a key technique in EA and many methods, including TOGAF, stress its importance. But there is more to management than keeping individual stakeholders happy. In this blog post, I want to introduce three techniques that not only help you ensure stakeholder satisfaction, but also make good use of stakeholders and their influence in achieving business goals.
Supporting Large Architectures as a Team
Large architectures of big organizations can become quite large and complicated, posing a challenge for the architects developing and maintaining them. In previous discussions, we have addressed a number of techniques for organizing and controlling such large models to keep things manageable. In this installment, we look at the processes and practices you can use to optimize the collaboration between the people working on these architectures.
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 have written about the use of a modeling language and the practical usage of the TOGAF Enterprise Continuum to classify architectural descriptions along different levels of abstraction. In this blog, I’m going to demonstrate how the content of these descriptions can be visualized with a standard notation. While TOGAF 9.1 provides the standard architecture development method (ADM), ArchiMate is the worldwide standard to model and visualize the content of enterprise architectures. Both are a public standard of The Open Group.
6 Ways to Organize Your Architecture Models (Part 1)
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.