Early Information Requirements Engineering for Target Driven Data Warehouse Development

  • Naveen Prakash
  • Hanu Bhardwaj
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 134)


We propose two stages for data warehouse requirements engineering (i) an ‘early information’ part where the information relevant to decision making is discovered, and (ii) a ‘late’ part where this information is structured as facts and dimensions. Our focus is on the former. Early information data warehouse requirements engineering starts with targets defined as pairs of the form <A, I> where A is an aspect of an organization and I is a set of business indicators. An aspect is a work area, work unit, service or quality to be preserved in an organization. Business indicators are measures/metrics for specifying the desired performance level of aspects. Targets are organized in a target hierarchy. This hierarchy is a complete specification of what is to be achieved by a top level target. We associate targets with choice sets so that alternative ways of target achievement can be represented. These alternatives form their own hierarchy. Finally, information relevant to selection of each alternative is discovered through Ends, Means, Key Success Factor, and Outcome Feedback analysis techniques. These techniques determine early information that is to be subsequently to be processed in the ‘late information’ requirements engineering stage. Our early information requirements engineering phase is illustrated through a case study.


aspects business indicators target choice set early information 


  1. [Bar11]
    Barone, D., Jiang, L., Amyot, D., Mylopoulos, J.: Composite Indicators for Business Intelligence. In: Jeusfeld, M., Delcambre, L., Ling, T.-W. (eds.) ER 2011. LNCS, vol. 6998, pp. 448–458. Springer, Heidelberg (2011) CrossRefGoogle Scholar
  2. [Boe99]
    Boehnlein, M., Ulbrich vom Ende, A.: Deriving initial Data Warehouse Structures from the Conceptual Data Models of the Underlying Operational Information Systems. In: Proc. of Workshop on Data Warehousing and OLAP, DOPLAP, Kansas City, MO, USA (1999)Google Scholar
  3. [Bon01]
    Bonifati, A., Cattaneo, F., Ceri, S., Fuggetta, A., Paraboschi, S.: Designing data marts for data warehouses. ACMTOSEM 10(4), 452–483 (2001)Google Scholar
  4. [Fel07]
    Felix, R.: Efficient Decision Making with Interactions Between Targets. In: Proceedings of the 2007 IEEE Symposium on Computational Intelligence in Multicriteria Decision Making, MCDM 2007, pp. 221–226 (2007)Google Scholar
  5. [Gol99]
    Golfarelli, M., Rizzi, S.: Designing the Data Warehouse: Key Steps and Crucial Issues. Journal of Computer Science and Information Management 2(3) (1999)Google Scholar
  6. [Hor12]
    Horkoff, J., Yu, E.: Comparison and Evaluation of Goal-oriented Satisfaction Analysis Techniques. Requirement Engineering Journal (2012)Google Scholar
  7. [Inm96]
    Inmon, W.H.: Building the Data Warehouse. John Wiley, New YorkGoogle Scholar
  8. [Lam09]
    van Lamsweerde, A.: Reasoning About Alternative Requirements Options. In: Borgida, A.T., Chaudhri, V.K., Giorgini, P., Yu, E.S. (eds.) Conceptual Modeling: Foundations and Applications. LNCS, vol. 5600, pp. 380–397. Springer, Heidelberg (2009) CrossRefGoogle Scholar
  9. [Niu08]
    Niu, L., Zhang, G.: A Model of Cognition-Driven Decision Process for Business Intelligence. In: IEEE/WIC/ACM International Conference on Web Intelligence and Intelligent Agent Technology, pp. 876–879 (2008)Google Scholar
  10. [Pra04]
    Prakash, N., Singh, Y., Gosain, A.: Informational Scenarios for Data Warehouse Requirements Elicitation. In: Atzeni, P., Chu, W., Lu, H., Zhou, S., Ling, T.-W. (eds.) ER 2004. LNCS, vol. 3288, pp. 205–216. Springer, Heidelberg (2004)CrossRefGoogle Scholar
  11. [Pra08]
    Prakash, N., Gosain, A.: An Approach to Engineering the Requirements of Data Warehouses. Requirements Engineering Journal 13(1), 49–72 (2008)CrossRefGoogle Scholar
  12. [Pra09]
    Prakash, N., Prakash, D., Sharma, Y.K.: Towards Better Fitting Data Warehouse Systems. In: Persson, A., Stirna, J. (eds.) PoEM 2009. LNBIP, vol. 39, pp. 130–144. Springer, Heidelberg (2009)CrossRefGoogle Scholar
  13. [Rol03]
    Rolland, C.: Reasoning with Goals to Engineer Requirements, Invited talk. In: Int. Conf. on Enterprise Information Systems, ICEIS 2003 (2003)Google Scholar
  14. [Sha09]
    Al-Shawa, M., Basir, O.: Constrained Rationality: Formal Targets-Reasoning Approach to Strategic Decision & Conflict Analysis. In: Proceedings of the 2009 IEEE International Conference on Systems, Man, and Cybernetics, pp. 1439–1445 (2009)Google Scholar
  15. [Wan04]
    Wang, Y., Liu, D., Ruhe, G.: Formal Description of the Cognitive Process of Decision Making. In: Proceedings of the Third IEEE International Conference on Cognitive Informatics, ICCI 2004, pp. 124–130 (2004)Google Scholar
  16. [Yu97]
    Yu, E.: Towards modeling and reasoning support for early requirements engineering. In: Proceedings of the IEEE International Symposium on Requirement Engineering, pp. 226–235. IEEE Computer Society (1997)Google Scholar

Copyright information

© IFIP International Federation for Information Processing 2012

Authors and Affiliations

  • Naveen Prakash
    • 1
  • Hanu Bhardwaj
    • 1
  1. 1.MRCEFaridabadIndia

Personalised recommendations