Blog Posts: Enterprise Architecture Software
Enterprise Architecture Software
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 […]
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 […]
Enterprise architecture is often perceived as an abstract, conceptual, and somewhat esoteric discipline practiced by ‘high priests’ who provide guidance with their lofty ‘architecture principles.’ It’s true that architects are often concerned with overarching, cross-cutting concerns that are not always visible to the people ‘in the trenches,’ but this view of enterprise architecture is misguided […]
-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 […]
-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 […]
Marc Lankhorst, Fabian Aulkemeier Enterprise architecture, agile software development, and DevOps are sometimes seen as being at odds. We think they can fruitfully collaborate and interface, but how do you do that? How can you align the concepts and processes from these worlds and bridge the cultural gap?