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…
Category: ArchiMate
Every article that has to do with ArchiMate
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…
On the Use of Colours in ArchiMate
The official ArchiMate 1.0 spec is colourless. The original ArchiMate project of Telin (Telematica Instituut) used colours, though they were never a part of the spec, they were a more something of a custom. Two different schemes using the original…
Modelling IT in Your Organization, a Broader Perspective
As Enterprise Architects, we model the use of IT in an organization and ArchiMate is a decent language for that. ArchiMate, with its business layer, application layer and technical layer helps us to model the different aspects of that use.…
Read More Modelling IT in Your Organization, a Broader Perspective
