• Tidak ada hasil yang ditemukan

Lecture Notes in Computer Science 5240

N/A
N/A
Protected

Academic year: 2023

Membagikan "Lecture Notes in Computer Science 5240"

Copied!
410
0
0

Teks penuh

Special thanks are due to all senior and regular members of the BPM 2008 Program Committee and their sub-referee judges for their work. We are also very grateful to the numerous people involved in organizing the BPM conference and associated satellite events.

Today and Tomorrow

Business Process Management

Scratching with the Chickens?

Although the business process community has placed a lot of emphasis on patterns, especially the famous workflow patterns, only limited support for using patterns can be found in today's business process modeling tools. While the basic control flow workflow patterns are available in almost all business process modeling tools, there is no support for the user to correctly apply these simple patterns, leading to many incorrectly modeled business processes.

1 Introduction

We distinguish three pattern usage scenarios and discuss a set of pattern compounds based on basic workflow patterns for control flow. The paper is organized as follows: In Section 2, we revisit the basic workflow patterns for control flow and define three scenarios for the use of control flow patterns during an iterative process modeling approach: (1) improvement of a single control flow edge using block-oriented pattern compounding , (2) applying a sample compound to a pair of selected control stream edges, (3) applying a base pattern to a set of selected control stream edges.

2 The Workflow Patterns Revisited

The infrastructure analyzes the consequences of applying a pattern with regard to the soundness of the resulting process model and enables only those patterns that are correctly applicable in a given context, which we describe by the category of the process fragments on which the pattern is applied relates. applied. Unfortunately, this availability of the patterns in current modeling tools is insufficient to allow users to successfully reuse proven solutions to recurring problems.

Fig. 1. The five basic workflow patterns exclusive choice, parallel split, simple merge, synchro- synchro-nization and sequence
Fig. 1. The five basic workflow patterns exclusive choice, parallel split, simple merge, synchro- synchro-nization and sequence

3 Scenario 1: Applying Patterns to a Single Edge

To determine whether a pattern can be applied correctly, the category of a fragment is important, which is defined by syntactic properties of the underlying workflow graph. The nodes of the PST, which represent the fragments, are annotated with the category of the fragment.

Fig. 2. Sound refinement of a process model by applying block-structured pattern compounds to a single edge
Fig. 2. Sound refinement of a process model by applying block-structured pattern compounds to a single edge

4 Scenario 2: Applying Patterns to a Pair of Edges

If the selected pair of edges is a pair of input/output edges of a SESE fragment, all the pattern connections we discussed for scenarios 1 and 2 are applicable, regardless of the category of the fragment. If the user selects a pair of edges where at least one of the edges is not an entrance or exit edge of a fragment, an analysis must be performed on the SESE fragments surrounding the selected edges.

Fig. 6. Adding an alternative branch pattern to two selected edges
Fig. 6. Adding an alternative branch pattern to two selected edges

5 Scenario 3: Applying Patterns to a Set of Edges

In the case of different nodes, using a pattern to merge branches also requires using another pattern to split branches again, because nodes cannot be merged. When using the synchronization pattern for the second choice e4, e5, e6, the final events can be combined into one node and no additional pass is required.

Fig. 7. Applying a single basic pattern to merge or synchronize all selected nodes/edges is not possible without introducing an error into the process model
Fig. 7. Applying a single basic pattern to merge or synchronize all selected nodes/edges is not possible without introducing an error into the process model

6 Implementation and Validation of Pattern-Based Editing

About 50% of all users who have installed plug-ins use them frequently in their daily work. 90% of all users confirmed that plug-ins help them improve the quality of their models.

7 Related Work

All three levels of process models can be built into a business process modeling tool. Unfortunately, very few practical recommendations for reusing process models are provided to business users.

8 Conclusion

