A while back I wrote the first post in this blog. It was about handling the secondary and tertiary architectures in your organization. Stuff like the application owner and the process owner and IT support etc. There, examples were given…
Category: ArchiMate
Every article that has to do with ArchiMate
Modeling Risks (and Security and more)
Now that ArchiMate 2.0 has been published it's time to deliver on a promise I made a while back. I have been pretty silent on this blog. I have lots of material but I have been working on an iBook…
Application Deployment Patterns
ArchiMate covers the standard three layers of enterprise architecture: business (products, business processes, business functions, business objects, roles, actors, etc.), application (application components, application functions, application services, data objects, etc.) and infrastructure (devices, nodes, networks, infrastructure services, artifacts), the infrastructure…
Modeling Web Browser Use
In a previous post, I wrote about modeling spreadsheets. In it, I described two methods of modeling these. I settled on modeling the Excel application not as an Application Component, but as an Infrastructure Service. That post laid the ground…
ArchiMate `Problem Areas’: Business Role
I like ArchiMate, but, being an Enterprise Architect (and thus rather pigheaded), I have my criticisms. In this post, I’ll be discussing what I would call a ‘Problem Area’ of ArchiMate: Business Role. Note: the content of this post has…
Modeling GOFBF
In a previous post, I discussed the structural/behavioural divide in ArchiMate and how it differs from GOFBF (Good Old-Fashioned Business Function, the one where structure encapsulates behaviour). In this (short) post, I’ll show a way to model this in ArchiMate.…
Business Process versus Business Function
A rather tricky part of ArchiMate is the difference between Business Process and Business Function. Both stand for behaviour at the Business Level. Both generally encapsulate in the end the same activities. Choosing between a Business Function and a Business…
On ArchiMate’s divide between behaviour and structure
Archimate is divided into structure and behaviour. Active structure objects (like Business Roles and Application Components) perform behaviour (like Business Processes/Functions and Application Functions) and these behaviours act on passive structure (like Business Objects and Data Objects. This division is…
Read More On ArchiMate’s divide between behaviour and structure
Modeling Spreadsheet Use
There sits your user, happily typing away in his spreadsheet. A rather large spreadsheet it is, full of complicated macros and code. Our user is a spreadsheet wizard, using a plugin from a remote data service and a lot of…
ArchiMate is not a language
ArchiMate has been labeled an `architecture language'. It certainly has aspects of a language. The combination of actors, behaviours and acted-upon objects resembles subject-verb-object of a normal language. And that is intentional: the designers of the language had this in…
R&A IT Strategy & Architecture 