BPMN4KM: Design and Implementation of a BPMN Extension for Modeling the Knowledge Perspective of Sensitive Business Processes

Hassen, Mariam Ben; Keskes, Molka; Turki, Mohamed; Gargouri, Faïez

doi:10.1016/j.procs.2017.12.121

Cited by 11 publications

(4 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…At the same time, despite the described method for the development of BPMN extensions (Stroppi et al, 2011a;, most of the proposed extensions in the literature were created ad hoc; without any method or coordination with the previously existing extensions. Therefore, they do not constitute a coherent proposal for the development of BPMN or the preparation of a version of BPMN dedicated to healthcare (Hassen et al, 2017;. Their use by individual researchers or practitioners may, therefore, constitute not a facilitation of but a hindrance in the exchange of knowledge.…”

Section: Scope Of Application Of Bpmnmentioning

confidence: 99%

“…, 2011a; Braun and Schlieter, 2014), most of the proposed extensions in the literature were created ad hoc; without any method or coordination with the previously existing extensions. Therefore, they do not constitute a coherent proposal for the development of BPMN or the preparation of a version of BPMN dedicated to healthcare (Hassen et al. , 2017; Braun and Esswein, 2014).…”

Section: Literature Reviewmentioning

confidence: 99%

“…Their use by individual researchers or practitioners may, therefore, constitute not a facilitation of but a hindrance in the exchange of knowledge. This hampers both the comprehensibility and comparability of the developed extensions and hinders the implementation of the extensions in the BPMN modeling tools (Hassen et al. , 2017).…”

Section: Literature Reviewmentioning

confidence: 99%

See 2 more Smart Citations

Proposal of BPMN extension with a view to effective modeling of clinical pathways

Szelągowski

Biernacki

Berniak-Woźny

et al. 2022

BPMJ

View full text Add to dashboard Cite

PurposeThe aim of the article is to propose BPMN extensions that facilitate the modeling of Clinical Pathways in a way that enables for various groups of users, the transfer of a much wider range of information in the form of process models without compromising their readability and usefulness.Design/methodology/approachThe paper uses the design science research methodology (DSRM) and covers phases of a design-oriented research project extending BPMN notation for clinical pathway modeling.FindingsThe article proposes extensions of BPMN in 5 areas, enabling standardization of the description of business processes of different natures and complexity and in turn meeting the needs and requirements of modeling clinical pathways and, more broadly speaking, knowledge-intensive business processes (kiBPs) in general. As shown by the evaluation carried out among medical personnel, the proposed extensions allow for the readable transfer of a considerably larger body of information relevant to the planned, conducted and assessed therapy (kiBPs) than the current BPMN 2.0 standard.Originality/valueThe BPMN extensions proposed in the article fill the gaps in this notation and do not require users to know many notations, which in practice is unrealistic. Defined extensions to the BPMN specification makes it possible to standardise the description of processes of different natures and levels of complexity. In this way, both simplified models (and views of models) dedicated to users unfamiliar with BPMN and models (or views) using advanced possibilities provided by BPMN can be based on one standard, even if they use only a small part of its possibilities.

show abstract

Section: Scope Of Application Of Bpmnmentioning

confidence: 99%

Section: Literature Reviewmentioning

confidence: 99%

See 1 more Smart Citation

Proposal of BPMN extension with a view to effective modeling of clinical pathways

Szelągowski

Biernacki

Berniak-Woźny

et al. 2022

BPMJ

View full text Add to dashboard Cite

show abstract

“…For work where the extension is represented and implemented in the same way, only the most recent publication is retained. For example, the papers of Ben Hassen, Keskes, Turki and Gargouri (2017), Ben Hassen et al (2017a) and Ben Hassen et al (2017b present similar extensions in terms of objective, representation and implementation. Thus, only the paper of Ben Hassen, Keskes, Turki and Gargouri (2017) was selected.…”

Section: Bpmn Extensionsmentioning

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