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.
BPMN specification defines an Activity as “Work that a company or organization performs using business processes”. But what are the common mistakes and how do you avoid making them?
This article places BPMN and UML alongside each other, with a summary of the commonalities and differences between the two languages.
For two decades, the terms Business Process and Workflow co-exist. However, many professionals still misunderstood the terms and commonly think that a Business Process is just another term for a Workflow. This article will explain the commonalities and differences between both terms and terms related to their management and IT support.
BPMN diagrams are commonly treated as synonyms for process diagrams. This short article will present the last three types of BPMN diagrams (collaboration diagrams, choreography diagrams and conversation diagrams) and the possibilities for their common use.
This series of articles is dedicated to the explanation of common BPMN 2.0 terms, where this article will explain the terms Fork, Join, Branch and Merge as defined in the BPMN 2.0 specification.
The IT4IT vision is a vendor-neutral Reference Architecture for managing the business of IT and underpins the important work done with IT frameworks such as TOGAF® 9, COBIT® and ITIL®.
TOGAF certification has become a de facto baseline for endorsing the skills of an enterprise architect. But how does it really help you?
Graphically, a Flow is represented with an arrow between elements in a Process, Collaboration, or Choreography. BPMN 2.0 defines different kinds of Flows, which are explained in this article.
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.