Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
Recovering Traceability Links between Code and Documentation
IEEE Transactions on Software Engineering
IBM Systems Journal - Model-driven software development
A UML profile for multidimensional modeling in data warehouses
Data & Knowledge Engineering - Special issue: ER 2003
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
Macro-level Traceability Via Media Transformations
REFSQ '08 Proceedings of the 14th international conference on Requirements Engineering: Foundation for Software Quality
The Data Warehouse Lifecycle Toolkit
The Data Warehouse Lifecycle Toolkit
ER'07 Proceedings of the 26th international conference on Conceptual modeling
A survey of traceability in requirements engineering and model-driven development
Software and Systems Modeling (SoSyM)
CAiSE'11 Proceedings of the 23rd international conference on Advanced information systems engineering
Proceedings of the fifteenth international workshop on Data warehousing and OLAP
Conceptualizing and specifying key performance indicators in business strategy models
CASCON '12 Proceedings of the 2012 Conference of the Center for Advanced Studies on Collaborative Research
Hi-index | 0.00 |
The complexity of the Data Warehouse (DW) development process requires to follow a methodological approach in order to be successful. A widely accepted approach for this development is the hybrid one, in which requirements and data sources must be accommodated to a new DW model. The main problem is that the relationships between conceptual elements coming from requirements and those coming from data sources are lost in the process, since no traceability is explicitly specified, consuming additional time and resources. Previously, we have defined a trace metamodel in order to trace user requirements to DW conceptual models. In this paper, we complement our approach by including traceability along the successive refinements performed at the conceptual level. Therefore, we preserve the existing relationships between elements, eliminating additional costs derived from performing the matching process multiple times. We provide an example of how Query/View/Transformation rules can automate trace generation, and we also provide a set of guidelines for connecting conceptual elements coming from requirements with those coming from the data sources.