Integrated Modeling of Process- and Data-Centric Software Systems with PHILharmonicFlows

Process- and data-centric software systems require a tight integration of processes, functions, data, and users. Thereby, the behavioral perspective is described by process models, while the information perspective is captured in a data model. Eliciting and capturing requirements of such software systems in a consistent way is a challenging task, demanding that both process and data model are well aligned and consistent with each other. While traditional software modeling languages do not allow for an explicit integration of data and process models, activity-centric process modeling languages tend to neglect the role of data as a driver of process execution; i.e., business objects are usually outside the control of the process, normally stored in external databases. To overcome this drawback, PHILharmonicFlows provides a comprehensive framework for enabling object-aware process support. In addition, a sound specification of process- and object-centric software systems becomes possible. In this paper, we present a requirements modeling approach that provides methodological guidance for modeling large process- and data-centric software systems based on PHILharmonicFlows. Such guidance will foster the introduction of respective software systems in the large scale

Data in Business Process Models. A Preliminary Empirical Study

Traditional activity-centric process modeling languages treat data as simple black boxes acting as input or output for activities. Many alternate and emerging process modeling paradigms, such as case handling and artifact-centric process modeling, give data a more central role. This is achieved by introducing lifecycles and states for data objects, which is beneficial when modeling data-or knowledge-intensive processes. We assume that traditional activity-centric process modeling languages lack the capabilities to adequately capture the complexity of such processes. To verify this assumption we conducted an online interview among BPM experts. The results not only allow us to identify various profiles of persons modeling business processes, but also the problems that exist in contemporary modeling languages w.r.t. The modeling of business data. Overall, this preliminary empirical study confirms the necessity of data-awareness in process modeling notations in general

Knowledge-Intensive Processes: Characteristics, Requirements and Analysis of Contemporary Approaches

Engineering of knowledge-intensive processes (KiPs) is far from being mastered, since they are genuinely knowledge- and data-centric, and require substantial flexibility, at both design- and run-time. In this work, starting from a scientific literature analysis in the area of KiPs and from three real-world domains and application scenarios, we provide a precise characterization of KiPs. Furthermore, we devise some general requirements related to KiPs management and execution. Such requirements contribute to the definition of an evaluation framework to assess current system support for KiPs. To this end, we present a critical analysis on a number of existing process-oriented approaches by discussing their efficacy against the requirements

Towards Schema Evolution in Object-aware Process Management Systems

Enterprises want to improve the lifecycle support for their businesses processes by modeling, enacting and monitoring them based on process management systems (PrMS). Since business processes tend to change over time, process evolution support is needed. While process evolution is well understood in traditional activity-centric PrMS, it has been neglected in object-aware PrMS so far. Due to the tight integration of processes and data, in particular, changes of the data and process schemes must be handled in an integrated way; i.e., the evolution of the data schema might affect the process schema and vice versa. This paper presents our overall vision on the controlled evolution of object-aware processes. Further, it discusses fundamental requirements for enabling the evolution of object-aware process schemas in PHILharmonicFlows, a framework targeting at comprehensive support of object-aware processes

Enabling Fine-grained Access Control in Flexible Distributed Object-aware Process Management Systems

To increase flexibility, object-aware process management systems enable data-driven process execution and dynamic generation of form-based tasks at run-time. Therefore, a powerful access control concept becomes necessary to define which data elements users may read or write at a given point in time during process execution. The access control concept we present in this paper has been realized in the context of the PHILharmonicFlows framework, which provides a distributed data-driven process execution engine. We present solutions that allow for complex as well as fine-grained permissions and roles, which are granted depending on the states of processes and data elements. We show how one can resolve authorization queries in real-time over multiple business objects and process instances. This constitutes a significant advantage over centralized access control systems

Object-aware Process Support in Healthcare Information Systems: Requirements, Conceptual Framework and Examples

The business processes to be supported by healthcare information systems are highly complex, producing and consuming a large amount of data. Besides, the execution of these processes requires a high degree of flexibility. Despite their widespread adoption in industry, however, traditional process management systems (PrMS) have not been broadly used in healthcare environments so far. One major reason for this drawback is the missing integration of business processes and business data in existing PrMS; i.e., business objects (e.g., medical orders, medical reports) are usually maintained in specific application systems, and are hence outside the control of the PrMS. As a consequence, most existing PrMS are unable to provide integrated access to business processes and business objects in case of unexpected events, which is crucial in the healthcare domain. In this context, the PHILharmonicFlows framework offers an innovative object-aware process management approach, which tightly integrates business objects, functions, and processes. In this paper, we apply this framework to model and control the processes in the context of a breast cancer diagnosis scenario. First, we present the modeling components of PHILharmonicFlows framework applied to this scenario. Second, we give insights into the operational semantics that governs the process execution in PHILharmonicFlows. Third, we discuss the lessons learned in this case study as well as requirements from the healthcare domain that can be effectively handled when using an object-aware process management system like PHILharmonicFlows. Overall, object-aware process support will allow for a new generation of healthcare information systems treating both data and processes as first class citizens

