Fig 5 - uploaded by Nick R. T. P. van Beest
Content may be subject to copyright.
Source publication
In distributed business process support environments, process interference from multiple stakeholders may cause erroneous process outcomes. Existing solutions to detect and correct interference at runtime employ formal verification and the automatic generation of intervention processes at runtime. However, these solutions are limited in their gener...
Contexts in source publication
Context 1
... for 19: end procedure correctness during execution. In Fig. 5, the architecture incor- porating the framework is represented graphically. The Process Modeller (PM) provides the design tools for the specification of the business process. The business process modelled by the PM uses activities that are available in the Service Repository (SR) by means of service operations. The SR contains a list ...
Context 2
... resolve this interference, an intervention process is generated. Fig. 8 shows the intervention process as generated by the IPG (see Fig. 5), including monitoring checkpoints generated and placed. Note that the checkpoints differ from Fig. 7, as the intervention process only concerns the request for a wheelchair. That is, it is not necessary to include checkpoints specific for the home ...
Similar publications
![Fig. 5.1 A generic monitoring framework (inspired by [2])](profile/Marco-Montali/publication/307934009/figure/fig3/AS:667948528185366@1536262747764/A-generic-monitoring-framework-inspired-by-2_Q320.jpg)
Monitoring is an activity in which a running system is observed, so as to become aware of its state. The fact that the system is observed makes monitoring complementary to approaches like formal verification and validation, which are tailored to assess the quality and trustworthiness of the system before the execution.
Software development for robotic systems is traditionally performed based on simulations, manual code implementation, and testing. However, this software development approach can cause safety issues in some scenarios, including multiple robots sharing a workspace. When different robots are executing individual planned tasks, they may collide when n...
Ensuring the compliance of developed software with security requirements is a challenging task due to imprecision on the security guidelines definition, and to the lack of automatic and formal means to lead this verification. In this paper, we present our approach that aims at integrating the formal specification and verification of security guidel...
Formal verification techniques provide a way to determine whether regulatory doc-uments are consistent and whether implementations conform to them. To apply these techniques a formal description of the regulation needs to be extracted. We present a framework, under which NLP techniques can be brought to bear, to aid a requirements engineer in extra...
People-driven service engagements involve communication over channels such as chat and email. Such engagements should be understood at the level of the commitments that the participants create and manipulate. Doing so provides a grounding for the communications and yields a business-level accounting of the progress of a service engagement. Existing...
Citations
... The idea of additional mechanisms that monitor correctness of transaction execution refers to another study (van Beest and Bucur, 2013). The authors propose an automated framework for the runtime verification and correction of business processes to avoid interferences. ...
The authors offer a method for detecting potentially incorrect execution of concurrent business processes. It is achieved by using symbolic execution of business process descriptions. The proposed method provides six steps: create a detailed business process description, define transactions, define the incorrect business process execution, create a tree of executable scenarios, calculate the results of the concurrent execution and identify scenarios leading to incorrect results. The proposed algorithm applies to both formally and informally described processes. The method was applied to analysis of different concurrent processes in e-commerce solutions, ticket distribution systems and hotel bookings.
... To handle violations of these conditions, subprocesses that comprise a set of compensation activities to restore a consistent state of the business process, called intervention patterns, can be linked with the scope for the purpose of resolving potential execution problems. By contrast, our approach does not employ the concepts of handlers, intervention processes, their generation [25], or the continuous detection of process interference [23] to deal with changing situations and focuses instead on ensuring that the activities grouped by a Situational Scope are only executed if certain situations prevail. Thus, the approach of Situational Scopes applies the concept of Dependency Scopes to situation handling and extends the concept by a metamodel to link scopes to defined situations for physical or virtual objects. ...
The automation of business processes is of vital importance for organizations to speed up their business and to lower costs. Due to emerging technologies in the field of Internet of Things, changing situations can be recognized automatically, which provides the basis for an automated adaptation of process executions in order to react to changing circumstances. Although approaches exist that enable creating self-adapting workflows, a systematic modelling approach that supports the specification of situational dependencies directly in workflow models is missing. In this paper, we tackle this issue by presenting a modelling extension called SitME that defines (i) an extensible Situation Event type, (ii) the concept of Situational Scopes, and (iii) a visual notation. As the introduced extension is language-independent, we apply the approach to BPEL to validate its practical feasibility.
