<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>Rennes, France, June</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Environmental Sustainability IN Agile Processes: the AMELI (Acting, MEasuring, Learning and Improving) Model - Extended Abstract</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Jennifer Pérez</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Agustín Yagüe</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Daniel Guamán</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Universidad Politécnica de Madrid</institution>
          ,
          <addr-line>Alan Turing s/n, Madrid, 28031</addr-line>
          ,
          <country country="ES">Spain</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Universidad Técnica Particular de Loja</institution>
          ,
          <addr-line>San Cayetano Alto, Loja, 1101608</addr-line>
          ,
          <country country="EC">Ecuador</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2023</year>
      </pub-date>
      <volume>0</volume>
      <fpage>5</fpage>
      <lpage>09</lpage>
      <abstract>
        <p>Sustainable development requires to be performed just using the necessary needs of the present without compromising future generation's needs. Agile software development is a perfect framework to deploy sustainable models with concrete activities and measurements that could assist agile practitioners to be aware about the sustainability in their agile processes. This work presents the AMELI model, which prescribes a set of activities and measurements that practitioners can use to learn from them in order to achieve future sustainability improvements in their agile processes. In this work, we present the environmental dimension of AMELI.</p>
      </abstract>
      <kwd-group>
        <kwd>1 Agile</kwd>
        <kwd>Process</kwd>
        <kwd>Sustainability</kwd>
        <kwd>Green</kwd>
        <kwd>Environmental</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Agile software development should have a strong commitment in such a way agile processes and
