Read this BPMN blog to better understand the roles of the 'Functional' and 'Process' approaches in business process modelling are.
Having a good metamodel is essential to every enterprise architect. We discuss how a good metamodel can help understand structure, document component relationships and much more.
Business Layer Behavior Concepts: Based on service orientation, a crucial design decision for the behavioral part of the ArchiMate metamodel is the distinction between “external” and “internal” behavior of an organization.
Before the BPMN 2.0 specification, there never was any confusion between tasks and events, in this article, we will discuss differences between message events and the send and receive tasks.
No, it’s not a typo. “Pre-requirements” or “prequirements” is a quirky way of expressing that a lot goes on before requirements are formalised enough...
If you’re a regular LinkedIn user you’ve probably noticed there have been quite a few changes this year; following Microsoft’s acquisition of the company for $26.2 million in 2016. There’s more to the makeover than just a cleaner look – there have been some changes in functionality too. So is it still the best sales weapon out there?
This article places BPMN and UML alongside each other, with a summary of the commonalities and differences between the two languages.
BPMN Process diagrams are most common, and are depicted as a graph of flow elements – Activities, Events, Gateways, and Sequence Flows that define finite execution semantics.
Although very similar to the UML 2.0 component, the ArchiMate component concept strictly models the structural aspect of an application: its behavior is modeled by an explicit relationship to the behavioral concepts.
There are some things in TOGAF that confuse practitioners over and over. The difference between scope and partition is one of those confusions that comes up as a regular question. In this blog we explain the key differences, and explain why TOGAF can be confusing.