Koehler, J., Vanhatalo, J.: Process anti-patterns: How to avoid the common pitfalls of business process modeling. F¨orster, A., Engels, G., Schattkowsky, T., Straeten, R.: Verification of business process quality constraints based on visual process patterns.

Review and Effects

Note that we focus on understanding a process model as the main point of evaluation. Our motivation is that in most business applications, the main purpose of a process model is to act as a communication tool [25,31].

2 A Review of Modularity and Process Modeling

Concepts and Terms

Modularization in Systems

Modularization in Process Models

Yet, an application in the field of process modeling is lacking, either by designing good decomposition operations or by testing their suitability. The aim of our research, as reported in the following paragraphs, is to contribute to a better understanding of the effects of modularization as a stepping stone towards such guidelines.

3 Research Design

We focused our search for suitable objects on three criteria: (1) presence of modularity, (2) size, and (3) access to the original creators of the models. Prior to the actual experimentation, all questions and correct answers were discussed with the makers of the models.

Fig. 1. Experiment design
Fig. 1. Experiment design

4 Results

Main Results

0.764 Total time Actual time spent on the entire experiment 0.948 Time A Actual time spent on model A in the experiment 0.641 Time B Actual time spent on model B in the experiment 0.417 – For model A there is no difference between the modular and the flattened. For model B, there is a significant difference between the modular and the flattened version in terms of the mean percentage of questions answered correctly (P = 0.001).

Supporting Results

0.726 Education University degree or not 0.453 Job type Business consultant or technical consultant 1.000 Modeling amount Estimated number of process models created 0.504. All P values ​​in this table are well greater than 0.05, so none of the factors examined signal anything close to a statistical difference between the groups at a 95% confidence level.

5 Discussion

Model Differences

The Influence of Modularity

Too few global questions were used to determine whether there is a difference in the mean percentage of questions answered correctly between using the modular or the flattened version of Model B. For local questions, there is a significant difference in terms of the mean percentage of correctly answered questions between the modular and the flat version of Model B (P=0.002).

Limitations

Where the reader of flattened model always sees the entire context, the reader of the modular version is confronted with exactly the right set of information when selecting the right subprocess. However, this does not seem too likely; an analysis of the results for model A showed no such effect.

6 Conclusion

We used the same modeling elements, the same top-down modeling direction, and roughly a similar width and width for both models on paper to limit this effect—if any (see Figure 2).

Acknowledgements

Vanderfeesten, I., Reijers, H.A., van der Aalst, W.M.P.: Evaluation of workflow process designs using cohesion and coupling metrics. Wynn, M.T., Verbeek, H.M.W., van der Aalst, W.M.P., ter Hofstede, A.H.M., Edmond, D.: Reduction rules for YAWL workflow nets with cancel regions and of-joins.

Experience Report

Major Challenges

Although BPMN is well suited for modeling workflows, the modeling team encountered a number of limitations in modeling organizational responsibilities within the workflows and the complex artifact structure supported by the business processes. In particular, simple role-based navigation and cross-referencing between roles, processes and artifacts are not directly usable, even though they are (implicitly) modeled in BPMN workflows.

Outline of the Paper

The process architecture team defined and used a number of tools that were necessary to ensure the creation of consistent and valid models. A number of practical instruments were introduced to fully leverage the work of the process architecture team and facilitate the transformation process.

2 Customizing BPMN

Process Architecture

It is clear that the process owner part is always white-box modeled. Sanity [1] cannot be guaranteed, due to the OR gate, which is allowed to reflect optional flows.

Organization Structure

Examples of such roles are "Author", "Expert", "Project Manager", "Head of Department", "Process Manager" or "Employee". Examples of the latter are "Employee of the Quality Management Department", "Review Owner" or "Head of the Testing Department".

Artifact Landscape

Examples of the use of artifacts are given in the review process in Figure 1. In the next step, the review protocol and pdf documents are transferred to the reviewers (“Request: Create Comments” interface).

