Role-Based Process View Derivation and Composition

Abstract

The process view concept deploys a partial and temporal representation to adjust the visible view of a business process according to various perception constraints of users. Process view technology is of practical use for privacy protection and authorization control in process-oriented business management. Owing to complex organizational structure, it is challenging for large companies to accurately specify the diverse perception of different users over business processes. Aiming to tackle this issue, this article presents a rolebased process view model to incorporate role dependencies into process view derivation. Compared to existing process view approaches, ours particularly supports runtime updates to the process view perceivable to a user with specific view merging operations, thereby enabling the dynamic tracing of process perception. A series of rules and theorems are established to guarantee the structural consistency and validity of process view transformation. A hypothetical case is conducted to illustrate the feasibility of our approach, and a prototype is developed for the proof-of-concept purpose.

Towards Understanding Quality-Related Characteristics in Knowledge-Intensive Processes - A Systematic Literature Review

“…We have not found works that specifically focus on the quality of KIPs. Characteristics Papers C1 -Knowledge-driven [14], [27], [31], [35], [12], [2], [35], [26], [33], [17], [6] C2 -Collaboration-oriented [35], [12], [2], [3] [26], [11], [23], [23], [32], [28], [18], [17], [6], [4] C3 -Unpredictable [15], [1], [27], [35], [12], [2], [26], [11], [23], [33], [24], [37], [36], [30], [28], [14], [9], [17], [4], [36], [30], [18],…”

“…[34] C4 -Emergent [14], [27], [16], [35], [3], [26], [24], [34], [36], [28], [9], [5], [17], [20] C5 -Goal-oriented [12], [26], [18] C6 -Event-driven [3], [12], [26], [36], [30], [18], [34], [23], [33], [24] C7 -Collaboration-oriented [14], [27], [35], [33], [37], [18], [20], [11], [23], [33], [37], [34], [8], [4] C8 -Constraint-and ruledriven [14], [27], [35], [3], [12], [2], [26], [11], [23], [33],…”

UniFlexView: A unified framework for consistent construction of BPMN and BPEL process views

“…Zhao et al presented a framework to support view abstraction and concretization of WS‐BPEL processes with a rigorous view model proposed to specify the dependency and correlation between structural components of process views with emphasis on the characteristics of WS‐BPEL, and a set of rules is defined to guarantee the structural consistency between process views during transformation. Then, Zhao et al extended their previous work to incorporate role dependencies into process view derivation in order to support organizational privacy protection, authorization control, and runtime updates to the process view perceivable to a user with specific view‐merging operations. However, both approaches are designed to support only a block‐structured language, WS‐BPEL in this case, and constructing views for unstructured workflows is not possible with these approaches.…”

User Interface Derivation Based on Role-Enriched Business Process Model

“…As a scenario example, Figure 2.9 shows account receivable (AR) process and its related process views for the involved user roles [96]. Both the process and related views are represented in BPMN.…”

“…Two groups of rules are developed based on graph reduction and graph aggregation. The parameter set are the same as the one developed by J.Kolb et alX.Zhao et al[96] proposed a view derivation approach based on user role hierarchy. The dependencies between involved roles are specified in their BP model.…”