Aggregated enterprise architecture wisdom
The Archimate notation aims to be the standard to be used by everyone in enterprise-architecture and related fields. But what exactly is its anatomy – its underlying structure? And if it’s aimed at enterprise-architecture, what is it about that structure that makes it seem only to support IT-architecture, and in such an awkwardly IT-centric way?
(Apologies, folks, […]
The previous post, ‘From business model to enterprise-architecture‘, turned out to be another of my monster essays. Sorry…
The detail’s there if you need it, but if you just want to do the translation from Business Model Canvas to Archimate, without worrying too much about the ‘Why’ behind it, here’s the short version.
Step 1: […]
Archimate aims to be the standard notation for enterprise-architectures. But has it become too IT-centric to be usable for that purpose? And is there any way we can get it to break out of the IT-centric box?
These questions came up for me whilst exploring the architectural processes we could use in expanding a business-model developed […]
Yes, the Business actor concept in Archimate do make sense in conjunction with the organization unit concept in Togaf. At least the Archimate concept covers the Togaf concept good enough to make it usable. The match is to be found in how Archimate uses “departments” and “business units” as examples. Archimate TOGAF Business actor Organization […]
Entitled “Just enough EA”, a set of case studies has been published by the Joint Information Systems Committee (JISC), made up of senior managers, academics and technology experts working in UK further and higher education. Continue reading →
Not having a concept for “Location” that stands on its own when creating these EA models will almost certainly create opportunity for misunderstanding. A “usable” Location in any blueprint must always be an instance of the pure logical Location Concept. An instance of a Location as used in an Enterprise context generally carry attributes of […]
The question about “the remaining role of UML now that ArchiMate has arrived” generated an interesting discussion on ArchiMate LinkedIn group. Adrian Champbell‘s first comment was: Archimate was deliberately designed to be mappable to BPMN and UML, but not to replace them. Not parallel universes but complementary ones. Archimate is for modelling at an Enterprise […]
If you follow my blog you will see that I am very hopeful of the future of ArchiMate. There is a great deal of potential here. I wrote a post entitled ArchiMate – The Emerging Architecture Modeling Standard that provides…
I was recently asked about the adoption trend of ArchiMate. I see demand for ArchiMate support slowly increasing in the UK, but it is nowhere near the tipping point that it has already reached in the Benelux area, especially in the Netherlands of course, where a requirement for enterprise architects to have Archimate experience is […]
I have recently finished reading the book ‘Lost on Translation’ by Nigel Green and Carl Bate and found it a very useful and insightful. I recommend it for the shelf of any Enterprise Architect. See http://www.lithandbook.com/ The book describes the VPEC-T ‘thinking framework’ and a focus on understanding the Values, Policies, Events, Content and Trust perspectives […]
Influence without authority—but with real responsibility in modern enterprise architecture
Comprehensive, practical handbook for enterprise architects, leaders, and students