A Standard for Representing Multidimensional Properties: The Common Warehouse Metamodel (CWM)

Medina, Enrique; Trujillo, Juan

doi:10.1007/3-540-45710-0_19

Cited by 24 publications

(9 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Its definition is similar to that of transformations in the Common Warehouse Metamodel (CWM) Standard [16]. The following sections describe attributes, expressed in the type system XML DTDs, default values and correlating reserved parameters.…”

Section: Transformationmentioning

confidence: 99%

OCLPrime - Environment and Language for Model Query, Views and Transformations

Süß¹,

Leicher²,

Busse³

2004

Electronic Notes in Theoretical Computer Science

View full text Add to dashboard Cite

UML, MOF, and MDA currently do not provide a standardized means to describe manipulation of model-elements in algorithms or rules. In order to define specific UML-based methods in a product-independent and portable way, this capability is essential. This paper discusses design and implementation of the hybrid language framework Prime and its derivative language OCLPrime in the light of the OMG Query / Views / Transformations RFP. Prime allows and coordinates the reuse of different languages for validation, selection, and projection in the Transformation of models. Its design follows the Composite, Visitor, and Interpreter patterns and coordinates the sub-languages in transactions. OCLPrime is a reference language implementation in Prime employing OCL expressions to select parts of a source model and SQL DML to project these into a target model. Pre-and Post-validations are performed by a UML Profile Validator.

show abstract

Section: Transformationmentioning

confidence: 99%

OCLPrime - Environment and Language for Model Query, Views and Transformations

Süß¹,

Leicher²,

Busse³

2004

Electronic Notes in Theoretical Computer Science

View full text Add to dashboard Cite

show abstract

“…However, CWM metamodels are (i) too generic to represent all peculiarities of MD modeling in a conceptual model (i.e. PIM) and (ii) too complex to be handled by both final users and designers [15], so we deeply believe that it is more reliable to design a PIM by using an enriched conceptual modeling approach easy to be handled (e.g. [9,10]), and then transform this PIM into a CWM-compliant PSM in order to assure the interchange of DW metadata between different platforms and tools.…”

Section: Related Workmentioning

confidence: 99%

Applying MDA to the development of data warehouses

Mazón

Trujillo

Serrano

et al. 2005

Proceedings of the 8th ACM International Workshop on Data Warehousing and OLAP

Self Cite

View full text Add to dashboard Cite

Different modeling approaches have been proposed to overcome every design pitfall of the development of the different parts of a data warehouse (DW) system. However, they are all partial solutions which deal with isolated aspects of the DW and do not provide designers with an integrated and standard method for designing the whole DW (ETL processes, data sources, DW repository and so on). On the other hand, the Model Driven Architecture (MDA) is a standard framework for software development that addresses the complete life cycle of designing, deploying, integrating, and managing applications by using models in software development. In this paper, we describe how to align the whole DW development process to MDA. Then, we define MD 2 A (MultiDimensional Model Driven Architecture), an approach for applying the MDA framework to one of the stages of the DW development: multidimensional (MD) modeling. First, we describe how to build the different MDA artifacts (i.e. models) by using extensions of the Unified Modeling Language (UML). Secondly, transformations between models are clearly and formally established by using the Query/View/Transformation (QVT) approach. Finally, an example is provided to better show how to apply MDA and its transformations to the MD modeling.

show abstract

“…After the transformation, the object-oriented schema has to be partitioned in order to reduce the number of joins and disk accesses. UML [9] extensions for data warehouse conceptual modeling have also been proposed [10,11]. OMG suggested the Common Warehouse Metamodel (CWM) [12,13], an approach to metadata interchange, which is capable of expressing major multidimensional properties [10].…”

Section: Introductionmentioning

confidence: 99%