Both languages can quite easily be used in combination. To this end, BPMN has a more fine-grained set of elements, with various types of events, tasks, and gateways. BPMN supports detailed sub-process and task modelling down to the level of executable specifications, but lacks the broader enterprise context, for example, to model the application services that support a process or the goals and requirements it has to fulfil. ArchiMate is typically used for high-level processes and their relations to the enterprise context, but it is not intended for detailed workflow modeling. The main standard for modelling business processes is the Business Process Model and Notation (BPMN). We finish this blog by demonstrating how Enterprise Studio supports this. In these tables, the more abstract, high-level concepts are presented on the left and the more concrete, detailed concepts are in the right-hand column. The following table provides an approximate mapping between ArchiMate concepts and BPMN. In this blog we focus on ArchiMate 3.0 and BPMN. In the previous blog we showed the relation between ArchiMate 3.0 and Business Motivation Model, Balanced Scorecard and Business Model Canvas. The uniqueness of ArchiMate does not lie in the individual concepts, rather the opposite: many concepts in the language are designed to have a direct correspondence with similar concepts in other techniques, so that you can easily use it in combination and zoom in on details of parts of the enterprise in these other techniques. For many domains, there are languages and techniques available that provide more detailed descriptions. Combining ArchiMate 3.0 with other standards BPMNĪs we explained in the first blog of this series, the ArchiMate language is not intended to replace other standards and modeling approaches.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |