Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
Recovering Traceability Links between Code and Documentation
IEEE Transactions on Software Engineering
Lineage Tracing in a Data Warehousing System
ICDE '00 Proceedings of the 16th International Conference on Data Engineering
YAM2: a multidimensional conceptual model extending UML
Information Systems
IBM Systems Journal - Model-driven software development
A UML profile for multidimensional modeling in data warehouses
Data & Knowledge Engineering - Special issue: ER 2003
Reconciling requirement-driven data warehouses with data sources via multidimensional normal forms
Data & Knowledge Engineering
GRAnD: A goal-oriented approach to requirement analysis in data warehouses
Decision Support Systems
An MDA approach for the development of data warehouses
Decision Support Systems
Software traceability with topic modeling
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
A survey of traceability in requirements engineering and model-driven development
Software and Systems Modeling (SoSyM)
Graphical Query Mechanism for Historical Data Warehouse within MDD
SCCC '10 Proceedings of the 2010 XXIX International Conference of the Chilean Computer Science Society
MoDELS'05 Proceedings of the 2005 international conference on Satellite Events at the MoDELS
| Hi-index | 0.00 |
Developing a data warehouse is an ongoing task where new requirements are constantly being added. A widely accepted approach for developing data warehouses is the hybrid approach, where requirements and data sources must be accommodated to a reconciliated data warehouse model. During this process, relationships between conceptual elements specified by user requirements and those supplied by the data sources are lost, since no traceability mechanisms are included. As a result, the designer wastes additional time and effort to update the data warehouse whenever user requirements or data sources change. In this paper, we propose an approach to preserve traceability at conceptual level for data warehouses. Our approach includes a set of traces and their formalization, in order to relate the multidimensional elements specified by user requirements with the concepts extracted from data sources. Therefore, we can easily identify how changes should be incorporated into the data warehouse, and derive it according to the new configuration. In order to minimize the effort required, we define a set of general Query/View/Transformation rules to automate the derivation of traces along with data warehouse elements. Finally, we describe a CASE tool that supports our approach and provide a detailed case study to show the applicability of the proposal.