Occurrence-Oriented Design Strategy for Developing Business Process Monitoring Systems

Developing provenance-aware query systems: an occurrence-centric approach

“…Unlike these approaches, herein, a holistic perspective of system dynamics is proposed that enhances the monitoring of business processes as a whole [17]. Specifically, when the dynamics of the system are defined as a set of processes accomplished by following several protocols, a three-dimensional business process monitoring approach is suggested, in which structure (objects), behavior (events, states, state changes), and guidance (protocols, processes and protocol performers) are considered simultaneously.…”

“…These three elements (protocol execution, object, effect) comprise a three-dimensional artifact, termed Occurrence [17].…”

“…It should also be noted that a biobank OcSystem was developed with the goal of identifying genetic and lifestyle aspects related to cardiovascular risk factors [17], which is used as a running example throughout this article. The QRP Platform should also be mentioned, which is a Capability Maturity Model Integration (CMMI) appraisal tool for project quality management [1].…”

“…[17] for details). An occurrence identifies a specific business process execution, the target business object, and the effect.…”

“…An OcSystem is any system that allows occurrences to be comprehensively managed, both in terms of their storage using an Occurrence Base (OcBase), and in terms of the tools facilitating the exploitation of related knowledge. This is an architectural proposal in the sense that different techniques or methodologies can benefit from these ideas (in Domínguez et al [17], a specific design strategy for OcSystems, using a model-driven approach, is presented). It is important to note that an OcSystem is by nature designed to be exploited from a provenance perspective.…”