International Journal of Information Technology and Computer Science (IJITCS)
IJITCS Vol. 5, No. 12, 8 Nov. 2013
Cover page and Table of Contents: PDF (size: 378KB)
Goal Structured Requirement Engineering and Traceability Model for Data Warehouses
Full Text (PDF, 378KB), PP.78-85
Views: 0 Downloads: 0
Author(s)
Vinay Kumar
1
Reema Thareja
2,*
Index Terms
Business Model, Data Centric, Data Driven, Data Warehouse, Requirements Engineering, Traceability
Abstract
Data warehouses are decision support systems that are specifically designed for the business managers and executives for reporting and business analysis. Data warehouse is a database that stores enterprise-wide data that can be used to deduce useful information. Business organizations can achieve a great level of competitive advantage by analyzing its historical data and learning from it. However data warehouse concept is still maturing as a technology. In order to effectively design and implement a data warehouse for an organization, its goal needs to be understood and requirement must be analyzed in the perspective of the identified goal. In this paper we present a goal structured model for requirements engineering that also enables its users to manage traceability between the goals, decisions, business strategy and the corresponding business model.
Cite This Paper
Vinay Kumar, Reema Thareja, "Goal Structured Requirement Engineering and Traceability Model for Data Warehouses", International Journal of Information Technology and Computer Science(IJITCS), vol.5, no.12, pp.78-85, 2013. DOI:10.5815/ijitcs.2013.12.10
Reference
[1]A. I. Anton, (1996). Goal based requirements analysis. Proceedings of the 2nd International Conference on Requirements Engineering ICRE’96, pp. 136-144.
[2]Anjana Gosain, Navin Prakash. Requirements Driven Data Warehouse Development. Proceedings CAiSE Conference, Klagenfurt/Velden, Austria, 16-20 June, 2003.
[3]B. Dano, H. Briand, F. Barbier. A use case driven requirements engineering process. Third IEEE International Symposium On Requirements Engineering RE'97, Antapolis, Maryland, IEEE Computer Society Press, 1997.
[4]Ballard C.,Herreman D., Schau D. , Bell R. , Kim E., Valencic A. Data Modeling Techniques for Data Warehousing, redbooks.ibm.com
[5]Davies, A., Overmyer, S. Identifying and Measuring Quality in a Software Requirements Specification. First International Software Metrics Symposium, 1993.
[6]Foder, J., Higgins, C., McDermied, J. & Storrs, G. SAM. A Tool to Support the Construction, Review and Evaluation of Safety Arguments in F. Redmill & T. Anderson [eds] Directions in Safety, Critical Systems. Springer Verlag, 1993
[7]Gotel, O.C.Z & Finklestein, A.C.W. An Analysis of the Requirements Traceability Problem. Imperial College of Science and Technology, 1993.
[8]Inmon W.H., Building the Data Warehouse, John Wiley, New York.
[9]J. Bubenko, C. Rolland, P. Loucopoulos, V De Antonellis. Facilitating ‘fuzzy to formal’ requirements modelling. IEEE 1st Conference on Requirements Engineering, ICRE’94 pp. 154-158, 1994.
[10]Jarke M., Jeusfeld A., Quix C., Vassiliadis P. Architecture and Quality in Data Warehouses, Proceedings 10th CAiSE Conference, Pernici B., Thanos C. (eds.), Springer, 93-113.
[11]Robert Winter, Bernhard Strauch (2003). Demand-driven Information Requirements Analysis in Data Warehousing. Proceedings of the Hawai International Conference on Systems Sciences, IEEE- 2003.
[12]Traci J. Hess, John D. Well. Understanding How Metadata and Explanations Can Better Support Data Warehousing and Related Decision Support Systems: An Exploratory Case Study. Proceedings of the 35th Hawaii International Conference on System Sciences – 2002.