Consistency requirements in business process modeling: a thorough overview

Awadid, Afef; Nurcan, Selmin

doi:10.1007/s10270-017-0629-2

Cited by 15 publications

(12 citation statements)

References 58 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Researchers have already identified the need for transforming DEMO models into other models for various reasons, e.g.,: (1) transforming concepts from DEMO to concepts contained within the ArchiMate business layer meta-model for the purpose of modelling the essential aspects of an enterprise first in DEMO, followed by a transformation into technological realization and implementation models [12]; (2) transforming the DEMO process models into Petri net models to facilitate simulation [12,13]; (3) transforming DEMO action models into BPMN models [14,15]; and (4) transforming DEMO organization construction diagrams into BPMN collaboration diagrams to semiautomate DEMO-to-BPMN transformations [16]. As indicated in Fig.…”

Section: Demo Weaknesses Bpmn Strengthsmentioning

confidence: 99%

“…Horizontal consistency refers to consistency between models at the same development phase, such as the analysis phase, whereas vertical consistency refers to consistency between models across different phases [2]. A recent systematic literature review (SLR) highlighted that the majority of studies focus on vertical integration and raised the need to also develop approaches that address horizontal consistency amongst models [3]. Another SLR [4] on existing tools that support horizontal transformations, indicate that only 7 out of 40 prominent modelling approaches support multi-view artefact creation, whereas only 6 of these 7, provide semi-automated support with for instance "wizards in the modelling environment".…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

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: Demo Weaknesses Bpmn Strengthsmentioning

confidence: 99%

Section: Introductionmentioning

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

“…This latter two works intend to assist BP designers in choosing the appropriate types of reusable artefacts in their modelling project. Finally, a thorough SLR was reported in (Awadid & Nurcan, 2017) on consistency requirements in BP modelling with a categorization of existing consistency approaches.…”

Section: Related Workmentioning

confidence: 99%

A systematic literature review on BPMN extensions

Zarour

Benmerzoug

Guermouche

et al. 2019

BPMJ

View full text Add to dashboard Cite

Purpose Business Process Model and Notation (BPMN) is a generic language that is often extended by researchers, either for dealing with processes of specific domains or for improving the language itself. The purpose of this paper is to present a literature review that aims to determine the current state of the art of BPMN extensions and identify the gaps that should be filled in this research area. Design/methodology/approach For a comprehensive and effective analysis, a systematic literature review was conducted. After the collection and filtering of papers, 52 extensions were retained to be thoroughly examined and compared according to a set of criteria including objective, targeted domain, conformity to the extension mechanism, demonstration, implementation, etc. Findings The representation of the results in the form of tables and graphs allowed the authors to deduce several positive points on the extensions as their demonstration through concrete examples. On the other hand, the authors have observed several shortcomings and suggested recommendations for addressing them. Originality/value To the best of the authors’ knowledge, the literature review is the only one that evaluates and compares all BPMN extensions over the last four years, based on several criteria covering different aspects. Furthermore, the authors were able to verify the conformity of extensions as they were published after the introduction of the BPMN extension mechanism by the Object Management Group.

show abstract

“…In 2001, a state-of-the-art survey on multi-view modelling was devoted to approaches dealing with inconsistencies management [11]. In 2009, a systematic literature review (SLR) reported on the mechanisms tackling the specific issues of UML diagrams consistency [12], while in 2017 another SLR targeted consistency requirements in the specific case of business processes modelling [13].…”

Section: For More Details)mentioning

confidence: 99%

“…The most common publication 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 Year # of primary studies type is conference (16 of 40), which also shows a stable trend of at least one publication per year since 2009. However, publications can be considered as evenly distributed among conferences (16), workshops (13), and journals (10), while book chapters have only one occurrence. Table 4 shows the publication venues that hosted more than one analysed research study.…”

Section: Publication Venuesmentioning

confidence: 99%

Multi-view approaches for software and system modelling: a systematic literature review

2019

View full text Add to dashboard Cite

Over the years, a number of approaches have been proposed on the description of systems and software in terms of multiple views represented by models. This modelling branch, so-called multi-view software and system modelling, praises a differentiated and complex scientific body of knowledge. With this study, we aimed at identifying, classifying, and evaluating existing solutions for multi-view modelling of software and systems. To this end, we conducted a systematic literature review of the existing state of the art related to the topic. More specifically, we selected and analysed 40 research studies among over 8600 entries. We defined a taxonomy for characterising solutions for multi-view modelling and applied it to the selected studies. Lastly, we analysed and discussed the data extracted from the studies. From the analysed data, we made several observations, among which: (i) there is no uniformity nor agreement in the terminology when it comes to multi-view artefact types, (ii) multi-view approaches have not been evaluated in industrial settings and (iii) there is a lack of support for semantic consistency management and the community does not appear to consider this as a priority. The study results provide an exhaustive overview of the state of the art for multi-view software and systems modelling useful for both researchers and practitioners. Keywords Model-driven engineering • Multi-view modelling • Viewpoints • Views • Consistency 1 Introduction Conventional wisdom on Model-Based Development (MBD) suggests that separation of concerns in modelling is crucial to manage the sheer complexity of modern software systems [1]. In fact, software engineering problems intrinsically involve many domains, each with their own experts, notations, and tooling [2]. Thus, providing these experts with views of the system that are specifically tailored to particular tasks enables superior clarity and simplicity by letting Communicated by Dr. Jeff Gray.

show abstract

Consistency requirements in business process modeling: a thorough overview

Cited by 15 publications

References 58 publications

Identifying Scenarios to Guide Transformations from DEMO to BPMN

Identifying Scenarios to Guide Transformations from DEMO to BPMN

A systematic literature review on BPMN extensions

Multi-view approaches for software and system modelling: a systematic literature review

Contact Info

Product

Resources

About