Fig. 3. Information model: The gematik’s artifact landscape
Fig. 3. Information model: The gematik’s artifact landscape

3 Using BPMN Models to Generate Process Documentation

An Intranet-Based, Fully Generated Process Portal

As a consequence, it was decided to create process documentation that could be fully generated from the process model. The process portal offers a process-based, role-based and artifact-based access to the process documentation.

The Approach Taken in Developing the Process Portal

At this stage, the process portal prototype contains complete process information for those processes included in the initial process model. The portal generator, process portal presentation layer and meta-model were finalized on this basis.

Fig. 4. The review process within the process portal
Fig. 4. The review process within the process portal

4 Practical Implementation

The Process Architecture Team and the Modeling Guideline In order to implement the proposed process landscape, an internal team was

When the metamodel is complete, the main process model must be adapted to the new metamodel to ensure that the process model can be used as a basis for the portal generator. To maximize support for the modeller, these criteria are summarized in the appendix to the modeling guide.

Further Instruments Utilized by the Process Architecture Team The process architecture team used a number of other instruments to improve

On the one hand, the meta model is a tool that the architecture team can use to validate the modeling guidelines, on the other hand it serves as a basis for automatic validation of the model (via validation scripts) and for automatic generation of the process. documentation (via script generation).

5 Conclusions

The practical tools used by the process architecture team have proven to be very effective, they will be further refined as the business transformation project continues. It is clear that the business transformation will not be complete once the process modeling effort is complete.

Recommendations Based on History

We also describe the implementation of our approach as an advisory service and its evaluation. In Chapter 4 we describe the experiment we conducted to evaluate whether recommendations indeed help achieve a certain goal.

2 Overview

All tasks have a fixed duration, however tasks B and C use the same database application and if B is directly followed by C, then the combined duration of the tasks is much shorter, as there is no closing time for B and no setup time for C in addition use the data provided by B, without re-importing data. At the same time, giving recommendations based on extracted knowledge from execution logs can provide knowledge that was not available during the design of the process.

3 Log-Based Recommendation Service

  • Preliminaries
  • Recommendations
  • Trace Abstraction
  • Support
  • Trace Weight
  • Expected Outcome

The target value of each trace from Ls(ρ,e) is weighted (ω) based on the degree of matching with the partial trace. The implementation of our recommendation service sorts enabled activities according to the difference between do and don't, i.e. the bigger the difference, the more attractive the activity.

Fig. 3. Example log, with weight and support values for ρ = D, F
Fig. 3. Example log, with weight and support values for ρ = D, F

4 Evaluation Based on a Controlled Experiment

  • Experiment Design
  • Experiment Preparation
  • Experiment Execution and Data Analysis
  • Experiment Results
  • Risk Analysis

Figures 5-7 show the effect of log size on average cycle time for the 12 samples generated using the recommendations. For array and multi-array abstraction, changes in register size do not significantly affect the average cycle time.

Fig. 5. Prefix Fig. 6. Set Fig. 7. Multi-set
Fig. 5. Prefix Fig. 6. Set Fig. 7. Multi-set

5 Related Work

Adams, M., ter Hofstede, AHM, Edmond, D., van der Aalst, WMP: a service-oriented implementation of dynamic flexibility in workflows. Vanderfeesten, I., Reijers, H.A., van der Aalst, W.M.P.: Product-based workflow support: a recommendation service for dynamic workflow execution.

Process-Aware Information Systems

These work items are offered to the users by the so-called work list handler. From the user's point of view, some work items are close, while others are far away.

2 Related Work

For example, the work list handler can show the length of work queues from other sources or the position of the work item on a geographic map at the execution location. The iProcess Suite is based on Google Maps, while our framework does not rely on an external service for processing maps and positioning work items.

3 The General Framework

Fundamentals

In these cases, e is assumed to be the latest possible completion time for each cancellation region of which the work item is a part. To formalize the notion of a distance metric, a distance function is defined for each metric that gives the distance between a work item and a resource with respect to that metric.

