2010
DOI: 10.1007/978-3-642-16373-9_2
|View full text |Cite
|
Sign up to set email alerts
|

Leveraging Business Process Models for ETL Design

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
40
0
1

Year Published

2013
2013
2017
2017

Publication Types

Select...
4
4

Relationship

0
8

Authors

Journals

citations
Cited by 33 publications
(41 citation statements)
references
References 13 publications
0
40
0
1
Order By: Relevance
“…This work enables the design developed in BPMN to be compatible across multiple tools and easy to extend to fit the requirements of a particular application. The BPMN approach was then adapted by [20][21][22] to construct a conceptual model of an ETL workflow.…”
Section: Bpmn-based Conceptual Modelmentioning
confidence: 99%
See 2 more Smart Citations
“…This work enables the design developed in BPMN to be compatible across multiple tools and easy to extend to fit the requirements of a particular application. The BPMN approach was then adapted by [20][21][22] to construct a conceptual model of an ETL workflow.…”
Section: Bpmn-based Conceptual Modelmentioning
confidence: 99%
“…The work in [22] proposes a layered method that starts with business requirements and systematically converts a conceptual model into its semantically equivalent physical implementation. The entire method is based on the QoXsuit of quality metrics [23] to construct an optimal ETL workflow.…”
Section: Bpmn-based Conceptual Modelmentioning
confidence: 99%
See 1 more Smart Citation
“…The complexity and variability of data transformations has introduced an additional challenge to the efforts for providing a commonly accepted modeling notation for these data flows. Several works have proposed different ETL modeling approaches, either ad-hoc [99], or based on well-known modeling languages, e.g., UML in [92] or BPMN in [3,101]. However, these modeling approaches do not provide any automatable means for the design of an ETL process (i.e., Low automation).…”
Section: Automationmentioning
confidence: 99%
“…The rationale behind this metamodel is the characterization of the ETL process as a combination of two perspectives: (i) A control process, responsible of synchronizing the transformation flows; (ii) A data process, feeding the data warehouse from the data sources. In this way, designers are able to specify conceptual models of ETL processes together with the business process of the enterprise (Wilkinson, 2010). Furthermore, the model-driven approach has been customized from a generic data warehouse approach (Mazón & Trujillo, 2008) into a concrete implementation for the ETL component.…”
Section: Introductionmentioning
confidence: 99%