Aggregated enterprise architecture wisdom
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…
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 …
Technology Implementations: Too Important to Fail Regardless of an enterprise’s size and industry, technology touches every aspect of a business’s operations now more than ever. Successful technology implementations have always been important but in today’s economic landscape, technology implementations NEED to be successful as they can make or break a business. Here are some horrific […]
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 over…
-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 practic…
-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 w…
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 p…
In a previous blog entry we introduced you to use case types and use case presentation methods (textual use cases or use case diagrams). In this entry, we will cover the five most important rules for creating use cases. Rule #1: Follow a straight path to achieve a use case goal A use case should be as concise […]
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,…
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 …
-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 interope…
Analyzing or designing the various features and functions of a software system can be daunting, especially when there are multiple actors and other interfacing systems involved. Thankfully, analysts can turn to use cases to make this process much easier. At the very minimum, an effective use case should: define how stakeholders interact with a system define how a system […]