Energy efficiency on the product roadmap: an empirical study across releases of a software product

E.A. Jagroep, Guiseppe Procaccianti, J.M.E.M. van der Werf, S. Brinkkemper, Leen Blom, Rob van Vliet

    Research output: Contribution to journalArticleAcademicpeer-review


    In the quest for energy efficient Information and Communication Technology, research has mostly focused on the role of hardware.

    However, the impact of software on energy consumption has been acknowledged as significant by researchers in software engineering. In spite of that, due to cost and time constraints, many software producing organizations are unable to effectively measure software energy consumption preventing them to include energy efficiency in the product roadmap.

    In this paper, we apply a software energy profiling method to reliably compare the energy consumed by a commercial software product across 2 consecutive releases. We demonstrate how the method can be applied and provide an in-depth analysis of energy consumption of software components. Additionally, we investigate the added value of these measurement for multiple stakeholders in a software producing organization, by means of semistructured interviews.

    Our results show how the introduction of an encryption module caused a noticeable increase in the energy consumption of the product. Such results were deemed valuable by the stakeholders and provided insights on how specific software changes might affect energy consumption. In addition, our interviews show that such a quantification of software energy consumption helps to create awareness and eventually consider energy efficiency aspects when planning software releases.
    Original languageEnglish
    Article numbere1852
    JournalJournal of software: Evolution and Process
    Issue number2
    Publication statusPublished - Feb 2017


    • energy efficiency
    • profiling
    • product roadmap
    • software product


    Dive into the research topics of 'Energy efficiency on the product roadmap: an empirical study across releases of a software product'. Together they form a unique fingerprint.

    Cite this