Coordinating Business Processes Using Semantic Relationships

Steinau, Sebastian; Künzle, Vera; Andrews, Kevin; Reichert, Manfred

doi:10.1109/cbi.2017.53

Cited by 16 publications

(29 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…PHILharmonicFlows, the object-aware process management framework we are using as a test-bed for the concepts presented in this paper, has been under development for many years at Ulm University [2]- [4]. This section gives an overview on the concepts necessary to understand the remainder of the paper.…”

Section: A Object-aware Process Managementmentioning

confidence: 99%

“…Note that a single object and its resulting form only constitute one part of a complete PHILharmonicFlows process. To allow for complex executable business processes, many different objects and users may have to be involved [4]. It is noteworthy that users are simply special objects in the object-aware process management concept.…”

Section: A Object-aware Process Managementmentioning

confidence: 99%

“…4 shows an example of a data model instance executed at run-time. Finally, complex object coordination, which becomes necessary as most processes consist of numerous interacting business objects, is possible as well [4]. As objects publicly advertise their state information, the current state of an object can be utilized as an abstraction to coordinate with other Customer objects corresponding to the same business process through a set of constraints, defined in a separate coordination process.…”

Section: A Object-aware Process Managementmentioning

confidence: 99%

“…Requirement 6: (Coordination) As object instances can be coordinated with each other based on their current state [4], state changes due to ad-hoc changes must be handled correctly. Such state changed may arise when required steps are inserted at earlier points in an object instance lifecycle process, as the example in Requirement 3 portrays.…”

Section: Requirementsmentioning

confidence: 99%

“…As the data model instance itself does not hold any data, its execution state is defined by the data in its object instances, as well as the execution state of the coordination process. This, in turn, depends solely on the relations that exist between the object instances, as well as their current states [4]. The log-defined view of a data model instance is defined as follows.…”

Section: B Data Model Instance Level Changesmentioning

confidence: 99%

See 4 more Smart Citations

Enabling Ad-Hoc Changes to Object-Aware Processes

Andrews

Steinau

Reichert

2018

2018 IEEE 22nd International Enterprise Distributed Object Computing Conference (EDOC)

Self Cite

View full text Add to dashboard Cite

Contemporary process management systems support users during the execution of repetitive, predefined business processes. However, when unforeseen situations occur, which are not part of the process model serving as the template for process execution, contemporary process management technology is often unable to offer adequate user support. One solution to this problem is to allow for ad-hoc changes to process models, i.e., changes that may be applied on the fly to a running process instance. As opposed to the widespread activity-centric process modeling paradigm, for which the support of instance-specific ad-hoc changes is well researched, albeit not supported by most commercial solutions, there is no corresponding support for adhoc changes in other process support paradigms, such as artifactcentric or object-aware process management. This paper presents concepts for supporting such ad-hoc changes in object-aware process management, and gives insights into the challenges we tackled when implementing this kind of process flexibility in the PHILharmonicFlows process execution engine. The development of such advanced features is highly relevant for data-centric BPM, as the research field is generally perceived as having low maturity when compared to activity-centric BPM.

show abstract

Section: A Object-aware Process Managementmentioning

confidence: 99%

Section: A Object-aware Process Managementmentioning

confidence: 99%

Section: A Object-aware Process Managementmentioning

confidence: 99%

Section: Requirementsmentioning

confidence: 99%

Section: B Data Model Instance Level Changesmentioning

confidence: 99%

See 3 more Smart Citations

Enabling Ad-Hoc Changes to Object-Aware Processes

Andrews

Steinau

Reichert

2018

2018 IEEE 22nd International Enterprise Distributed Object Computing Conference (EDOC)

Self Cite

View full text Add to dashboard Cite

show abstract

Modeling Process Interactions with Coordination Processes

Steinau¹,

Andrews²,

Reichert³

2018

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

With the rise of data-centric process management paradigms, small and interdependent processes, such as artifacts or object lifecycles, form a business process by interacting with each other. To arrive at a meaningful overall business process, these process interactions must be coordinated. One challenge is the proper consideration of one-to-many and many-to-many relations between interacting processes. Other challenges arise from the flexible, concurrent execution of the processes. Relational process structures and semantic relationships have been proposed for tackling these individual challenges. This paper introduces coordination processes, which bring together both relational process structures and semantic relationships, leveraging their features to enable proper coordination support for interdependent, concurrently running processes. Coordination processes contribute an abstracted and concise model for coordinating the highly complex interactions of interrelated processes.

show abstract

Engineering a Highly Scalable Object-Aware Process Management Engine Using Distributed Microservices

Andrews

Steinau

Reichert

2018

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Scalability of information systems has been a research topic for many years and is as relevant as ever with the dramatic increases in digitization of business processes and data. This also applies to processaware information systems, most of which are currently incapable of scaling horizontally, i.e., over multiple servers. This paper presents the design science artifact that resulted from engineering a highly scalable process management system relying on the object-aware process management paradigm. The latter allows for distributed process execution by conceptually encapsulating process logic and data into multiple interacting objects that may be processed concurrently. These objects, in turn, are represented by individual microservices at run-time, which can be hosted transparently across entire server clusters. We present measurement data that evaluates the scalability of the artifact on a compute cluster, demonstrating that the current prototypical implementation of the run-time engine can handle very large numbers of users and process instances concurrently in single-case mechanism experiments with large amounts of simulated user input. Finally, the development of scalable process execution engines will further the continued maturation of the data-centric business process management field. 1 Problem Definition For decades, researchers have been examining parallelism, concurrency, and scalability in computer hard-and software. The topic of scalability also became instantly relevant to workflow management systems (WfMS) when they first showed up on the market, as they were explicitly built with large-scale applications in mind [16]. First attempts to create scalable WfMS applied existing scalable architecture principles. The resulting approaches, such as WIDE [7], OSIRIS [17], ADEPTdistribution [5], and Gridflow [6], focused on the system architecture point of view, largely ignoring other aspects, such as role assignments, permissions, and data flow. However, the process models these approaches, especially Gridflow, are meant to support, are typically high-performance production workflows, where these aspects merely play a secondary role [16].

show abstract

Coordinating Business Processes Using Semantic Relationships

Cited by 16 publications

References 22 publications

Enabling Ad-Hoc Changes to Object-Aware Processes

Enabling Ad-Hoc Changes to Object-Aware Processes

Modeling Process Interactions with Coordination Processes

Engineering a Highly Scalable Object-Aware Process Management Engine Using Distributed Microservices

Contact Info

Product

Resources

About