An Aspect Oriented Approach for Implementing Situational Driven Adaptation of BPMN2.0 Workflows

Patiniotakis, Ioannis; Papageorgiou, Nikos; Verginadis, Yiannis; Apostolou, Dimitris; Mentzas, Gregoris

doi:10.1007/978-3-642-36285-9_44

Cited by 10 publications

(7 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Besides rather task-driven approaches (e.g. Dorn et al, 2010), first concepts are evolving that apply the EDBPM paradigm in order to handle exceptional cases in knowledge intense business processes (Grambow et al, 2012;Hermosillo et al, 2010;Patiniotakis et al, 2013;Zhao and Paschke, 2013). These approaches try to utilize CEP for detecting relevant situations in order to adapt the underlying process according to a predefined procedure.…”

Section: Synthesizing and Analyzing The Current State Of Researchmentioning

confidence: 99%

Event-Driven Business Process Management: where are we now?

Krumeich

Weis

Werth

et al. 2014

Business Process Mgmt Journal

View full text Add to dashboard Cite

Purpose – The business operations of today's enterprises are heavily influenced by numerous of internal and external business events. With the Event Driven Architecture and particularly the Complex Event Processing (CEP), the technology required for identifying complex correlations in these large amounts of event data right after its appearance has already emerged. The resulting gain in operational transparency builds the foundation for (near) real-time reactions. This motivated extensive research activities especially in the field of Business Process Management (BPM), which essentially coined the term Event-Driven BPM (EDBPM). Now, several years after the advent of this new concept, the purpose of this paper is to shed light to the question: where are we now on our way towards a sophisticated adoption of the CEP technology within BPM? Design/methodology/approach – The research methodology of this paper is a structured literature analysis. It basically follows the procedure proposed by vom Brocke et al. (2009). This verified five-step process – entitled “Reconstructing the giant” – allowed a rigorous study. As a result, various research clusters were derived, whose state-of-the-art exposed existing research gaps within EDBPM. Findings – First of all, the paper provides a concise conceptual basis on different application possibilities of EDBPM. Afterwards, it synthesizes current research into six clusters and highlights most significant work within them. Finally, a research agenda is proposed to tackle existing research gaps to pave the way towards fully realizing the potentials of the paradigm. Originality/value – So far, a comparable study of the current state-of-the-art within EDBPM is non-existent. The findings of this paper, e.g. the proposed research agenda, help scholars to focus their research efforts on specific aspects that need to be considered in order to advance the adoption of the CEP technology within BPM.

show abstract

Section: Synthesizing and Analyzing The Current State Of Researchmentioning

confidence: 99%

Event-Driven Business Process Management: where are we now?

Krumeich

Weis

Werth

et al. 2014

Business Process Mgmt Journal

View full text Add to dashboard Cite

show abstract

“…The SAN framework has been coupled with an aspect-oriented extension of BPMN2.0 in order to enable the execution of BPMN2.0 processes and support business process adaptation [3]. In that work, SANs are used to monitor the process execution environment and describe meaningful reactions to problems.…”

Section: Fig 1 Basic Modeling Primitives Of Sansmentioning

confidence: 99%

“…This dynamic behaviour of SANs along with the use of AO4BPMN2.0 (aspect-oriented extension of BPMN2.0, presented in [3]), induces flexibility in collaborative business processes. Abstract actions are leaf nodes in SANs that when visited (during SAN traversal), they determine on-the-fly the tasks they should be performed, selecting them from a repository of alternative actions, called Action Pool.…”

Section: Flexibility Approachmentioning

confidence: 99%

“…All components along with their extensions were coded using Java programming language. The Adaptation Manager component handles the coupling of SAN engine with the aspect-oriented extension of BPMN2.0 (presented in [3]) in order to enable the execution of BPMN2.0 processes and support business process adaptation. Its primary role is to closely monitor the execution of process instances and activate the corresponding advices based on SAN traversal (further details can be found in [3]).…”

Section: Algorithm and Implementationmentioning

confidence: 99%

“…We use the nuclear crisis management scenario [3], where a large quantity of radioactive substance is accidentally released in the atmosphere. A number of mitigating actions take place based on a predefined collaborative process that involves several different actors, authorities and services (e.g.…”

Section: Illustrative Scenariomentioning

confidence: 99%

See 2 more Smart Citations

Collaborative Process Flexibility Using Multi-Criteria Decision Making

Patiniotakis

Papageorgiou

Apostolou

et al. 2013

IFIP Advances in Information and Communication Technology

Self Cite

View full text Add to dashboard Cite

Abstract. The ability to deal with both foreseen and unforeseen changes in a collaborative process (also known as Collaborative Process flexibility) is considered critical for the business process management systems. In this paper, we present an approach that uses a modeling framework and engine called Situation Action Network (SAN), along with multi-criteria decision making methods and techniques (MCDM). Such combination introduces event-driven flexibility in collaborative processes. We discuss and implement appropriate notions and mechanisms in order to alleviate a part of the modeler's effort during the design of hierarchical rules (i.e. SAN trees). This increases their run time flexibility and support the adaptation of collaborative business processes. We validate our approach using an illustrative scenario taken from the nuclear crisis management domain.

show abstract

A hybrid approach for aspect‐oriented business process modeling

Jalali¹,

Maggi

Reijers

2018

J Software Evolu Process

View full text Add to dashboard Cite

Separation of concerns has long been an important strategy to deal with complexity when developing a system. Some concerns (like security) are scattered through the whole system, and different modules are tangled to such concerns. These concerns are known as cross-cutting concerns.When the system in question is a business process, cross-cutting concerns are aimed at being encapsulated by Aspect-Oriented Business Process Modeling. However, the state-of-the-art techniques in this field lack efficient mechanisms that (1) support composition of cross-cutting concerns that can be defined in parallel to (a part of) a process model and (2) enable specifying both mandatory and optional cross-cutting concerns. To address these limitations, this paper proposes a new Aspect-Oriented Business Process Modeling approach. The approach is hybrid since it is based on declarative rules to relate imperative cross-cutting concerns and imperative business process models. The approach is explained, formally grounded with precise semantics, and used accordingly to implement the artifacts that support modeling and enactment of business processes in the proposed fashion as a proof of concept. In addition, the approach is evaluated on the basis of the Technology Acceptance Model during a workshop session. The result shows that participants perceived the approach usable and easy to use. KEYWORDS aspect orientation, business process modeling, cross-cutting concerns, declarative rules, hybrid models INTRODUCTIONSeparation of concerns is an important strategy for people to deal with complexity. This strategy has been widely used and adopted in developing systems where designers can divide the specifications of systems into smaller individual modules. These modules can be managed, understood, and changed separately but integrated into a comprehensive, overall specification. The lack of a proper separation can lead to very intertwined complex systems, which are hard to be changed and managed.Business processes are examples of such systems, which can be defined through sets of constraints to fulfill specific goals. These constraints specify how activities in a business process can be managed, and they are categorized into 2 major groups. One group consists of procedural flow-based constraints that specify how a business process should be performed step by step. The other group consists of very flexible models suitable for specifying processes characterized by high variability, which can hardly be specified as a predetermined procedure. We call the models in the first group imperative models while those in the second group declarative models. 1 Imperative models specify the behavior of flow-oriented and rigid business processes. In these models, the behavior of a process is specified explicitly. Imperative models can be expressed using Business Process Model And Notation (BPMN), 2 Yet Another Workflow Language (YAWL), 3 Petri nets, etc. In contrast, declarative models allow all behavior to happen unless it is explicitly forbidden. Thus, they suit...

show abstract

An Aspect Oriented Approach for Implementing Situational Driven Adaptation of BPMN2.0 Workflows

Cited by 10 publications

References 14 publications

Event-Driven Business Process Management: where are we now?

Event-Driven Business Process Management: where are we now?

Collaborative Process Flexibility Using Multi-Criteria Decision Making

A hybrid approach for aspect‐oriented business process modeling

Contact Info

Product

Resources

About