<!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 />
    <article-meta>
      <title-group>
        <article-title>Integrating Sustainability Awareness Analysis and BPMN-Modelling</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>John Krogstie</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Norwegian University of Science and Technology (NTNU)</institution>
          ,
          <addr-line>Trondheim</addr-line>
          ,
          <country country="NO">Norway</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2026</year>
      </pub-date>
      <abstract>
        <p>All enterprise information system changes need to take the sustainability efects of a reengineered business area or organisation into account. The way to analyse sustainability efects is not clearly related to standard enterprise modelling approaches, and this position paper tries to motivate further discussion on possible ways of linking these types of methods by suggesting an integrated meta-model of SusAF and BPMN. The proposal is explored through the use of an example and discussed in relation to the quality of modelling language integration. The example illustrates one way this might be done, but also that there might be other ways of integrating sustainability awareness techniques and enterprise modelling that are worth pursuing. We are currently experimenting with additional links between sustainability analysis and enterprise modelling to provide further results at PoEM 2025 and beyond.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Sustainability analysis</kwd>
        <kwd>BPMN</kwd>
        <kwd>SusAF</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        1. Introduction
PoEM 2025 focuses on Enterprise Modelling for Sustainable Reindustrialisation. Sustainability has been
recognised as central to information systems and software engineering for at least the last decade [
        <xref ref-type="bibr" rid="ref3">3,
10</xref>
        ]. In [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], it is concluded that sustainability should become a key concern in the next generation of
engineered systems. [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] focuses specifically on the critical role of modelling in this regard. ICT plays a
vital role in assuring both social, environmental and economic sustainability. The need for the ICT field
to address sustainability has been acknowledged for some time in areas such as Information systems
[19], HCI, and software engineering [
        <xref ref-type="bibr" rid="ref4">4, 13</xref>
        ].
      </p>
      <p>
        There are several approaches to evaluating and creating awareness of sustainability. One of these,
the Sustainability Assessment Framework (SAF) [13], structures the efects of software systems into
four dimensions. Three of them have been incorporated into several sustainability models since the
1980s, following the Brundtland [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] framework, which encompasses the economic, environmental, and
social dimensions. To this, SAF adds the technical dimension.
      </p>
      <p>
        The Sustainable Awareness Framework (SusAF) [
        <xref ref-type="bibr" rid="ref4 ref5">4, 5</xref>
        ] also has a separate individual dimension. In
