Advertisement

Extending a Metamodel for Formalization of Data Warehouse Requirements

  • Natalija Kozmina
  • Laila Niedrite
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 194)

Abstract

In performance measurement systems that are built on top of a data warehouse, the information requirements in natural language are different performance indicators that should be stored and analyzed. We use the requirement formalization metamodel to create a formal requirement repository out of information requirements in natural language. In the course of this research we tested the compatibility of the existing requirement formalization metamodel applying it to a set of over 150 requirements for the currently operating data warehouse project. As a result, we extended the formal specification of information requirements with some additional classes like themes, grouping, and requirement priorities, and relationships discovered in this case study. We discussed benefits of requirement prioritization and advantages of transferring requirement priority values to schema elements with and aim of detecting schema elements to be incorporated into dashboards.

Keywords

data warehouse performance indicators requirement formalization prioritization 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Inmon, W.H.: Building the Data Warehouse, 3rd edn. Wiley Computer Publishing (2002)Google Scholar
  2. 2.
    Winter, R., Strauch, B.: A Method for Demand-driven Information Requirements Analysis in Data Warehousing Projects. In: Proceedings of 36th Annual Hawaii International Conference on System Sciences (HICSS 2003), pp. 1359–1365. IEEE, Waikoloa (2003)Google Scholar
  3. 3.
    Niedritis, A., Niedrite, L., Kozmina, N.: Performance Measurement Framework with Formal Indicator Definitions. In: Grabis, J., Kirikova, M. (eds.) BIR 2011. LNBIP, vol. 90, pp. 44–58. Springer, Heidelberg (2011)CrossRefGoogle Scholar
  4. 4.
    Kozmina, N., Niedrite, L., Golubs, M.: Deriving the Conceptual Model of a Data Warehouse from Information Requirements. In: Proceedings of the 15th International Conference on Enterprise Information Systems (ICEIS 2013), Angers, France, vol. 1, pp. 136–144 (2013)Google Scholar
  5. 5.
    Parmenter, D.: Key Performance Indicators: Developing, Implementing, and Using Winning KPIs, 2nd edn. Jon Wiley & Sons, Inc. (2010)Google Scholar
  6. 6.
    Frank, U., Heise, D., Kattenstroth, H., Schauer, H.: Designing and Utilizing Business Indicator Systems within Enterprise Models - Outline of a Method. In: Loos, P., Nüttgens, M., Turowski, K., Werth, D. (eds.) Modellierung betrieblicher Informationssysteme (MobIS 2008) - Modellierung zwischen SOA und Compliance Management, vol. 141, pp. 89–105. LNI, Saarbrücken (2008)Google Scholar
  7. 7.
    Popova, V., Treur, J.: A Specification Language for Organizational Performance Indicators. Applied Intelligence Journal 27(3), 291–301 (2007)CrossRefGoogle Scholar
  8. 8.
    Popova, V., Sharpanskykh, A.: Modeling Organizational Performance Indicators. Information Systems 35(4), 505–527 (2010)CrossRefGoogle Scholar
  9. 9.
    Pourshahid, A., Amyot, D., Chen, P., Weiss, M., Forster, A.J.: Business Process Monitoring and Alignment: An Approach Based on the User Requirements Notation and Business Intelligence Tools. In: WER, pp. 80–91 (2007)Google Scholar
  10. 10.
    ITU-T – International Telecommunications Union: Recommendation Z.150 (02/03), User Requirements Notation (URN) – Language Requirements and Framework, Geneva, Switzerland (2003) Google Scholar
  11. 11.
    Berander, P., Andrews, A.: Requirements Prioritization (Chapter 4). In: Aurum, A., Wohlin, C. (eds.) Engineering and Managing Software Requirements, pp. 69–94. Springer, Berlin (2005)CrossRefGoogle Scholar
  12. 12.
    Lausen, S.: Software Requirements – Styles and Techniques. Pearson Education, Essex (2002)Google Scholar
  13. 13.
    Karlsson, J.,, Wohlin, C., Regnell, B.: An Evaluation of Methods for Prioritizing Software Requirements. Information and Software Technology 39(14-15), 939–947 (1998)CrossRefGoogle Scholar
  14. 14.
    Brackett, J.W.: Software Requirements Technical Report. Carnegie Mellon University, Software Engineering Institute (1990)Google Scholar
  15. 15.
    Expert Business Analyst: Requirements Prioritization, http://expertbusinessanalyst.com/requirements-prioritization/
  16. 16.
    Karlsson, L., Berander, P., Regnell, B., Wohlin, C.: Requirements Prioritisation: An Experiment on Exhaustive Pair-Wise Comparisons vs. Planning Game Partitioning. In: Proceedings of the 8th International Conference on Empirical Assessment in Software Engineering (EASE 2004), pp. 145–154. IEE, Stevenage (2004)CrossRefGoogle Scholar
  17. 17.
    Leffingwell, D., Widrig, D.: Managing Software Requirements – A Unified Approach. Addison-Wesley, Upper Saddle River (2000)Google Scholar
  18. 18.
    Saaty, T.L.: The Analytic Hierarchy Process. McGraw-Hill, New York (1980)Google Scholar
  19. 19.
    Regnell, B., Höst, M., Natt och Dag, J., Beremark, P., Hjelm, T.: An Industrial Case Study on Distributed Prioritisation in Market-Driven Requirements Engineering for Packaged Software. Requirements Engineering 6(1), 51–62 (2001)CrossRefGoogle Scholar
  20. 20.
    Alshehri, S., Benedicenti, L.: Using the Analytical Hierarchy Process as a Ranking Tool for User Story Prioritization Techniques. In: Proceedings of the 8th International Conference on Software Engineering Advances, pp. 329–335. IARIA, Venice (2013)Google Scholar
  21. 21.
    A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), version 2. International Institute of Business Analysis, Toronto, Ontario, Canada (2009)Google Scholar

Copyright information

© Springer International Publishing Switzerland 2014

Authors and Affiliations

  • Natalija Kozmina
    • 1
  • Laila Niedrite
    • 1
  1. 1.Faculty of ComputingUniversity of LatviaRigaLatvia

Personalised recommendations