Measuring the Impact of Emergence in Business Applications

  • Dieter Rombach
  • Michael Kläs
  • Christian Webel
Conference paper
Part of the Progress in IS book series (PROIS)


Enterprise software systems must be designed for flexibility to allow adaptation of their inter-organizational relationships and their products to changing requirements or contexts while retaining existing functionality and user acceptance. To support this, we introduce the notion of Emergent Enterprise Software Systems. Emergent Enterprise Software Systems combine existing software paradigms with proactive and self-x behaviors into a stable and reliable software system. This is mainly achieved via new concepts, methods, tools and technologies. One of the main challenges is how to measure the impact of emergent software, i.e., to determine the benefit of these methodological and technological solutions with regard to business goals. This requires a goal-oriented measurement approach encompassing the definition of measurement goals, the definition of metrics, and the interpretation of measured data in the underlying context. In this paper, we outline a goal-oriented approach (GQM) for quantitatively measuring the impact of emergence enablers, and an approach (GQM+Strategies) for aligning such evaluations across organizational levels.


Technology Evaluation User Context Business Goal Strategy Graph Measurement Goal 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.



The work presented in this paper was partially funded by the Software-Cluster projects EMERGENT and SINNODIUM ( under grant no. 01IC10S01 and 01IC12S01F, the ARTEMIS Joint Undertaking under grant agreement no. 269335, and the German Federal Ministry of Education and Research (BMBF). The authors assume responsibility for the content.


  1. Basili VR (1984) Quantitative evaluation of software engineering methodology. In: Proceedings of 1st Pan Pacific computer conference, 1984bGoogle Scholar
  2. Basili VR, Caldiera G, Rombach HD (1994a) The experience factory. In: Marciniak JJ (ed) Encyclopedia software engineering, vol 1. Wiley, New York, pp 469–476Google Scholar
  3. Basili VR, Caldiera G, Rombach HD (1994b) Goal, question, metric paradigm. In: Marciniak JJ (ed) Encyclopedia of software engineering, vol 1. Wiley, New York, pp 528–532Google Scholar
  4. Basili V et al (2010) Linking software development and business strategy through measurement. Computer 2010(43):57–65CrossRefGoogle Scholar
  5. Budd CI, Budd CS (2010) A practical guide to earned value project management. Management Concepts, VAGoogle Scholar
  6. Frischbier S, Gesmann M, Mayer D, Roth A, Webel C (2012) Emergence as competitive advantage-engineering tomorrow’s enterprise software systems. In: Proceedings of the 14th international conference on enterprise information systems (ICEIS 2012), Wroclaw, Poland, ISBN 978-989-8565-12-9, July 2012 Google Scholar
  7. Heidrich J, Rombach D, Kläs M (2014) Model-based Quality Management of Software Development Projects. In: Ruhe G, Wohlin C (eds) Software project management in a changing world, Springer Google Scholar
  8. ISACA (2007) Control objectives for information and related technology (CoBIT®). Retrieved 04/ Dec /2007, from
  9. Kaplan R, Norton D (1992) The balanced scorecard—measures that drive performance. Harvard Business Review, Massachusetts Jan–Feb 1992, p 71Google Scholar
  10. Kläs M, Bauer T, Tiberi U (2012) Beyond herding cats: aligning quantitative technology evaluation in large-scale research projects. In: Proceedings of 14th international conference on product-focused software development and process improvement (PROFES 2012). Paphos, Cyprus, 2012Google Scholar
  11. Lindstrom D (1993) Five ways to destroy a development project. Softw, IEEE. 1993(10):55–58CrossRefMathSciNetGoogle Scholar

Copyright information

© Springer International Publishing Switzerland 2014

Authors and Affiliations

  • Dieter Rombach
    • 1
  • Michael Kläs
    • 1
  • Christian Webel
    • 1
  1. 1.Fraunhofer Institute for Experimental Software Engineering (IESE)KaiserslauternGermany

Personalised recommendations