Converting DEMO PSI Transaction Pattern into BPMN: A Complete Method

Mráz, Ondřej; Náplava, Pavel; Pergl, Robert; Skotnica, Marek

doi:10.1007/978-3-319-57955-9_7

Cited by 12 publications

(7 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Problem: Although BPMN is a well-adopted modelling standard applied by industry to model business processes, additional guidance is required to create consistent and executable BPMN models [24]. Mraz et al [25] and Rodrigues [15] have already developed some principles and practices for transforming OCD constructs (based on DEMOSL 3.0) and the underlying transaction patterns for transaction kinds into BPMN models. Others [19] already demonstrated the possibility of using a tool to transform some DEMOSL 3.7 concepts to BPMN 2.0 concepts, but a sub-set of invalid transformations are generated when using the tool, since the transformation specifications were based on a set of incomplete transformation scenarios.…”

Section: Methodsmentioning

confidence: 99%

Identifying Scenarios to Guide Transformations from DEMO to BPMN

Vries

Bork

2021

Advances in Enterprise Engineering XIV

View full text Add to dashboard Cite

The heterogeneity in enterprise design stakeholders and models generally demands for consistent and efficient transformations of enterprise design knowledge between different conceptual modelling languages. A systematic process and precise model transformation specifications are a prerequisite for realizing such transformations. The Design and Engineering Methodology for Organizations (DEMO) approach represents the organization design of an enterprise in four linguistically based, semantically sound aspect models. The Business Process Model and Notation (BPMN) on the other hand enables more flexibility in creating models and benefits from wide adoption in industry, the execution of processes e.g., by simulations, and the availability of proper tooling. A transformation of DEMO models into BPMN models is thus desirable to avail of both, the semantic sound foundation of DEMO and the wide adoption and execution possibilities of BPMN. Previous research already developed some principles and practices for transforming DEMO models into BPMN models, based on DEMOSL 3.7. This study focuses on the latest DEMO language specification, DEMOSL 4.5, since we believe that more clarity is required to specify consistent, well-motivated transformation specifications. We present a list of main requirements for developing transformation specifications to transform concepts represented in a Coordination Structure Diagram and Process Structure Diagram of DEMO into corresponding concepts in a BPMN collaboration diagram. The article makes three contributions: (1) Generic requirements for developing DEMO-to-BPMN transformation specifications; (2) Nine transformation scenarios that are validated by multiple demonstration cases; and (3) A comprehensive college case that demonstrates all transformation scenarios.

show abstract

Section: Methodsmentioning

confidence: 99%

Identifying Scenarios to Guide Transformations from DEMO to BPMN

Vries

Bork

2021

Advances in Enterprise Engineering XIV

View full text Add to dashboard Cite

show abstract

“…One of the research topics in the field of DEMO is the integration and combination of other modelling methods and notations [25,19,16,17]. When we follow the recommendations of these publications, the best way to support the combination of modelling methods is to have a tool that supports various modelling methods and notations.…”

Section: Requirement 2 the Tool Must Be Fully Compliant With The Demo...mentioning

confidence: 99%

“…At the same time, there is an increasing uptake of DEMO in practice. The latter is illustrated by the active usage (and certification) community5, reported cases concerning the use of DEMO [4,1] and [7, chapter 19], as well as integration with other mainstream enterprise modelling approaches such as ArchiMate [15,25] and BPMN [2,19,12].…”

Section: Introductionmentioning

confidence: 99%

Towards Enterprise-Grade Tool Support for DEMO

Mulder

Proper

2020

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

The Design and Engineering Methodology for Organisations (DEMO) method is a core method within the discipline of Enterprise Engineering (EE). It enables the creation of so-called essential models of organisations, which are enterprise models focusing on the organisational essence of an organisation, primarily in terms of the actor roles involved, and the business transactions between these actor roles. The DEMO method has a firm theoretical foundation. At the same time, there is an increasing uptake of DEMO in practice. With the increased uptake of DEMO also comes a growing need for enterprisegrade tool support. In this paper, we therefore report on a study concerning the selection, configuration, and extension, of an enterprise-grade tool platform to support the use of DEMO in practice. The selection process resulted in the selection of Sparx Enterprise Architect for further experimentation in terms of configuration towards DEMO. The configuration of this tool framework to support DEMO modelling, also provided feedback on the consistency and completeness of the DEMO Specification Language (DEMOSL), the specification language that accompanies the DEMO method.

show abstract

“…BPMN models are prevalent in industry and offer modeling flexibility, but the models are often incomplete, since they are not derived from theoretically-based, consistent coordination patterns [2]. Others [3] identified the need to generate BPMN models from DEMO models, based on transformation specifications. Yet, the specifications did not consider the complexity of hierarchical structures in DEMO models.…”

Section: Introductionmentioning

confidence: 99%

“…According to a study by Decosse et al [7], the AM and FM "are necessary if you are going to develop or select applications". The conceptual knowledge embedded in the PM is similar to the BPMN collaboration diagram [3]. Yet, BPMN is widely adopted by industry [8] and facilitates simulation and workflow automation, as demonstrated by BPMN-based industrial tools, such as ADONIS, Camunda and Bizagi.…”

Section: Introductionmentioning

confidence: 99%

Empirical Evaluation of a New DEMO Modelling Tool that Facilitates Model Transformations

Gray

Vries

2020

Lecture Notes in Computer Science

View full text Add to dashboard Cite

The engineering methodology for organizations (DEMO) incorporates an organization construction diagram (OCD) and transaction product table (TPT) to depict a consolidated representation of the enterprise in terms of actor roles that coordinate in consistent patterns on different transaction kinds. Although managers find the OCD useful due to its high level of abstraction, enterprise implementers and operators prefer detailed flow-chart-like models to guide their operations, such as business process model and notation (BPMN) models. BPMN models are prevalent in industry and offer modeling flexibility, but the models are often incomplete, since they are not derived from theoreticallybased, consistent coordination patterns. This study addresses the need to develop a DEMO modeling tool that incorporates the novel feature of transforming userselected parts of a validated OCD, consistently and in a semi-automated way, into BPMN collaboration diagrams. The contribution of this article is two-fold: (1) to demonstrate the utility of the new DEMO-ADOxx modelling tool, including its model transformation ability; and (2) to empirically evaluate the usability of the tool.

show abstract

Converting DEMO PSI Transaction Pattern into BPMN: A Complete Method

Cited by 12 publications

References 8 publications

Identifying Scenarios to Guide Transformations from DEMO to BPMN

Identifying Scenarios to Guide Transformations from DEMO to BPMN

Towards Enterprise-Grade Tool Support for DEMO

Empirical Evaluation of a New DEMO Modelling Tool that Facilitates Model Transformations

Contact Info

Product

Resources

About