Schema Evolution in Object and Process-Aware Information Systems: Issues and Challenges

Enabling process flexibility is crucial for any process-aware information system (PAIS). In particular, implemented processes may have to be frequently adapted to accommodate to changing environments and evolving needs. When evolving a PAIS, corresponding process schemas have to be changed in a controlled manner. In the context of object-aware processes, which are characterized by a tight integration of process and data, PAIS evolution not only requires process schema evolution, but the evolution of data and user authorization schemas as well. Since the different schemas of an object-aware PAIS are tightly integrated, modifying one of them usually requires concomitant changes of the other schemas. This paper presents a framework for object-aware process support and discusses major requirements and challenges for enabling schema evolution in object-aware PAISs

Design and Implementation of a Runtime Environment of an Object-Aware Process Management System

Contemporary business process management systems manage their processes based on the activity-centric paradigm. However, many business processes are un- or semistructured and cannot be represented adequately by the activity-centric paradigm. The fundamental reason for this insufficiency is the lack of cohesion between processes on one hand and data on the other. Object-aware process management provides a solution for this issue by tightly integrating processes with data. Data is represented as structured object types with complex data dependencies. This is mirrored in the concepts of object behavior and object interactions. Object behavior is captured in micro processes, whereas object interactions are represented by macro processes. Both micro and macro processes are integral parts of the runtime of an object-aware process management system. Furthermore, the execution of micro and macro processes is governed by process rules. The process rules advance the process state depending on the available data, react to user interactions or perform error handling. PHILharmonicFlows is a framework that aims at the proper support of object-aware processes. A prototype implementing the framework is currently under development. This thesis contributes to the prototype by describing concepts concerning process rules and by providing implementations as well. In detail, the contributions are as follows. The ongoing development of the prototype requires process rules to be easily created and altered, i.e. to enable a high maintainability. Therefore, a high level of abstraction for the process rule definitions is necessary. The Process Rule Framework enables the creation and alteration of process rules and satisfies the high maintainability requirement by leveraging functional programming devices. Using the Process Rule Framework, a high productivity can be achieved when handling process rules. Moreover, the Process Rule Framework has the possibility to be extended to a general-purpose rule engine in which rules may be created, compiled and executed during runtime. At runtime, process rules provide one of the cornerstones to object-aware process execution. This requires complex interactions between process rules, as they can trigger each other and therefore chain together. The challenge is to enable these interactions while keeping the individual process rules independent from each other and only loosely coupled. The Process Rule Manager enables the complex interactions between process rules by providing the means to coordinate and control process rule interactions. Additionally, the Process Rule Manager abstracts from the inner workings of process execution and provides a well-defined interface to interact with a micro process

Executing Lifecycle Processes in Object-Aware Process Management

Data-centric approaches to business process management, in general, no longer require specific activities to be executed in a certain order, but instead data values must be present in business objects for a successful process completion. While this holds the promise of more flexible processes, the addition of the data perspective results in increased complexity. Therefore, data-centric approaches must be able to cope with the increased complexity, while still fulfilling the promise of high process flexibility. Object-aware process management specifies business processes in terms of objects as well as their lifecycle processes. Lifecycle processes determine how an object acquires all necessary data values. As data values are not always available in the order the lifecycle process of an object requires, the lifecycle process must be able to flexibly handle these deviations. Object-aware process management provides operational semantics with built-in flexible data acquisition, instead of tasking the process modeler with pre-specifying all execution variants. At the technical level, the flexible data acquisition is accomplished with process rules, which efficiently realize the operational semantics

PHILharmonicFlows: towards a framework for object-aware process management

Companies increasingly adopt process management systems (PrMS) that offer promising perspectives for more flexible and efficient process execution. However, there still exist many processes in practice which are not adequately supported by contemporary PrMS. We believe that a major reason for this deficiency stems from the unsatisfactory integration of processes and data in existing PrMS. Despite emerging approaches that address this integration, a unified and comprehensive understanding of object-awareness in connection with process management is still missing. To remedy this deficiency, we extensively analyzed various processes from different domains which are not adequately supported by existing PrMS. As a major insight we learned that in many cases comprehensive process support requires object-awareness. In particular, process support has to consider object behavior as well as object interactions, and should therefore be based on two levels of granularity. Besides this, object-awareness requires data-driven process execution and integrated access to processes and data. This paper presents the basic properties of objectaware processes as well as fundamental requirements for their operational support. It further introduces our PHILharmonicFlows framework which addresses these requirements and enables object-aware process management in a comprehensive manner. Finally, we evaluate this framework along several process scenarios. We believe that a holistic approach integrating data, processes and users offers promising perspectives in order to overcome the numerous limitations of contemporary PrMS