2007 IEEE 23rd International Conference on Data Engineering 2007
DOI: 10.1109/icde.2007.369018
|View full text |Cite
|
Sign up to set email alerts
|

Abstract Process Data Warehousing

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
12
0

Year Published

2007
2007
2022
2022

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 11 publications
(12 citation statements)
references
References 1 publication
0
12
0
Order By: Relevance
“…The dirty event data lead to wild data provenance answers [28], mislead the aggregation profiling in process data warehousing [9], or obstruct finding interesting process patterns [17]. Indeed, the event data quality is essential in process mining, and known as the first challenge in the Process Mining Manifesto by the IEEE Task Force on Process Mining [30].…”
Section: Introductionmentioning
confidence: 99%
“…The dirty event data lead to wild data provenance answers [28], mislead the aggregation profiling in process data warehousing [9], or obstruct finding interesting process patterns [17]. Indeed, the event data quality is essential in process mining, and known as the first challenge in the Process Mining Manifesto by the IEEE Task Force on Process Mining [30].…”
Section: Introductionmentioning
confidence: 99%
“…In analogy to the general notion of services, Web services could be seen as a possible counterpart in the digital world (see [CD02] for details). However, Web services are defined only to provide standardized interfaces for enabling application-to-application communication [W3C07c].…”
Section: Definitionsmentioning
confidence: 99%
“…For example, in a pipe-and-filter style, components have input and output streams on which they operate, and streams are directed between components using pipes as connectors. As a more recent approach, Web services [CD02,W3C07c] …”
Section: Architectural Stylesmentioning
confidence: 99%
“…Moreover, two events Check Inventory(C) and Validate(D) in L1 correspond to one composite event Inventory Checking & Validation (4). For simplicity, we use ABCDEF to denote event names in L1, while 123456 are events in L2.…”
Section: Introductionmentioning
confidence: 99%
“…The company has started to integrate these heterogeneous event data into a unified business process data warehouse [3,4], where different types of analyses can be performed, e.g., querying similar complex procedures or discovering interesting event patterns in different subsidiaries (complex event processing, CEP [6]), comparing business processes in different subsidiaries to find common parts for process simplification and reuse [19], or obtaining a more abstract global picture of business processes (workflow views [2]) in the company. Without exploring the correspondence among heterogeneous events, applications such as query and analysis over the event data may not yield any meaningful results.…”
Section: Introductionmentioning
confidence: 99%