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
20 Jul 2009
TL;DR: It is argued that the effective design of flexible processes calls for a substantially different modelling paradigm: one where processes are organized as interacting business objects rather than as chains of activities.
Abstract: Mainstream business process modelling techniques promote a design paradigm wherein the activities that may be performed within a case, together with their usual execution order, form the backbone on top of which other aspects are anchored. This Fordist paradigm, while effective in standardised and production-oriented domains, breaks when confronted with processes in which case-by-case variations and exceptions are the norm. We contend that the effective design of flexible processes calls for a substantially different modelling paradigm: one where processes are organized as interacting business objects rather than as chains of activities. This paper presents a meta-model for business process modelling based on business objects. The paper also presents a real-life case study in which a number of human service delivery processes were designed using the presented meta-model. The case study demonstrates that the meta-model addresses three key flexibility requirements encountered in this domain.

45 citations

Journal ArticleDOI
TL;DR: In this article, the authors propose a methodology that addresses several aspects of the business rules lifecycle: acquisition, deployment, and evolution, assuming that business rules are expressed in terms of business concepts and corporate knowledge that are captured in a high level architecture.
Abstract: Business rules give rise to an important set of requirements on any system being developed or procured for an enterprise. While most of the work done in this area focuses on identifying and documenting business rules, we have proposed a methodology that addresses several aspects of the business rules lifecycle: acquisition, deployment and evolution. The methodology assumes that business rules are expressed in terms of business concepts and corporate knowledge that are captured in a high level architecture. The architecture proposed consists of three interconnected components: the enterprise model, the business rules model and the decision support model. This approach permits a greater variety of rules to be specified while providing an opportunity to automate the production of deployable business rules. The ability to deal with the inconsistent and ambiguous rules is crucial in capturing the conflicting requirements placed on the operation of any large scale enterprise. This paper presents a flexible deployment of business rules, which not only supports decision making in the face of conflicting requirements, but also the evolution of those requirements in the face of changing regulatory environments, competitive markets and corporate goals.

45 citations

Journal ArticleDOI
TL;DR: The xPPM method is proposed to provide a tight connection between PMs, ERs, FPs, and MVDs and to improve the reusability of predefined ERs and FPs.

45 citations

Journal Article
TL;DR: The paper describes an approach which is based on the ARIS architecture to combine tool-based enterprise models (on type level) with enterprise-wide information systems and application services.
Abstract: Business Process Management is an approach of model-oriented design, coordination and execution of business processes. Its objective is to combine tool-based enterprise models (on type level) with enterprise-wide information systems and application services. In order to fullfill this objective mechanisms and instruments for process coordination as a layer between modelling layer and execution layer have to be developed. Also feedback and change management methods must exist to involve the agents and company parties (business process owners, service centers, organizational units etc.) which are part of the managed business processes. The paper describes an approach which is based on the ARIS architecture.

45 citations

Journal ArticleDOI
TL;DR: Researchers analyzed 585 BPMN 2.0 process models from six companies and found that split and join representations, message flow, the lack of proper model decomposition, and labeling related to quality issues.
Abstract: Many organizations use business process models to document business operations and formalize business requirements in software-engineering projects. The Business Process Model and Notation (BPMN), a specification by the Object Management Group, has evolved into the leading standard for process modeling. One challenge is BPMN's complexity: it offers a huge variety of elements and often several representational choices for the same semantics. This raises the question of how well modelers can deal with these choices. Empirical insights into BPMN use from the practitioners' perspective are still missing. To close this gap, researchers analyzed 585 BPMN 2.0 process models from six companies. They found that split and join representations, message flow, the lack of proper model decomposition, and labeling related to quality issues. They give five specific recommendations on how to avoid these issues.

45 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