their assets should be sustainable-aware [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. Sustainability addresses three main dimensions
[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ][
        <xref ref-type="bibr" rid="ref2">2</xref>
        ][
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]: Environmental, Social and Economic. In this work, we present the environmental dimension
of a sustainability model for agile practitioners sustainable-aware agile processes, called AMELI
(Acting, MEasuring, Learning and Improving). It prescribes activities to measure sustainability
indicators that allow one to learn how to improve sustainability in next sprints or projects [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. As a
result, AMELI provides agile practitioners to have a continuous feedback about the green degree of
their agile processes.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. The AMELI (Acting, Measuring,</title>
    </sec>
    <sec id="sec-3">
      <title>Environmental Dimension</title>
    </sec>
    <sec id="sec-4">
      <title>Learning and</title>
    </sec>
    <sec id="sec-5">
      <title>Improving)</title>
    </sec>
    <sec id="sec-6">
      <title>Model:</title>
      <p>
        The AMELI model has been conceived to support sustainability IN agile processes [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]
through some activities and measurements derived from a set of main questions about agile process.
The environmental dimension addresses the questions: Where, How, What and When.
      </p>
      <p>
        WHERE? This question is about where the agile process is conducted, i.e. the place where the agile
team works. The place where our agile process is adopted provide us valuable information about our
environmental sustainability degree [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. AMELI prescribes to calculate the indicator of Place
Environmental Waste by using the main indicators (energy, paper, plastic and water) that vary
throughout the working progress of the team (see equations, Figure 1). The Energy Place Waste
equation provide us the power consumption in kilowatts per hour (kWh) (see Eq.3), the Paper Waste is
measured using an integer number that corresponds with the number of A4 sheet papers (see Eq.4), the
Plastic Waste is measured in an integer number (see Eq.5), and the Water Waste is measured in liters
(see Eq.6). Finally, the Place Environmental Waste is the sum of all this values (see Eq.1), providing a
number that we should try be improved sprint to sprint. Since this sum has different measurement units,
it is important to normalize the values applying the Z normalization, which consists in scaling the values
of each component using its mean value and its standard deviation. In addition, it is important to
emphasize that the place not only generates waste, it can also generate environmental value. This value
can be achieved by actions of the company that are independent of the agile process but help to reduce
the waste footprint of its agile process adoption. This value is called Place Environmental Value (see
equations, Figure 1). The organization may perform actions to generate new energy by installing
photovoltaic panels in the building where the agile team is working, also the company can be involved
in actions of afforest o reforest by planting trees, as well as actions about harvesting or desalination of
water, or even, its recycling. The Energy Generation equation provide us the power generation in
kilowatts per hour (kWh) (see Eq.7). The Paper Generation is measured using an integer number that
corresponds with the number of A4 sheet papers (see Eq.8) (a tree is 45 feet high and 8 inches across
has between 10.000 sheets of paper). The Plastic Recycling is measured in an integer number that
represents the number of plastic items that have been recycled by the team (see Eq.9), and the Water
facilitation is measured is the liters of water that has been harvested, desalinated or recycled through
initiatives that the company has been participated (see Eq.10). Finally, the Place Environmental Value
is the sum of all this Z normalized values providing a number that should be improved sprint to sprint.
In addition, the difference among the Place Environmental Value (see Eq.6) and the Place
Environmental Waste (see Eq.1) will provide a value about our sustainable degree from the where
perspective (see Eq. 11), which is called Where Sustainability Degree:
Place Environmental Waste = Energy Place Waste + Paper Waste + Plastic Waste + Water Waste (Eq.1)
Energy Place Waste = Lights Power Consumption + Computers Power Consumption + Air Conditioning Systems Consumption + Heating Systems Power Consumption (Eq.3)
Paper Waste = TransformToNumberA4Sheets (Number of Post-its + Number of Booknotes * Number of paper sheets + Number of Other Kind of Papers) +Number of A4 paper sheets (Eq. 4)
Plastic Waste = Number of elements of plastic used not recyclable (bottles,glasses,bags,straws,cutlery,dishes,etc) (Eq.5)
Water Waste = Water Consumption of the bathrooms (Eq. 6)
Place Environmental Value = Energy Generation + Paper(Oxygen) Generation + Recycling + Water Facilitation (Eq.2)
Energy Generation = Power Generated from photovoltaic panels of the building (Eq.7)
Paper(Oxygen) Generation = (Number of trees restored from degraded forests,afforested and/or reforested) *10.000 + Number of recycled paper elements (Eq. 8)
Plastic Recycling = Number of recycled plastic elements (Eq. 9)
Water facilitation = Water harvesting,desalination and recycling (Eq.10)
      </p>
      <p>Where Sustainability Degree = Place Environmental Value - Place Environmental Waste (Eq.10)</p>
      <p>Finally, there are other non-quantitative actions that can be performed in the team’s working place
in order to improve our Where Sustainability Degree. They consist in promoting habits to the agile team
that in the medium term will be materialized in quantitative sustainability results, e.g. switching off
computers, screens or other electronic devices when they are not used.</p>
      <p>HOW? This question is about how the agile team conducts its agile process. The agile process is
articulated by using a set of development tools and hardware devices. The selection of this hardware
and software components is also critical in our environmental sustainability, since they will incur a
degree of power consumption depending on their properties and they will provide a degree. Therefore,
it is important to select the most suitable sustainability components without losing the required
properties to successfully develop the agile process. The How question must be analyzed from two
different moments: the selection and the use, which are described as follows.</p>
      <p>Selection. Before starting the agile process, the selection of the hardware and software setting has
to be determined to adopt the agile process. In AMELI, we promote the selection of this setting by
taking into account the energy consumption reduction. To that end, the selection process should be
proceeded as follows:</p>
      <p>Code 1. Hardware Software Selection</p>
      <p>
        There is a lot of advances in the measurement of power consumption and the design of sustainable
hardware. Therefore, the power consumption of hardware devices is detailed as a norm in their
specification, and the selection of the most suitable hardware for supporting the agile process is easy.
However, a lot of work is still pending in software and we do not have this power consumption
information. There are initiatives and tools that support software measurement [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
      </p>
      <p>Use. Once, the tools have been selected from the established selection criteria. AMELI defines the
Environmental How Sustainability Degree, i.e. the power consumption of the agile process (see
Eq.11).</p>
      <p />
      <p>
        1
= (  ℎ   
∗    
(
1. In addition, it is important to promote the developing techniques described in Figure 2.a, i.e.
refactoring on the fly and well-known green patterns that boost the sustainable software execution [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ],
[
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], and evidencing the energy saving of the improvement by measuring the product
execution after these refactoring. The What Sustainability Degree can be measured with two different
units: the power consumption of the product (see Eq.12) and the level of the What Sustainability Degree,
i.e. the performed sustainability actions related with the product are marked for calculating the value
(see Figure 2.a).
      </p>
      <p>ℎ  ℎ  
=   
+ 

 
a) What Sustainability Degree
b) AMELI adoption in the Agile Process</p>
    </sec>
    <sec id="sec-7">
      <title>3. Conclusions</title>
      <p>This work presents the AMELI (Acting, MEasuring, Learning and Improving) model as a
mechanism to address sustainability IN agile processes by smoothly integrate it into the agile activities.
In this work we address the environmental dimension. As future work, we plan to define the activities
of the economic and social dimensions, as well as to evaluate the model in a real setting to analyze the
feedback of practitioners in order to extend/reduce the model to facilitate its adoption.</p>
    </sec>
    <sec id="sec-8">
      <title>4. Acknowledgements</title>
      <p>This work is partially funded by the Spanish Ministry of Economy and Competitiveness (MINECO)
through the project SIoTCom: Sustainability-Aware IoT Systems Driven by Social Communities
(PID2020-118969RB-I00).
5. References</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Amsel</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ibrahim</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Malik</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tomlinson</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Toward sustainable software engineering: Nier track</article-title>
          .
          <source>In: 33rd International Conference on Software Engineering</source>
          , pp.
          <fpage>976</fpage>
          -
          <lpage>979</lpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Calero</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Piattini</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <source>Puzzling out Software Sustainability. Sustainable Computing Journal</source>
          .
          <volume>16</volume>
          (
          <year>December 2017</year>
          ):
          <fpage>117</fpage>
          -
          <lpage>124</lpage>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Dick</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Drangmeister</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kern</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Naumann</surname>
          </string-name>
          , S.:
          <article-title>Green software engineering with agile methods</article-title>
          .
          <source>In: 2nd Int.Workshop on Green and Sustainable Software</source>
          , San Francisco, CA, USA,
          <year>2013</year>
          , pp.
          <fpage>78</fpage>
          -
          <lpage>85</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Eckstein</surname>
          </string-name>
          , J.,
          <string-name>
            <surname>de O. Melo</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          (
          <year>2021</year>
          ):
          <article-title>Sustainability: Delivering Agility's Promise</article-title>
          .
          <source>Software Sustainability</source>
          . Springer, Cham.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>Green</given-names>
            <surname>Software</surname>
          </string-name>
          <article-title>Foundation: awesome-green-software</article-title>
          , https://github.com/Green-SoftwareFoundation/awesome-green-software,
          <source>last accessed</source>
          <year>2023</year>
          /02/17.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Guamán</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pérez</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Garbajosa</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rodríguez</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          (
          <year>2020</year>
          ).
          <article-title>A Systematic-Oriented Process for Tool Selection: The Case of Green and Technical Debt Tools in Architecture Reconstruction</article-title>
          .
          <source>In: Product-Focused Software Process Improvement. LNCS</source>
          , vol
          <volume>12562</volume>
          . Springer.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Guamán</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pérez</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          &amp;
          <string-name>
            <surname>Valdiviezo-Diaz</surname>
            ,
            <given-names>P. Estimating</given-names>
          </string-name>
          <article-title>the energy consumption of model-viewcontroller applications</article-title>
          .
          <source>J Supercomputing</source>
          (
          <year>2023</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Lago</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gu</surname>
            ,
            <given-names>Q.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Bozzelli</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          (
          <year>2014</year>
          ).
          <article-title>A systematic literature review of green software metrics</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Li</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          (
          <year>2012</year>
          , April):
          <article-title>Dynamic analysis of object-oriented software complexity</article-title>
          .
          <source>Int. Conf. on Consumer Electronics, Communications and Networks</source>
          , pp.
          <fpage>1791</fpage>
          -
          <lpage>1794</lpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Murugesan</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          (
          <year>2008</year>
          ).
          <article-title>Harnessing green IT: Principles and practices</article-title>
          .
          <source>IT professional</source>
          ,
          <volume>10</volume>
          (
          <issue>1</issue>
          ),
          <fpage>24</fpage>
          -
          <lpage>33</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Naumann</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dick</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kern</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Johann</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>The GREENSOFT Model: A reference model for green and sustainable software and its engineering</article-title>
          .
          <source>Sustainable Computing: Informatics and Systems</source>
          , vol.
          <volume>1</volume>
          , no.
          <issue>4</issue>
          , pp.
          <fpage>294</fpage>
          -
          <lpage>304</lpage>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Pérez-Castillo</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Piattini</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          (
          <year>2014</year>
          ).
          <article-title>Analyzing the harmful effect of god class refactoring on power consumption</article-title>
          .
          <source>IEEE software</source>
          ,
          <volume>31</volume>
          (
          <issue>3</issue>
          ),
          <fpage>48</fpage>
          -
          <lpage>54</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>Rashid</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Khan</surname>
            ,
            <given-names>S. U.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Khan</surname>
            ,
            <given-names>H. U.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Ilyas</surname>
            <given-names>M.</given-names>
          </string-name>
          :
          <string-name>
            <surname>Green-Agile Maturity Model</surname>
          </string-name>
          :
          <article-title>An Evaluation Framework for Global Software Development Vendors</article-title>
          .
          <source>In: IEEE Access</source>
          , vol.
          <volume>9</volume>
          , pp.
          <fpage>71868</fpage>
          -
          <lpage>71886</lpage>
          ,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>Rocheteau</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          (
          <year>2015</year>
          )
          <article-title>: Energy Wasting Rate as a Metrics for Green Computing</article-title>
          and
          <string-name>
            <given-names>Static</given-names>
            <surname>Analysis</surname>
          </string-name>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <surname>Shamshiri. H.</surname>
          </string-name>
          (
          <year>2021</year>
          ):
          <article-title>Supporting sustainability design through agile software development. In Evaluation and Assessment in Software Engineering</article-title>
          . ACM, New York, USA,
          <fpage>300</fpage>
          -
          <lpage>304</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <surname>Venters</surname>
            ,
            <given-names>C. C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Capilla</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Betz</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Penzenstadler</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Crick</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Crouch</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , ... &amp;
          <string-name>
            <surname>Carrillo</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          (
          <year>2018</year>
          ).
          <article-title>Software sustainability: Research and practice from a software architecture viewpoint</article-title>
          .
          <source>Journal of Systems and Software</source>
          ,
          <volume>138</volume>
          ,
          <fpage>174</fpage>
          -
          <lpage>188</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <surname>Ciccullo</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pero</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Caridi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gosling</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Purvis</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          (
          <year>2018</year>
          ).
          <article-title>Integrating the environmental and social sustainability pillars into the lean and agile supply chain management paradigms: A literature review and future research directions</article-title>
          .
          <source>Journal of cleaner production</source>
          ,
          <volume>172</volume>
          ,
          <fpage>2336</fpage>
          -
          <lpage>2350</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <surname>Zakrzewska</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Piwowar‐Sulej</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jarosz</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sagan</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Sołtysik</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          (
          <year>2022</year>
          ).
          <article-title>The linkage between Agile project management and sustainable development: A theoretical and empirical view</article-title>
          .
          <source>Sustainable Development</source>
          ,
          <volume>30</volume>
          (
          <issue>5</issue>
          ),
          <fpage>855</fpage>
          -
          <lpage>869</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <surname>Georgiou</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rizou</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Spinellis</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          (
          <year>2019</year>
          ).
          <article-title>Software development lifecycle for energy efficiency: techniques and tools</article-title>
          .
          <source>ACM Computing Surveys (CSUR)</source>
          ,
          <volume>52</volume>
          (
          <issue>4</issue>
          ),
          <fpage>1</fpage>
          -
          <lpage>33</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>