scispace - formally typeset
Search or ask a question
Topic

Business Process Model and Notation

About: Business Process Model and Notation is a research topic. Over the lifetime, 9038 publications have been published within this topic receiving 190712 citations. The topic is also known as: Business Process Modeling Notation & BPMN.


Papers
More filters
Proceedings ArticleDOI
19 Jul 2005
TL;DR: This work introduces a categorization for the classification of modeling languages and approaches used to model collaborative business processes and shows how the classification facilitates the development of methodologies for collaborativeBusiness process modeling.
Abstract: Business process modeling (BPM) is one of the key factors in defining service-oriented solutions for business collaborations. Like in traditional software engineering there is a need for adaptable methodologies to develop information and communication technology (ICT) systems supporting collaborative business processes. In this work we introduce a categorization for the classification of modeling languages and approaches used to model collaborative business processes. Considering an example, we show how the classification of modeling languages and approaches facilitates the development of methodologies for collaborative business processes.

58 citations

Proceedings ArticleDOI
03 Jan 2007
TL;DR: A survey of the most promising specifications at both levels of B2B e-commerce and discusses how individual specifications on different levels fit together - starting from business models via business processes to artifacts ready for deployment.
Abstract: In recent years business-to-business (B2B) e-commerce has been subject to major rethinking. A paradigm shift from document centric file-based interchange of business information to process-centric and service-based information exchange can be observed. On a business level, a lot of work has been done to capture business models and collaborative business processes of an enterprise. On a technical level, the focus in software development is moving towards service-oriented architectures (SOA). These transitions on both levels promise a market entry at lower costs and an easier adjustment to changing market conditions. Hence, an overwhelming quantity of specifications and approaches emerged in the past targeting the area of B2B - these are partly competing and overlapping. In this paper, we provide a survey of the most promising ones at both levels and classify them using the open-edi reference model standardized by ISO. Furthermore, we discuss how individual specifications on different levels fit together - starting from business models via business processes to artifacts ready for deployment

58 citations

Proceedings Article
01 Jan 2007
TL;DR: This paper proposes a new notion of coupling, which has been used successfully in software engineering for many years and extends other work by specifically incorporating the effects of different types of connectors used on a process model’s coupling level.
Abstract: Various efforts recently aimed at the development of quality metrics for process models. In this paper, we propose a new notion of coupling, which has been used successfully in software engineering for many years. It extends other work by specifically incorporating the effects of different types of connectors used on a process model’s coupling level.

58 citations

Book ChapterDOI
08 Jun 2015
TL;DR: A conservative extension of BPMN for declarative process modeling, namely BPMn-D, is presented and it is shown that Declare models can be transformed into readable B PMN-D models.
Abstract: Traditional business process modeling notations, including the standard Business Process Model and Notation (BPMN), rely on an imperative paradigm wherein the process model captures all allowed activity flows. In other words, every flow that is not specified is implicitly disallowed. In the past decade, several researchers have exposed the limitations of this paradigm in the context of business processes with high variability. As an alternative, declarative process modeling notations have been proposed (e.g., Declare). These notations allow modelers to capture constraints on the allowed activity flows, meaning that all flows are allowed provided that they do not violate the specified constraints. Recently, it has been recognized that the boundary between imperative and declarative process modeling is not crisp. Instead, mixtures of declarative and imperative process modeling styles are sometimes preferable, leading to proposals for hybrid process modeling notations. These developments raise the question of whether completely new notations are needed to support hybrid process modeling. This paper answers this question negatively. The paper presents a conservative extension of BPMN for declarative process modeling, namely BPMN-D, and shows that Declare models can be transformed into readable BPMN-D models.

58 citations

Book ChapterDOI
07 Sep 2009
TL;DR: This research investigates how the processes are elicited in visualized business process models to understand how knowledge about working procedures in organizations is communicated.
Abstract: Visualized business process models are the central artifacts to communicate knowledge about working procedures in organizations. Since more organizations take the process perspective to share knowledge and make decisions, it is worth investigating how the processes are elicited.

57 citations


Network Information
Related Topics (5)
Web service
57.6K papers, 989K citations
88% related
Software development
73.8K papers, 1.4M citations
88% related
Software system
50.7K papers, 935K citations
86% related
Ontology (information science)
57K papers, 869.1K citations
85% related
Software construction
36.2K papers, 743.8K citations
84% related
Performance
Metrics
No. of papers in the topic in previous years
YearPapers
202383
2022208
2021122
2020164
2019211
2018242