both frameworks, efects are classified as direct, enabling, or long-term (systemic) [11]. [15] extends
this to four levels of efects, diferentiating between direct and indirect efects. In a review study of
techniques to incorporate sustainability into requirements engineering [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], SusAF is the most frequently
discussed approach; however, these publications are primarily from the team that developed the original
framework. Beyond what is described in this literature, the application of the framework is limited [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ],
although some other works are reported [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
      </p>
      <p>Whereas both SAF and SusAF are attempted to be used as inputs to software requirements and design,
the link between sustainability analysis and enterprise business processes is less explored. In this paper,
we report on the first attempts to bridge this gap, an approach that we are currently experimenting
with in a course in information systems at the university.</p>
      <p>Thus, our research question is
•</p>
      <p>RQ1: How can sustainability effects be related to business process models?</p>
      <p>In the next section, we will provide further background on SusAF. In Section 3, we describe
the main result, and in Section 4, we give an example of the integrated use of SusAF and BPMN
[17]. These results are discussed in Section 5, before we conclude in Section 6.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Background and Related Work</title>
      <p>
        As mentioned above, five dimensions have traditionally been used in the development of a
model for sustainability evaluation of ICT projects [
        <xref ref-type="bibr" rid="ref4">4, 14</xref>
        ], utilising SusAF, where the model is
referred to as the ‘sustainability analysis diagram’ (SusAD). Specifically, SusAF is composed of
the SusAD, the chart for visualising potential sustainability effects of a (software) system, and
five question sets for guiding exploration of the five sustainability dimensions [14]. Effects are
on different levels. Direct effects, such as energy consumption, are what Hilty et al. [11] denote
first-order effects. Second-order enabling effects include the consequences of processes being
changed. Third-order structural effects are seen as long- and medium-term change in behaviour.
      </p>
      <p>
        The five dimensions can be described in the following way [
        <xref ref-type="bibr" rid="ref4">4, 14</xref>
        ]:





      </p>
      <p>The environmental dimension covers the use and stewardship of natural resources.
It includes material and resources, waste and pollution, biodiversity, and energy
usage.</p>
      <p>The technical dimension covers the ability to maintain and evolve artificial systems
(such as software) over time, including aspects of maintainability, adaptability,
security, and scalability.</p>
      <p>The economic dimension covers financial value, customer relationship management,
supply chain, logistics, governance and innovation.</p>
      <p>The individual dimension covers health, lifelong learning, privacy, usability,
universal availability, safety, and agency.</p>
      <p>The social dimension covers relationships between individuals and groups. This
includes a sense of community, trust, inclusiveness, diversity, equity, participation
and communication [9].</p>
      <p>In addition, we have added a sixth dimension that covers compliance with rules and
regulations, both in the short term and to ensure future-proofing for upcoming regulations.
This is in view of the large number of regulations emerging, particularly in the EU, with the AI
Act being just one of many, although specifically important due to the significant role AI plays
in digitalization and sustainable development [18]. The renewed framework is illustrated in
Figure 1.</p>
      <p>Aspects within these dimensions are often interlinked, so that an effect in one area can have
a positive or negative effect on another effect in the same or different dimension, possibly on
another level, as will be illustrated in the example in Section 4.</p>
      <p>In enterprise modelling, we aim to support the modelling of effective enterprises, including
good business processes. A good business process produces its products or services by
optimising one or more of a set of quality features. The value of a process to be optimised is not
only the economic return, but also a broader set of possible objectives, as listed in Table 1,
further explained below.
 Time: Time from the start to the end of the process. Based on the expectations, it should
be on time (or faster), i.e., be timely.
 Quality: The quality of the resulting product is as expected (or better).
 Cost: Direct monetary costs as expected or lower.
 Flexibility: Often relates to how one can treat discrepancies with the normal path of the
process. The required flexibility varies significantly for different types of processes.
 Resource usage: This can relate to several areas. When it comes to employees, they
would not like to work in a process where they experience that they are exploited.
When it comes to natural resources, Green BPM as part of Green information systems
[19] has emerged as an area where one examines the overall carbon footprint of the
process or any other type of pollution resulting from it.
 Unwanted side-effects: Some examples are a process that jeopardises the security of the
customers (think of an internet bank with too poor security) or privacy, or the
reputation of the company (using child labourers to produce their products, for
instance, or for a public service to be biased against certain groups of citizens). The
process should not have unwanted bias.
 According to regulations: In most areas, both in the public and private sectors, you have
to act according to the regulations in the area (usually country) that you operate. You
can also consider the situation where you are certified according to a specific process
or at a certain maturity level, which may be necessary to be allowed to deliver a
particular product or service. This can also be important to be regarded as a sufficiently
good provider in a supply chain or digital business ecosystem.
 Reproducible: The level of service can be redone, and does not deteriorate, e.g. because
of being supported by unmaintainable IT-solutions, or too dependent on individuals in
the company.
 Improvable: It is possible to gauge the level of service, and not only keep this up, but
potentially improve it by introducing, e.g., new technology.</p>
      <p>The dimension of process-value is related to the dimensions of sustainability in the following
ways:
 Time and cost -&gt; Economic impact
 Resource – usage -&gt; Environmental impact
 Improvable -&gt; Technical impact
 According to regulations -&gt; Compliance impact
 Unwanted side-effects -&gt; Social, individual or technical impact
 Flexibility -&gt; Individual impact
 Reproduceable -&gt; Technical impact</p>
      <p>Quality can thus have an impact on any of the sustainability dimensions.</p>
    </sec>
    <sec id="sec-3">
      <title>3. Approach to Integration</title>
      <p>A way of bridging SUSAF with requirements and process modelling in an information system
context is suggested below, where concepts from SusAF are linked to (process) modelling and
quality of business processes. The figure is described in more detail below:</p>
      <p>A system can have specific effects. The system can be an existing system (as-is analysis), or a
new system planned for development (to-be analysis) and is often either a software system or
an information system (including also a set of business processes and an (re)organisation in
addition to the technical software system). Our focus here is (enterprise) information systems.
The effects have an impact (low/medium/high) if they occur, and a likelihood of occurring
(low/medium/high). The effect itself can be regarded as positive or negative.</p>
      <p>To achieve a positive effect, or avoid a negative effect, one has parts of a process (activities
that might utilise a software system). The business process can be depicted, for example, in
BPMN. Another possible approach (not shown here) is to link effects to goal models (that an
effect will achieve a goal more or less likely). In this paper, we focus on the integration with
process models. Process metrics are as listed above.</p>
      <p>Figure 2: Metamodel of extended SusAF and process value in BPMN</p>
      <p>Effects can be part of an effect-chain. In these cases, one effect might have a positive or
negative influence on achieving another effect. Effects are categorised according to the levels
(immediate (direct), enabling, structural) and dimensions (economic, technical, individual,
social, environmental, and compliancy) as previously described. Sub-dimensions as found in
[14] are not depicted in the diagram.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Example Application of the Approach</title>
      <p>The following example illustrates the possible connection between sustainability concerns and
a new procurement process in a public sector agency. Figure 3 is a high-level, simplified BPMN
model of the first part of such a process.</p>
      <p>The process begins when someone in a department within the agency identifies a demand
(Event: Demand identified). If the product is locally available, one uses the good from stock. If
not, the demand is further described, and a purchase requisition is made. A worker in the central
procurement department checks this. If the supplier is known, an order is made. If not, the new
supplier is registered in the system first. Finally, an approver triggers the actual order to the
supplier.</p>
      <p>
        The organisation aspires to have a more sustainable procurement process. Several possible
sustainability effects at various levels are illustrated in Figure 4 (described further in Table 2),
partly inspired by the example found in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>Note that this relates to the whole procurement process, as it is supported in the technical
procurement systems (bottom right).</p>
      <p>Below is a listing of the effects found in Figure 4, before we list the relationships (effect
chains). The +/- indicates a positive or negative effect, the first digit represents the level of
effect, and the second digit represents the dimension.</p>
      <p>Some connections among effects2
 +D.T.1 - + &gt; +E.T.1 or – E.T.1: The use of a standard procurement solution will
potentially save money for evolution and maintenance, given that it supports the
process wanted by the organisation well. On the other hand, if numerous local changes
are required, the evolution and maintenance activities may become more extensive.
(thus, the effect can be both positive and negative).
 +D.T.1 - + &gt; +E.EC.1: A standard solution can be quick to implement, and thus one can
enforce a new process quickly. A bespoke solution may be slower to implement, but it
will be better equipped to accommodate specific needs. On the other hand, it may
necessitate different types of maintenance needs that would have been addressed in a
standard solution.
2 -+&gt; is a positive connection (i.e. that one effect make the other effect more likely),
- -&gt; is a negative connection (i.e. that one effect is expected to dampen another effect)
Compliancy</p>
      <p>Direct effect
+ D.EN.1 Show
carbon footprint in
system
- D.I.1 Reduce
freedom of
choice
+ D.SO.1 Make
procurement
transparent to
local providers
+ D.T.1 Use
standard solution
+ D.EC.1 Select a
cheap IT solution
+ D.C.1 Ensure
following
procurement laws
+ D.C.2 Enforce
frame agreement</p>
      <p>Enabling effect
+ E.EN.1 Enable
choice based on
carbon footprint
-E.I.1 Decrease
choice possibility
+/- E.T.1 system
maintenance
+ E.EC.1 Quick
implementation of
the system
-E.EC.2 Law cases
+ E.SO.1 facilitate + S.SO.1 improved
use of local providers community
relationship
Structural effect
+S.EN.1 Market
reward for
sustainable
production
-S.I.1 Diminished
trust and
workarounds
- S.T.1 Lock-in
+ S.EC.1 local
economy
improvement






+D.T.1 - + &gt; +D.C.1: A standard solution is probably made in a way that enforces
following the existing procurement laws.
+D.C.1 - - &gt; - E.EC.2: Following the procurement laws will minimise the risk of being
sued by providers from erroneous procurement (and thus reduce the risk of losing
lawsuits).
+D.4.1 - - &gt; +D.EN.1: If the standard procurement system does not include information
about carbon footprint, it will be hard to support this. Similar to other ways of
supporting sustainability (e.g., the enforcement of local suppliers).
+ D.C.2 -- &gt; + E.SO.1: The enforcement of frame agreements might make it more
challenging to use some local suppliers.
+ D.C.2 - + &gt; - E.I.1: The enforcement of using frame agreements can make the
possibility of individual choice less, thus enforcing this potentially negative effect.
+D.1.1/+2.1.1 - + &gt; S.EN.1: If information on carbon footprint is available, and many use
this opportunity, in the long term, it can influence the market to provide more
sustainable options and thus have a long-term positive effect on environmental
sustainability, especially if it influences the standard procurement solutions.</p>
      <p>As we understand, there are a number of connections and trade-offs to be made, which can
be discussed based on this analysis. Additionally, the influence of this on the process can be
illustrated in the process model, which is here supplemented with comments, as there is no
suitable notation in BPMN for sustainability effects. Whereas some aspects are on an overall
system level (choice of standard or bespoke system), other elements are closely related to where
in the process different aspects are enforced.</p>
      <p>In Figure 5, we illustrate some of the links that can also influence the overall time used for
procurement, from the time a need is identified until a purchase order is sent.


</p>
      <p>Is the standard solution to be used for all steps, or is this only used for the formal part,
whereas one might add specific wishes in the initial purchase requisition?
Is the frame agreement enforced in all steps, thus almost disallowing selecting new
suppliers, or is it first implemented by the procurement department or the final
approver (with the possible need of restarting part of the process, e.g. needing to
update the process model)?
Is it possible to see the carbon footprint by the initial procurement request and make a
choice based on this , or is this first taken into account by the procurement
department?</p>
    </sec>
    <sec id="sec-5">
      <title>5. Discussion</title>
      <p>
        Different dimensions of sustainability are increasingly becoming critical in how we are evolving
organised activities. In enterprise modelling, we have several approaches to provide an
overview of current and future situations, supporting the analysis and development of new
information systems. Many workshop-oriented approaches, such as SAF and SusAF, exist to
identify the sustainability effects of systems, and links to software requirements [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and design
[13] have been developed; however, they are currently underutilized in practice [
        <xref ref-type="bibr" rid="ref1 ref5">1, 5</xref>
        ].
      </p>
      <p>Returning to our research question RQ1: “How can sustainability effects be related to
business process models? “, we have in this paper provided an example of one possible way this
can be done. We admit, though, that this is so far weak anecdotal evidence which provide
important risk to validity.</p>
      <p>The example presented, although simple, illustrates several novelties:

</p>
      <p>In addition to the five traditional dimensions of sustainability effects, we have
introduced a compliance dimension, which proved helpful to illustrate the laws,
regulations and standards that influence the overall system, which also will affect the
process model.</p>
      <p>A meta-model of the extended version of SusAF is provided, also illustrating one way
that sustainability effects can be linked to parts of the process models and requirements
and, through that, to the achievement of process value.</p>
      <p>Although the example illustrates that it is possible to link sustainability effects to business
process models, the link is not immediately apparent, and much of the reasoning behind the
resulting business process is not easily illustrated in the existing BPMN language, apart from as
comments/annotations. That said, this applies to all process value deliberation; the 'why' aspect
of the process model is poorly represented in standard BPMN, indicating a need to link the
sustainability diagrams to more comprehensive enterprise modelling notations, such as
ArchiMate or 4EM [16] which also include goal modelling.</p>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusion and Further Work</title>
      <p>In this position paper, we have begun to explore the possible integration of a sustainability
awareness framework and process modelling using BPMN, aiming to take sustainability more
consciously into account in process improvements. This can be supported more concretely in
BPMN models as part of enterprise process modelling.</p>
      <p>The example provided in this paper, is to our knowledge, the first attempt to establish such
a link on the modelling language level. A suggestion for the main parts of a combined
metamodel is presented, although only a limited part of a BMPN-metamodel is provided. The overall
approach is currently tested by student groups in an advanced Bachelor course with around 150
students. Based on the learnings we will update the overall approach. The next step is to design
a better tool that supports this by integrating it with a BPMN meta-model found in other tools.
We plan to do this using the Mimris-environment3, and also devise a better notation, taking into
account aspects of quality of modelling languages [12]. Using this we plan to perform additional
experiments, both as for the usefulness and usability of such language, being studied as being
used in industrial cases. The possibility of parallel modelling and meta-modelling supported in
Mimris will make possible further extensions of the meta-model of the approach through use.
We will also investigate the integration of sustainability effects with goal-oriented modelling,
such as found e.g., in 4EM [16]. A more detailed evaluation is planned for Autumn 2026 linking
to the course in which we are currently piloting the approach.</p>
    </sec>
    <sec id="sec-7">
      <title>Declaration on Generative AI</title>
      <p>During the preparation of this work, the author did not use AI tools, but only built-in services
in Microsoft Word in order to do grammar and spelling check.
3 https://mimris.vercel.app/modelling
[9] de Souza, C. M., Soares Cruzes, D., Jaccheri, L., Krogstie, J.: Social sustainability approaches
for software development: A systematic literature review, in International Conference on
Product-Focused Software Process Improvement, pp. 478–494, Springer, (2023)
[10] Freitag, C. et al. The real climate and transformative impact of ICT: A critique of estimates,
trends, and regulations. Patterns 2, 9 (2021)
[11] Hilty, L.M., Aebischer, B.: ICT for Sustainability: An Emerging Research Field. In: Hilty,
L.M., Aebischer, B. (eds.) ICT Innovations for Sustainability. Advances in Intelligent
Systems and Computing 310, Springer International Publishing (2015)
[12] Krogstie, J.: Model based development and evolution of Information Systems. A quality</p>
      <p>Approach. Springer (2012)
[13] Lago, P., Verdecchia, R., Condori-Fernandez, N., Rahmadian, E., Sturm, J. van Nijnanten,
T., Bosma, R., Debuysscher, C., Ricardo, P.: Designing for Sustainability: Lessons Learned
from Four Industrial Projects (2020)
[14] Penzenstadler, B. et al.: The SusA Workshop - improving sustainability awareness to
inform future business process and systems design
https://zenodo.org/records/3676514#.YzFa9C8eOk7 last visited 18.2.2024
[15] Rugeviciute, A., Courboulay, V., Hilty, L.M.: The research landscape of ICT for
sustainability: harnessing digital technology for sustainable development: ICT4S (2023)
[16] Sandkuhl, K., Stirna, J., Persson, A., Wißotzki, M.: Enterprise Modeling Springer (2014)
[17] Silver, B.: BPMN Method and Style, Cody-Cassidy Press (2011)
[18] Vinuesa, R.; Azizpour, H.; Leite, I.; Balaam, M.; Dignum, V.; Domisch, S.; Felländer, A.;
Langhans, S.D.; Tegmark, M.; Fuso Nerini, F.: The Role of Artificial Intelligence in
Achieving the Sustainable Development Goals. Nature Communications 11, 233.
https://doi.org/10.1038/s41467-019-14108-y (2020)
[19] vom Brocke, J., Watson, R. T., Dwyer, C., Elliot, S., Melville, N.: Green Information Systems:
Directives for the IS Discipline. Communications of the Association for Information
Systems, 33, pp. https://doi.org/10.17705/1CAIS.03330 (2013)</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>P.</given-names>
            <surname>Bambazek</surname>
          </string-name>
          , I. Groher,
          <string-name>
            <given-names>N.</given-names>
            <surname>Seyff</surname>
          </string-name>
          ,
          <article-title>Sustainability in Agile Software Development: A Survey Study among Practitioners</article-title>
          .
          <source>In 2022 International Conference on ICT for Sustainability (ICT4S)</source>
          (pp.
          <fpage>13</fpage>
          -
          <lpage>23</lpage>
          ). IEEE (
          <year>2022</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Bambazek</surname>
            ,
            <given-names>I. Groher</given-names>
          </string-name>
          , and
          <string-name>
            <given-names>N.</given-names>
            <surname>Seyff</surname>
          </string-name>
          , Bambazek,
          <string-name>
            <given-names>P.</given-names>
            ,
            <surname>Groher</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            ,
            <surname>Seyff</surname>
          </string-name>
          , N.:
          <article-title>Requirements engineering for sustainable software systems: a systematic mapping study</article-title>
          ,
          <source>Requirements Engineering</source>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>25</lpage>
          , (
          <year>2023</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Becker</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chitchyan</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Duboc</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Easterbrook</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mahaux</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Penzenstadler</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rodríguez-Navas</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Salinesi</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Seyff</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Venters</surname>
            ,
            <given-names>C.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Calero</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Akinli Koçak</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Betz</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>The Karlskrona manifesto for sustainability design</article-title>
          .
          <source>arXiv preprint arXiv:1410</source>
          .
          <fpage>6968</fpage>
          . (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Becker</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Betz</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chitchyan</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Duboc</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Easterbrook</surname>
            ,
            <given-names>S.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Penzenstadler</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Seyff</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Venters</surname>
            ,
            <given-names>C.C.</given-names>
          </string-name>
          :
          <article-title>Requirements: The Key to Sustainability</article-title>
          .
          <source>IEEE Software Special Issue on the Future of Software Engineering</source>
          , Volume
          <volume>33</volume>
          ,
          <string-name>
            <surname>Issue</surname>
            <given-names>1</given-names>
          </string-name>
          , pages
          <fpage>56</fpage>
          -
          <lpage>65</lpage>
          ,
          <year>January 2016</year>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <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>Duboc</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chitchyan</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kocak</surname>
            ,
            <given-names>S. A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brooks</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          , ... &amp;
          <string-name>
            <surname>Venters</surname>
            ,
            <given-names>C. C.</given-names>
          </string-name>
          (
          <year>2024</year>
          ).
          <article-title>Lessons Learned from Developing a Sustainability Awareness Framework for Software Engineering using Design Science</article-title>
          .
          <source>ACM Transactions on Software Engineering and Methodology</source>
          ,
          <volume>33</volume>
          (
          <issue>5</issue>
          ),
          <fpage>1</fpage>
          -
          <lpage>39</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Bork</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>David</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>España</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Guizzardi</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Proper</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Reinhartz-Berger</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          <article-title>The Role of Modeling in the Analysis and Design of Sustainable Systems: A Panel Report</article-title>
          .
          <source>Communications of the Association for Information Systems</source>
          ,
          <volume>54</volume>
          (
          <issue>34</issue>
          ),
          <fpage>911</fpage>
          -
          <lpage>936</lpage>
          . (
          <year>2024</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Brundtland</surname>
            ,
            <given-names>G.H.</given-names>
          </string-name>
          :
          <source>Report of the World Commission on Environment and Development: Our Common Future, United Nations World Commission on Environment and Development</source>
          (
          <year>1987</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Chasanidou</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krogstie</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Boletsis</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gasparini</surname>
            ,
            <given-names>A. A.</given-names>
          </string-name>
          :
          <article-title>Sustainability design in industry and academia</article-title>
          .
          <source>In the 2024 International Conference on ICT for Sustainability (ICT4S)</source>
          . Stockholm, Sweden, June 24-28. (
          <year>2024</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>