Available Metrics

For each available mapm ∈M, there exists a function positionm : W ∪R → Coordinates that returns the current coordinates for work items and available resources on mapm. This can be measured by the number of sibling work items that the resource has already performed.

Table 2. Distance Metrics currently provided by the implementation
Table 2. Distance Metrics currently provided by the implementation

4 Implementation

The User Interface

Special colors are used to represent the different stages of the work item's life cycle. Table 3 provides an overview. When a resource clicks on a work item, the positions of the other resources to which that work item is submitted are shown.

Architectural Considerations

For example, Interface B is used by the worklist handler to learn about work items to be submitted for execution. The standard version of the worklist handler provides queues of work items in a specific state.

Fig. 1. Position of the visualisation components in the YAWL architecture
Fig. 1. Position of the visualisation components in the YAWL architecture

5 Example: Emergency Management

On these cards, work items are placed at the location where they need to be performed. By selecting one of the resources in the list, you can view the work items submitted to that resource.

Fig. 3. Examples of Geographic Maps for Disaster Management
Fig. 3. Examples of Geographic Maps for Disaster Management

6 Conclusions

Dumas, M., van der Aalst, W.M.P., and Hofstede, A.H.M.: Process-aware information systems: bridging people and software through process technology. Russell, N., van der Aalst, W.M.P., and Hofstede, A.H.M., Edmond, D.: Workflow Resource Patterns: Identification, Representation and Support Tools.

Business Process Modeling

1 Introduction

This paper presents an integrated approach that overcomes the above limitation and enables end users to become informed participants in business process modeling. It is implemented and validated by a process-enhanced groupware system - the Collaborative Task Manager (CTM) that provides enhanced end-user development capabilities.

2 Related Work

It generally allows end users to create hierarchical task lists by splitting tasks into subtasks. TDGs enable informed end-user participation in process composition by providing a workflow-like view of evolving collaborative tasks beyond the capabilities of regular email and task lists.

3 Approach

