Aggregated enterprise architecture wisdom
Enterprise Architecture (EA) is a discipline that creates value for organizations by answering the question “how should we organize ourselves?”The art of modeling plays an important role in this discipline, both to get insight in the current …
The Open Group released ArchiMate 2.0, the latest version of the organization’s open and independent modeling language for enterprise architecture. The updated version is now aligned with TOGAF, enabling enterprise architects using the language to improve the way key business…
By Andrew Josey, The Open Group, Henry Franken, BiZZdesign ArchiMate® 2.0, an Open Group Standard, is an upwards-compatible evolution from ArchiMate 1.0 adding new features, as well as addressing usage feedback and comments raised. ArchiMate 2.0 stand…
In two previous postings we have discussed the necessity of separating the what of architecture from the how (see here) and concluded that it is both useful and important to distinguish between a logical, ideal-world architecture description for a so…
In a previous post we discussed two levels of architecture description within ArchiMate: the service level describes the what and the underlying components and processes describe the how. The motivation for making this distinction was also discussed:…
We at Corso are seeing many EA practitioners gravitating to the ArchiMate framework as the tool for delivering Enterprise Architecture. Why is this? Unlike many frameworks to date that do not specify how model views are represented, ArchiMate provides a clear notation and language for the communication of EA. The ArchiMate framework is currently at version […]
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 […]