The resulting task (B''') receives a reference to the deviant Wf task (PB'), and the latter receives a reference to the deviant ad-hoc task (B''') when it is detected. While the ad-hoc task management server tracks the changes of the deviant ad-hoc task hierarchy (from B'''), the Wf server tracks the state of the deviant Wf task (PB' – started, suspended, ended).

4 Collaborative Task Manager (CTM)

Programming by Example of Weakly-Structured Process Models

This makes it possible to assess whether the deviating ad hoc task and the corresponding Wf task continue in parallel, or whether the ad hoc task is completed before the Wf task is further processed. When the Wf ends, the Wf model can be redefined by considering the deviant ad-hoc flow in addition to the original ad-hoc task hierarchies used to define the Wf.

Fig. 2. CTM to-do list
Fig. 2. CTM to-do list

SER of Weakly-Structured Process Models

From Email and To-Do to Formal Workflows

Both functionalities are provided in the 'Deployment' tab in the upper central part of Figure 5. The TDG of the created ad-hoc task can be opened from the Wf task's form in the jBPM front end and vice versa.

Fig. 5. CTM process definition environment
Fig. 5. CTM process definition environment

5 Case Study

After SL1 transferred the customer sales report data to the R/3 system, she checked the resulting invoiced amount in the system against the amount in the sales report. For this purpose, CSO created an ad hoc task 'prepare liability statement' in the task list and started preparing the document.

Table 1. Excerpt of case study metrics
Table 1. Excerpt of case study metrics

6 Conclusions

For this and other applications, it is desirable that the decomposition be unique, modular, and as thin as possible, where modular means that a local change to the workflow graph can only cause a local change of decomposition. We believe that analytics also helps in understanding large processes and finding reusable sub-processes. a), (b) Two analyzes of the same workflow graph.

Fig. 1. (a), (b) Two parses of the same workflow graph. (c) Parse tree corresponding to (a)
Fig. 1. (a), (b) Two parses of the same workflow graph. (c) Parse tree corresponding to (a)

2 The Refined Process Structure Tree

  • Fragments
  • Triconnected Components
  • Canonical Fragments and the Process Structure Tree
  • Canonical fragment)
    • Computing All Fragments from the Canonical Fragments
    • Modularity

Examples of (a) a pure bond fragment, (b) a semipure bond fragment, (c) a directed bond fragment, and (d) a bond fragment. A connection fragment F F(u v) is canonical if it is a maximal connection fragment, a directed maximal, semipure, or maximal pure connection fragment such that F is not properly contained in any connection fragment F¼ F(v u).

Fig. 3. (a) Two-terminal graph G, and (b) its undirected version U(G), where r is the return edge
Fig. 3. (a) Two-terminal graph G, and (b) its undirected version U(G), where r is the return edge

3 Computing the PST

Add these edge counts to the respective edge counts of the parent component for each shared boundary node. Restructure the tree of the three-connected components into the tree of the canonical fragments (the PST).

Fig. 11. The high-level steps of Alg. 1. Step 1: Detect the triconnected components. Step 2: Ana- Ana-lyze each triconnected component to determine whether the respective component subgraph is a fragment
Fig. 11. The high-level steps of Alg. 1. Step 1: Detect the triconnected components. Step 2: Ana- Ana-lyze each triconnected component to determine whether the respective component subgraph is a fragment

4 Conclusion

In this paper, we extend the operational guidelines approach by asserting, in addition to deadlock freedom, that there are no dead activities in a composite system. This means that R must match P if and only if it is at least possible to perform the activity "credit approved" in the composition of the online banking service and the requester.

2 Preliminaries

Open Nets

Two open networks M and N are composable if all components (except interfaces) are pairwise separated. Clearly, we are mostly interested in constructing open networks in such a way that the assembly is deadlock-free.

Fig. 1. The running example process N c and two strategies M 1 and M 2
Fig. 1. The running example process N c and two strategies M 1 and M 2

Operating Guidelines

Let M be an open net that obeys the above assumption and let Y be the set of all reachable Petri net labels M∗ =interior M. The working bus of an open net OGN is not a special marked automaton such that an open net M matches an OGN if and only if M strategy forN.

3 Covering Open Net Nodes

Deciding the Coverage of Open Net Nodes

The most permissive strategy for N is the open network MPN = (P, T , F, I, O, m0, Ω), whose behavior corresponds exactly to the transition system (Q, C, δ, q0) with. The knowledge K :Q → P(MarkN) that OGN has about the possible markings of N in state q ∈ Q is defined by K(q) =K(mq).

Fig. 3. The initial part of the most permissive strategy MP N c for N c which has been constructed according to Def
Fig. 3. The initial part of the most permissive strategy MP N c for N c which has been constructed according to Def

A Finite Representation of All Cover X -Strategies

In the following, we formalize annotated automata augmented with a global constraint and define the corresponding relation between an open net and such an annotated automaton. Finally, we are ready to construct the operating guideline with global constraint OGψX(N) of an open netN as a representation of the setStratCoverX(N) of all CoverX strategies forN.

Discussion

The example suggests that the magnitude of the global constraint will be much smaller in practice. In addition, when we match M with OGψX(N), we need to check whether the global constraint is satisfied by the assignmentγM.

4 Related Work

OGψ The global constraint is a conjunction of at most |X|disjunctions, where each disjunction may consist of at most |Q|literals.

5 Conclusion

Massuthe, P., Schmidt, K.: Operating Guidelines - an Automata-theoretical basis for the service-oriented architecture. ed.).

Using a Simulation-Based Graph Edit Distance

Choreography can block, because the customer does not receive a rejection message from the airline. However, this trace does not provide information about which service should be changed in which way to avoid blocking.

Fig. 1. Choreography between travel agency, airline, and customer. The choreography can deadlock, because the customer does not receive a refusal message from the airline.
Fig. 1. Choreography between travel agency, airline, and customer. The choreography can deadlock, because the customer does not receive a refusal message from the airline.

2 Service Models

Service Automata and Operating Guidelines

A service can be controlled if there exists a partner service such that their compositions ⊕ S (i.e., the choreography of the service and the partner) are deadlock-free. It does not satisfy the formula ϕ(q2) = (?confirmation∧?rejection) for AND's state q2 because the service automaton does not receive a rejection message in the simulated state q1.

Fig. 3. A service automaton S customer modeling the customer service of Fig. 1 (a) and the operating guideline O agency ⊕ airline of the composition of travel agency and airline service (b)
Fig. 3. A service automaton S customer modeling the customer service of Fig. 1 (a) and the operating guideline O agency ⊕ airline of the composition of travel agency and airline service (b)

Fixing Deadlocking Choreographies

3 Graph Similarities

Both the discount factorp and the label similarity function L can be chosen arbitrarily to adjust the result of the similarity algorithm. 5 and assume a discount factor p= 0.5 and a label similarity function L that assigns 1.0 to identical labels and 0.5 to any other pair of labels.

4 A Matching-Based Edit Distance

Simulation-Based Edit Distance

These editing actions define basic editing actions whose similarity is determined by the edge similarity functionL. 1, the resulting modification actions (cf. Table 1) simply insert or remove edges to current nodes rather than to new nodes.

Combining Formula-Checking and Graph Similarity

In a permutation, every outgoing edge of a state of the automaton must be present as first element of a pair (a), every outgoing edge of a state of the OG that is part of the label set β must be present as second element of a few (b). Similarly, del(q1) calculates the cost of deleting the entire subgraph of the automaton from stateq1.

Fig. 6. Matching cannot be achieved solely by transition insertion. The service automa- automa-ton (a) does not match with the OG (b) because of a missing ?b-branch
Fig. 6. Matching cannot be achieved solely by transition insertion. The service automa- automa-ton (a) does not match with the OG (b) because of a missing ?b-branch

Matching-Based Edit Distance

5 Complexity Considerations and Experimental Results

The length of OG formulas is bounded by the maximum degree of nodes, which is again bounded by the interface I. The “search space” column in Table 2 lists the number of acyclic deterministic services denoted by OG.

Table 2. Experimental results
Table 2. Experimental results

6 Related Work

The proposed algorithm exploits the compact representation of the OG and makes it possible to efficiently find the most similar service from over 102,000 candidates. Furthermore, several service mediation approaches such as [33] assume aggregate perception of the participants' internal states during runtime.

7 Conclusion and Future Work

The difference between all mentioned related approaches and the setting of this paper is that these approaches either focus on low-level programs or mainly aim to find structural (certainly not simulation-based) differences between two given services and are therefore not applicable to finding most similar performance from a large set (cf. Table 2) of candidates. K¨uster, J.M., Gerth, C., F¨orster, A., Engels, G.: Detecting and resolving process model discrepancies in the absence of a change log.

Business Process Implementations

Realization of this approach requires calculation of the expected component coupling based on a given process model. Finally, we use this information to calculate the expected coupling of the object's lifecycle components.

2 Example and Background

For the implementation of the alumni day process, we distribute the process activities among ten BSMs (Budget, Cafeteria, Date, etc.). In the next section, we explore how the implementation of different workflow patterns using BSMs introduces threads between the BSM components and thus contributes to the coupling of the resulting assembly model.

Fig. 1. Process Model for Alumni Day Organization
Fig. 1. Process Model for Alumni Day Organization

3 Implementing Workflow Patterns Using BSMs

An example containing an example of both of these workflow patterns is shown in Fig. In a solution to this pattern, the decision must be placed in one of the BSMs, as shown in Fig.

Fig. 7. WP2 & WP3 ExampleWP2 Parallel Split & WP3
Fig. 7. WP2 & WP3 ExampleWP2 Parallel Split & WP3

4 Predicting Coupling of BSM Implementations

Downstream and upstream control objects can be calculated for a given process model using data flow analysis techniques [9]. Possible revisions include identification of objects that can be represented by an aggregated life cycle and refactoring control flow in the process model.

Fig. 13. Downstream and Upstream Control Objects in a Process Model
Fig. 13. Downstream and Upstream Control Objects in a Process Model

7 Conclusions and Future Work

In particular, we will focus on open workflow networks (oWFNs) [2] which extend workflow networks [3] with interface sites. Another Workflow Language (YAWL) [7], the workflow language that is based on the analysis of workflow patterns [8].

2 Background on Process Instantiation

Most notably, process instantiation requires the definition of the initial state of the new instance. A definition of an initial state is explicit if the initial state is part of the definition of the process model.

Fig. 1. Entry points in different process modeling languages
Fig. 1. Entry points in different process modeling languages

3 A Framework for Process Instantiation

  • When to Create a New Instance?
  • Which Entry Points Are Activated?
  • For Which Non-activated Start Events Are Subscriptions Created?
  • How Long Are Subscriptions Kept?
  • A Classification of Instantiation Semantics

Example: In a second process model for invoice management (Figure 12), the start events “receive paper invoice” and “receive electronic invoice” appear again. All patterns associated with start events (A-4, A-5, all S patterns, and all U patterns) rely on the ability to specify single or multiple event triggers (C-4, C-5).

Fig. 3. C-1 Ignorance in a YAWL net
Fig. 3. C-1 Ignorance in a YAWL net

4 Discussion

Based on the CASU framework, we classified six of the most prominent languages ​​according to their instantiation semantics. In this regard, the explicit description of instantiation semantics using the CASU framework can ultimately help to reduce ambiguity and the number of errors in conceptual process modeling.

Constraints in Scientific Workflows

The task of setting temporal constraints described in this paper is to assign a set of coarse and fine-grained upper bound temporal constraints to scientific workflows. In this paper, a probabilistic strategy for setting both coarse- and fine-grained temporal constraints is proposed.

2 Motivating Example and Problem Analysis

Therefore, we also need to place fine-grained temporal constraints on each activity. Specifically, for this example workflow segment, an overall coarse-grained temporal constraint and twelve fine-grained temporal constraints for activities X1 through X12 must be set.

3 Probability Based Temporal Consistency

The distribution of activity durations can be obtained from workflow system logs. Without losing generality, we assume all the activity durations follow the

The activity durations are independent to each other

The purpose of probabilistic temporal consistency is to facilitate the efficiency of setting temporal constraints. Therefore, the probability-based temporal consistency supports the setting of both coarse-grained and fine-grained temporal constraints.

Fig. 2. Probability based temporal consistency
Fig. 2. Probability based temporal consistency

4 Probabilistic Strategy for Setting Temporal Constraints

The weight for each activity in the sequence building block is 1 since they only need to be executed once. As depicted in Figure 5, the parallelism building block contains two paths that execute in a parallel relationship.

Fig. 3. Sequence building block
Fig. 3. Sequence building block

Gambar

Fig. 2. Sound refinement of a process model by applying block-structured pattern compounds to a single edge
Figure 10 shows a screen capture of our prototype implementation where we added pattern support in the form of additional plug-ins to IBM WebSphere Business  Mod-eler, which is an Eclipse-based commercial business process modeling tool
Fig. 1. Experiment design
Fig. 2. Flattened versions of the used process models
+7

Referensi

Dokumen terkait

By using our application, users can get hassle free service at home that saves time and money.QuickAi provides features that a user can see available bus or tickets, price and other