<!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>Exploratory Case Study on Sustainability Awareness with a Startup for Business Models</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Birgit Penzenstadler</string-name>
          <email>birgit.penzenstadler@csulb.edu</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Anoushka Mara</string-name>
          <email>anoushkamara@gmail.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Stephanie Nam</string-name>
          <email>stepha789@gmail.com</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Brian Budzinski</string-name>
          <email>brian@partneur.com</email>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>CSU Long Beach</institution>
          ,
          <addr-line>Long Beach</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>CSU Long Beach, USA</institution>
          ,
          <addr-line>Lappeenranta Univ. of Techn.</addr-line>
          ,
          <country country="FI">Finland</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>CSU Long Beach, USA, Los Alamitos High School</institution>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Partneur</institution>
          ,
          <addr-line>Long Beach</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>-Start-up businesses are often not primarily con- curriculum and standards of business planning [18] nor recerned with the overall sustainability impact of their business quirements engineering [23]. Despite showing up in research idea. However, designing sustainability into the start-up business over the past ten years, there is little strategic support by isduecacefsrsombutthreeqstuairrtesmaadydiimtiopnraolveknthoewirledlogneg-atenrdmtiimmep.acItns athnids RE for integrating sustainability into the subsequent design paper, we perform a case study of the start-up Partneur, who process [3]. As a result, there is no strategic support tailored are developing an online platform for developing business ideas towards explicitly integrating sustainability into the subseaccording to the Business Model Canvas. We show the usage of quent design process of a start-up business plan. In order our artifact-based analysis approach and discuss observations to incorporate sustainability into the long-term vision of a aPnadrtnleeussro,nasndleamringehdt., iTnhteuranp, pirnofoarcmh pthreoivridfeudturneewuseirnssiognhtshotwo business, we apply an artifact-based approach that visualizes to incorporate sustainability into their business idea as well. the potential goals and their impacts on sustainability in the Index Terms-sustainability awareness; requirements engi- different dimensions. neering; evaluation research; artifact orientation; Our contribution to easing the challenge of limited resources and sustainability knowledge when developing a business idea I. INTRODUCTION is a set of diagrams (e.g., stakeholders, goals, use cases) and guidelines for sustainability awareness (e.g., five dimensions Society's innovation and progress has come with many of sustainability) as initially proposed in [23]. costs whether in environmental, economic, societal, technical, We contribute a case study that serves as an example to and many other dimensions. In general, sustainability is a start-ups demonstrating how they can visualize the goals of concern of rising importance for companies [5]. There is their business and align them with sustainability. While we an increasing number of startups, yet these new businesses do this for a business that uses the Business Model Canvas have limited resources and lack extensive knowledge on (BMC) as their main guideline to develop their prototype, we sustainability. As a result, they resort to focusing on the are not attempting to constructively critique any specific type development of a minimum viable product [27]. The rise of business model but instead offer an artifact-based approach of startups has radically changed not only the tech industry rooted in requirements engineering to explore any type of but also commerce as a whole. The startup scene is fed business model with regards to their sustainability impacts. by young developers and entrepreneurs, many of which are The diagrams and models serve as a mapping of concept to just about to graduate from college. To give them a better clarify and help in the development of their business idea in the foundation in skills that are relevant to getting a business short run and long run. The implementation of sustainability off the ground, CSULB founded the College of Business principles (as proposed, e.g., in the Karlskrona Manifesto [4]) Administration “Business Incubator” (https://www.csulb.edu/ from the start of a business idea diminishes long run risks cba-graduate-programs/cob-incubator). The Business Incuba- and allow for greater success [15]. This paper completes a tor consists of a group of engaged young entrepreneurs that case study with a local startup, Partneur (www.partneur.com) leads a series of talks on topics relevant to startups. The and provides models of their stakeholders, goals, system Business Incubator is advised and supported by a business vision, use cases, and sustainability awareness diagram. They administration professor, Prof. Wade Martin. Over the course give an overview of the most important requirements for the of a semester, interested students can participate in the talks system development of Partneur. With the analysis, Partneur and receive mentorship. is equipped with the resources and knowledge needed to gear Designing sustainability into a start-up business idea from their business toward a resilient and sustainable business. the beginning may improve the long-term impacts and success The impact of this case study of an artifact-based approach of the business. The problem is that such efforts require to systems engineering for sustainability serves as an example additional knowledge and time in terms of research, and then for other companies in early development stages, or even integrating the acquired knowledge into business plan drafts, companies that are further down the road and want to improve while sustainability is not yet integrated into the traditional the long-term plan for their business. The case study of this</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        paper can be followed and replicated to provide businesses
with the guidance they may otherwise not yet have available.
Thus, the study contributes to a knowledge base [
        <xref ref-type="bibr" rid="ref29">29</xref>
        ], [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] and
facilitates designing sustainability into new business idea and
systems development.
      </p>
    </sec>
    <sec id="sec-2">
      <title>II. RELATED WORK AND BACKGROUND We introduce our foundation work on Requirements Engineering for Sustainability and sustainability awareness diagram that helped assess the Partneur prototype.</title>
      <sec id="sec-2-1">
        <title>A. Requirements Engineering for Sustainability (RE4S)</title>
        <p>
          Partneur is developing a software system to support their
business process, and requirements are the key leverage point
for practitioners who want to develop sustainable
softwareintensive systems [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. We use the term RE4S as defined in
previous work [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ]: Requirements Engineering for Sustainability
(RE4S) denotes “the concept of using requirements
engineering and sustainable development techniques to improve the
environmental, social, and economic sustainability of software
systems and their direct and indirect effects on the surrounding
business and operational context” [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ]. In order to develop
such systems, we need awareness (by education) and guidance
(e.g., by training), and creativity (to find better solutions).
The RE4S approach uses an artifact model, guiding questions,
checklists, and reference models to elaborate the requirements
for a system under development. The entire approach is
described in detail in [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ] and example specifications have
been provided in [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ], [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. Furthermore, example artifacts are
provided in the results section of this article. A customized
version of the AMDiRE artifact model [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ], the RE4S artifact
model as adapted for this case study is depicted in a simplified
manner in Fig. 1. It contains a stakeholder model, a goal
model, a system vision, a usage model, and a sustainability
awareness diagram (explained in detail in the next section).
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>B. Sustainability Awareness Diagram</title>
        <p>
          The Sustainability Awareness Diagram (SuSAD) [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ] is a
diagram to provide an overview of the impacts of system
on the five dimensions of sustainability [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ] in the three
orders of effect [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. The dimensions are environmental,
economic, social, individual, and technical [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. The
environmental dimension refers to the usage and protection of natural
resources. The economic dimension refers to the ability to
preserve value and capital. The social dimension refers to
the ability of societies to preserve the solidarity and services.
The individual dimension refers to the ability of the people
to live their lives and express themselves in freedom. The
technical dimension relates to the longevity of socio-technical
systems. Impact on sustainability can be observed via impact
on one or more of its dimensions. As a result, it is advocated
that sustainability requires simultaneous consideration of these
interrelated dimensions [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]. Nevertheless, interdependencies
exist between these dimensions including tradeoffs that may
have to be negotiated for a system under analysis [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. In
addition, we can also consider the five dimensions in relation
to three orders of impacts or effects of software systems [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ],
[
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]. Immediate effects are attributed directly to the lifecycle
of the system through the resources used for its production,
usage, and disposal. Enabling effects are caused by the usage
of the system in its application environment, and potentially
by many users over a period of time (months to a couple
of years). The structural effects show when accumulating the
aggregated effects of usage by many users over an extended
period of time (years or decades) [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ].
        </p>
        <p>
          The work by Seyff et al. [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ] presented a tabular version
of the sustainability analysis using as elicitation method a
modified WinWin Negotiation Model and the EasyWinWin
method to support the negotiation of requirements and their
impact on sustainability. This includes identifying affected
sustainability dimensions, discussing how immediate, enabling
and structural effects are manifested, and how these effects
should be taken into account in the development of a system.
The results support the authors’ view that every requirement
affects sustainability and each such effect should be considered
if the full view of the system’s impact on sustainability is to
be observed [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ].
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>C. Case Study: Partneur</title>
        <p>This explorative study was conducted with the start-up
company Partneur. They were selected upon discussion with
various start-up companies based on the common interest
of learning more about how Partneur could strengthen their
business vision in terms of sustainability. Furthermore, the
Partneur founders are involved in the Business Incubator that
serves as multiplier and knowledge disseminator amongst
aspiring start-up founders on campus but also from the public
community in and around Long Beach.</p>
        <p>
          Their main business idea is to provide an online platform
for collaboration on the development of business plans. The
underlying model they use for these business plans is the
Business Model Canvas (BMC) [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ].
        </p>
      </sec>
      <sec id="sec-2-4">
        <title>D. Business Model Canvas</title>
        <p>
          As explained in [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ], a business model can “best be
described through nine basic building blocks that show the logic
of how a company intends to make money”. The nine blocks
cover the four main areas of a business: customers, offer,
infrastructure, and financial viability. The business model is like
a blueprint for a strategy to be implemented through
organizational structures, processes, and systems. The original business
model canvas is a template with blocks for customer segments,
value propositions, channels, customer relationships, revenue
streams, key resources, key activities, key partnerships, and
cost structure. An organization serves one or several customer
segments. It seeks to solve customer problems and satisfy
customer needs with value propositions. Value propositions are
delivered to customers through communication, distribution,
and sales channels. Customer relationships are established and
maintained with each customer segment. Revenue streams
result from value propositions successfully offered to customers.
Key resources are the assets required to offer and deliver the
previously described elements by performing a number of key
activities. Some activities are outsourced and some resources
are acquired outside the enterprise to key partnerships. The
business model elements result in the cost structure [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ].
        </p>
        <p>Note that this paper does not endorse one type of business
plan over another but that our case study partner Partneur is
developing an online platform to enable people to
collaboratively work on a business model canvas, and that is the
business idea that we are analyzing using the artifact-based
requirements engineering for sustainability (RE4S) approach.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>III. RESEARCH DESIGN</title>
      <p>
        This exploratory case study [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] was carried out in the Fall
semester of 2018 at the California State University, Long
Beach. The research objective was to perform a structured
approach to requirements engineering and a sustainability
awareness diagram for a local startup company.
      </p>
      <p>The selection of the case study partner was based on
availability and potential for impact. Partneur is a local
startup company in its first steps that is founded by four young
entrepreneurs who graduated from CSULB and run the
Business Incubator on campus. Thus, a successful application of
the RE4S and SuSAD approach could inform many start-ups in
the making and support their business and system development
as the Business Incubator serves as a knowledge disseminator.</p>
      <p>The research objective was to apply the artifact-based
requirements engineering approach including the sustainability
awareness diagram to the case of a local start-up company in
their early development stages, and to evaluate the usability
of the approach for the (inexperienced) requirements engineers
and usefulness of the results for the founders.</p>
    </sec>
    <sec id="sec-4">
      <title>IV. CASE STUDY: RESULTS</title>
      <p>This section presents the results from the requirements
elicitation that was performed by analyzing an early prototype
of the Partneur online platform and in interview sessions with
two of the founders.</p>
      <sec id="sec-4-1">
        <title>A. Stakeholder model</title>
        <p>
          In the requirements engineering domain, a stakeholder is
commonly defined any individual, group or a business who
has a stake in the system, i.e, an entity who is affected by the
system and/or affects the system through some component [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ],
[
          <xref ref-type="bibr" rid="ref28">28</xref>
          ], [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. But this doesn’t mean that every stakeholder is
interested in the project’s success. For example, although
legislators influence the way a company or system works, they
are usually unaffected or little affected by the system’s success
or failure. Stakeholders can be identified through iteratively
analyzing the goals to deduce key role-players who influence
the system, inspecting the business and operational context of
the system under development, instantiating a generic
reference list, and so on. In general, stakeholders can be classified
based on their roles and function. A generic list of categorizing
stakeholders by their roles are: users, creators, developers,
institutions etc. Based on their functions, stakeholders can
be categorized into the following groups: Decision makers,
Information providers, Regulatory, Implementers, End Users
and Post Implementation support [
          <xref ref-type="bibr" rid="ref25">25</xref>
          ]. A stakeholder model
is used to define the various stakeholders of a system, and
visually represent them along with their connection to the
system. It can be represented through UML actor hierarchies,
informal hierarchical graphics or natural language [
          <xref ref-type="bibr" rid="ref25">25</xref>
          ].
        </p>
        <p>The stakeholder diagram is a UML representation of the
different classes of stakeholders of Partneur. Here, the
stakeholders are classified into groups based on their role in the system.
Firstly, we have the founders of Partneur who presently have
a majority stake in the system. They are the founders and key
innovators of this tool. They are responsible for the planning,
decision-making, execution and control of the system. They
are advised by a team of Experts, namely Business Analysts
and Domain Experts. Business Analysts advise the Owners on
the best ways to optimize the business, predict future trends for
the system and improve the decision-making process. Domain
Experts provide feedback and solutions about a specific topic
or area of interest in this industry.</p>
        <p>Next, we have a team of developers who are collectively
responsible for the creation, maintenance and security of the
Partneur website and online tool. They include Engineers, IT
Security, Troubleshooting team and Testers. We also have a
Marketing team to analyze the positioning of the product,
devise strategies to gain more users and effectively reach out
to the target market. Further, there is a Legal team and a team
of Online regulators to check the decorum of the users in using
the tool, safeguard the intellectual property of the system and
keep a check on disruptive teams or negative activity.</p>
        <p>The primary users of Partneur are individuals with little
or almost no background in business. The aim of the tool
is to guide the users through a step by step process in a
creating a business plan for their idea and assisting them until
they launch the product. The secondary users are students
in universities across the country. The tool would serve as
an educational tool in building a business plan for initiatives
or student clubs encouraging entrepreneurship. Mentors are
experienced individuals with several years of experience in the
field of Entrepreneurship. They voluntarily take the initiative
to provide guidance to the teams and advise them in their
key decisions. Educational institutions, Partners and Sponsors
provide visibility and support to Partneur. They assist in
marketing efforts to gain more users and help in growing
the platform with insights and/or monetary aid. Finally,
Competitors are other online platforms that provide support for
creating a business plan from scratch. A few of Partneur’s
key competitors are liveplan.com, businessplanpro.com, and
planbuildr.com. However, Partneur are the only ones who
focus especially on team building around a business plan in
the making.</p>
      </sec>
      <sec id="sec-4-2">
        <title>B. Goal model diagram</title>
        <p>
          Goals are targets for achievement, which determine the
driving force behind the system. They help in establishing
a framework for the system. They define the high-level
objectives of the system and guide decisions at various levels
within the enterprise [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ], [
          <xref ref-type="bibr" rid="ref32">32</xref>
          ]. Goals are subdivided into three
categories: Business goals, Usage goals and System goals.
Business Goals are the key goals of the business that lay the
foundation for other goals. They have a direct impact on the
entire system and provide motivation for the system. Usage
Goals determine how the primary, secondary and tertiary users
work with the system. They are related to the functional
context of the system. System Goals explain how the system
is supposed to work to achieve the above goals. They are
system-related goals that target system characteristics [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ].
        </p>
        <p>Each goal can be further decomposed into smaller sub
goals. These sub goals ensure that certain pre-requirements
are met before moving on to achieving the larger goal. This
helps in addressing issues and resolving conflicts during the
implementation of the system. Further, the goals are analyzed
to see if they have a sustainable factor, i.e., does the goal bring
out sustainability in any of the five dimensions (individual,
social, technical, economic and environmental).</p>
        <p>A goal model diagram is used to depict the decomposition of
goals into subgoals, and the respective interdepencies between
the goals. This forms the basis for early identification and
resolution of conflicts, and defining the rationale of a
requirement. In most cases, a Primary Goal is subdivided into several
Business goals which are further decomposed into Usage goals
followed by System goals. Further, every goal improves the
sustainability factor of the dimensions listed at the top of the
goal.</p>
        <p>The goal model diagram depicts the goal model for Partneur.
At the top, we have the primary goal of Partneur. This is the
mission statement of Partneur which is to “formulate, build and
execute business ideas”. This primary goal is decomposed into
several Business goals (which are highlighted in blue). The
business goals include: attracting possible investors to fund
the projects, impacting the Long Beach community with the
launch of these innovative projects, creating a reliable interface
for users to connect and build these projects, providing a
transparent, financial model to users so that they know exactly what
they are paying/signing up for, and finally aiding educational
institutions and users by providing them Partneur as a learning
tool.</p>
        <p>The Usage goals (highlighted in yellow) tell us about what
the users can achieve with the system. By attracting investors
(Business Goal), the users can network and make connections
with the investors and can create a pitch deck of their project
to show them. Users can create innovative, impactful projects
which will in turn benefit the Long Beach community at large.
Using the reliable interface of Partneur, users can connect with
a team, discuss and share skills and information securely, and
legally protect their project ideas. Transparency in the financial
model can be achieved by having few economic variables
for the membership pricing: i.e. the membership pricing may
depend only on a few key factors like number of projects etc.
Users can learn and apply real-life skills in their projects and
receive mentoring. This way, Partneur succeeds in providing
an online learning tool for individuals.</p>
        <p>The System goals (highlighted in green) are broad
systemrelated goals, which relate to the overall functioning of the
system. They include high availability the total system (includes
website, security, privacy and mentoring), excellent system
security to protect user’s information and privacy, and easy
navigation features which will enable the system to be a
userfriendly interface.</p>
        <p>Usually, the parent goals and subgoals work toward
improving a common sustainability dimension. For example,
the Business goal of impacting the Long Beach community
helps in expanding the Social dimension of sustainability
by improving the community and standard of living. It also
positively enhances the Environmental aspect of sustainability
by launching projects which are aimed at being eco-friendly
and bringing about a “green” change in the society. This
can be followed by the Usage goal of connecting a team of
entrepreneurs. It positively impacts the sustainability of the
social dimension by bringing people closer in a community
and creates an environment where people can work collectively
to achieve a common goal. Lastly, the Usage goal can be
achieved by having a user-friendly interface (which can be
achieved by having an easy navigation amongst other things)
and a high availability of the system. These goals enhance the
technical aspect of sustainability by ensuring that the system
functions according to the requirements set by the developers
and/or expectations set by the users.</p>
      </sec>
      <sec id="sec-4-3">
        <title>C. UML use case overview diagram</title>
        <p>
          Use cases are used to represent a business function, process,
or activity performed in the modeled business. A business actor
represents a role played by some person or system external to
the modeled business, and interacting with the business. A
business use case should produce a result of observable value
to a business actor [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ]. An adapted UML depiction of these
use-cases (Fig. 3) outlines all the possible use-case scenarios
of the primary, secondary and tertiary users of the system.
        </p>
        <p>Partneur has three types of end users: Individual users,
Investors and Mentors. Each of these users are business actors
to Partneur and play a particular role in the system. The
primary user is an individual user, who is seeking to utilize
the Partneur tool in bringing his business idea to life. He can
choose to initiate a project or simply join an existing team. He
takes the first step by creating an account with the website.
Next, he can choose to create a project of his own and choose
a Business model best suited to his idea. This is followed
by the Team Development process which includes connecting
with people to create a team. If an individual user doesn’t
choose to initiate a project, then he can request to join an
existing project. The Team Development phase is followed by
the Development phase. It includes Market Research, choosing
a Financial Template, creating a Business plan and choosing
the Services required to develop the project. A Mentor is
a secondary user of the system who provides his valuable
insights and assists the team in making key decisions in the
Development phase of one or more projects. Service providers
are tertiary users of the system. They are not key business
actors since they don’t create an account with the system and
are not personally involved with the project which the goal
of success. However, they do impact the system by providing
their services (such as Accounting, Website development etc.)
to various teams who contact them for their services. Finally,
Investors are important business actors of the system. They are
secondary users of the system who launch the various projects
after they are completed. First, they create an account with
Partneur. Next, investors choose certain criteria about the kind
of projects they would be interested in funding. And finally,
they select one or more project and help in launching them by
providing monetary funding.</p>
      </sec>
      <sec id="sec-4-4">
        <title>D. System Vision as Rich Picture</title>
        <p>
          A system vision diagram is a joint vision of the system
agreed by all stakeholders. One way we can create this big
picture is through graphically depicting the entire system in
a rich picture format. A rich picture is a holistic thinking
approach for a complex system with several stakeholders [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ].
It consists of text, symbols, icons and thought bubbles to
illustrate the main elements and relationships that need to
be considered in trying to intervene in order to create some
improvement. It includes a broad view of the stakeholders,
processes and elements of the system. The thought bubbles
are queries/thoughts/ideas of the specific stakeholder in this
situation. A rich picture helps in understanding the complexity
of an entire situation. It points out relationships and
connections that we may otherwise miss. A rich picture helps to
open discussion and come to a broad, shared understanding of
a situation. We have used icons from the sustainability library
that was created at the ICT4S 2018 conference [
          <xref ref-type="bibr" rid="ref31">31</xref>
          ].
        </p>
        <p>
          The system vision diagram (Fig. 4) depicts the system vision
of Partneur in a rich picture format [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ]. Firstly, let’s begin
with the owners of Partneur. They overview and manage all
the processes and key decisions of the system. They own the
Partneur website and are responsible for its overall functioning
and issues. The owners are usually concerned about issues
such as: How to get more users? How to get more schools on
board with Partneur? How to achieve credibility of the system?
How to manage legal issues? How to get more funding?
        </p>
        <p>Next, we have the team of IT Developers who develop the
code and database to build the website. They work together
with the Support team to ensure that the system has a
reliable, secure, user-friendly interface with high availability.
In addition to individual users, we also have students from
schools/educational institutions who are the secondary users
of Partneur. Thus, Partneur has partnerships with a few local
schools/institutions who utilize Partneur as a learning tool to
enhance the teaching process. Next, we have the Mentors
who overlook the teams and projects and provide guidance
throughout the process. Some Mentors might belong to an
educational institution but not necessarily. Next, we have
motivated, passionate individuals who have signed up and created
an account with Partneur. They may belong to an educational
institution, but not necessarily. Since these individuals usually
have little or no prior experience in entrepreneurship, they
have concerns such as how to identify suitable partners, how
to obtain funding, and how to estimate operating costs. Further,
these individuals form separate teams to create their projects.
Each team member has concerns like “I hope this team sticks
together”, “I hope our ideas are not stolen” etc. Every team
works on one or more projects. They create a Business model
and pitch deck. Investors fund the project if they like the pitch
deck. Investors think about factors such as Does the project has
a high ROI, low risk etc. A legal team backs the project pitch
deck to ensure that the Intellectual Property (IP) is protected.
After the investment in the project, the project proceeds to
becoming a final product. The final product ends up having a
positive effect on the community at large.</p>
      </sec>
      <sec id="sec-4-5">
        <title>E. Sustainability Awareness Diagram (SuSAD)</title>
        <p>Now that we have a clear picture of the whole system,
its processes, stakeholders and motivation, we can combine
our insights to create a sustainability awareness diagram of
the system. This is a diagram which details the immediate,
enabling and systemic effects of the entire system. A SusAD
diagram can be graphically represented in several forms. Here,
we have utilized a pentagon radar diagram. Each side of the
pentagon represents one of the sustainability dimensions.</p>
        <p>The diagram is split into three levels. At the innermost level,
the immediate effects of the system are listed, according to
the dimensions of sustainability that they impact. Immediate
effects include the direct effects of the production, use and
disposal of the software systems. The middle level and the
outermost level detail the enabling effects and systemic effects
of the system. Enabling effects arise from a system’s
application over time. This includes the opportunities to consume
more or lesser resources amongst the other changes induced
by the system. System effects represent the “persistent changes
observable at macro level”.</p>
        <p>
          One way of making use of the contents of the SuSAD is
to connect this to sustainability patterns, which can be found
in the Sustainability Pattern Catalogue (https://patternscatalog.
herokuapp.com) [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. Table 1 shows which patterns we have
identified as applicable for Partneur.
        </p>
        <p>
          In detail, these patterns are characterized by the following.
For details on examples from companies where these patterns
have been successfully applied, please see [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
        </p>
        <p>HR 2: Data Privacy and Security Policy — With the raise
of the Internet of Everything (IoE), people can now share
and access business or personal data from anywhere at any
time. Therefore, data privacy and especially security is a huge
concern in the world, especially for the IT industry that is
at the basis of this IoE. To fight these issues, 75% of the
companies established a Data Privacy statement where they
explain how they use our data. These statements constantly
evolve to meet the new regulations as we saw recently in
Europe. Moreover, since the most private data is the one that
is unreachable, companies also include Data Security in the
conception of their products or services that allows them to
increase the trust of their customer.</p>
        <p>G3: Collaborate with peers — According to the UN,
collaboration is one of the keys to meet Sustainable Development
Goals. By participating to the creation of laws or standards
companies, most of the companies try to increase their
cooperativity. Moreover, most of the companies also decided to
go further than local regulation in different places where they
operate, especially when they are in the third world. These
initiatives can lead to an international recognition in specific
fields for companies, and even sometimes to be defined as
“an example to follow”. Finally, local and internal cooperation
is also very important this is why more than half of the
companies implemented stakeholder engagement mechanisms
to define their own sustainability objectives (see pattern G1).</p>
        <p>
          G5: Transparency — Publish sustainability data to the
public audience and make pricing transparent. All of the 20
companies investigated in [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] provided environmental data
such as CO2 emissions, electricity consumption, resources
consumption, etc. They also published their different
donations, and few even reported their political contributions or
stated that they weren’t involved in it. On one hand, this
practice, allows companies to keep a track on the level of
advancement of their different sustainability strategies and give
the possibility for public institutions to confirm it. On the other
hand, they can inform customers about their different impacts
on sustainability.
        </p>
        <p>ENV3: Design ecological products — In order to reduce
their environmental impacts, companies decided to design
more ecological products regarding the materials used to
build them. This is concretely translated in two ways. First,
reuse materials into the manufacturing process, also known as
circular economy. Second, reduce or eliminate the proportion
of toxic or harmful materials from the products. In order to
be even more efficient, this strategy is most of the time
combined with the implementation of an end of life management
program which allows companies to directly refurbish, recycle
or reuse the products they sold (see patterns CONS1).</p>
        <p>
          ENV4: Resource efficiency — To limit their resources’
consumption companies, and then reduce their environmental
negative impacts, companies decided to set up initiatives to
economize different type of resources. Most of them decided
to focus on waste generation from office and water efficiency
both from office and from operations. We can also notice
that more than half of the companies decided to set up
paper efficiency strategy, mainly by optimizing their printing
policies. To maximize the impacts of this strategy, employees
need to be fully aware with environmental issues [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
        </p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>V. ANALYSIS AND DISCUSSION This section analyses and discusses the results of the case study summarized in the above presented artifacts.</title>
      <sec id="sec-5-1">
        <title>A. Usability of artifacts &amp; approach by the requirements engineers</title>
        <p>In creating each diagram for the case study, we found a fresh
perspective in understanding the system. It helped us get a
thorough big picture of the stakeholders, functions, processes,
goals, possible use-case scenarios and sustainable dimensions
underlying in the system.</p>
        <p>While creating the Stakeholder model diagram, we started
by categorizing the possible stakeholders of the system into
three groups: Individual, Business and Systemic. Each group
represents an increasingly larger set of people. Individual
stakeholders are single body stakeholders who play a role in
the system such as an owner or an individual user. Business
stakeholders are enterprises or organizations that play a role
in the system for example competitor businesses, educational
institutions etc. System stakeholders are larger, organizational
bodies that play a role in the system for example the local
community, environment etc. It was important to remember
that these stakeholders can be affected directly or indirectly by
the system. Not all stakeholders are direct users of the system.
We derived the list of stakeholders by iteratively assessing
the generic lists of stakeholders based on their functions
and roles and critically analyzing the possible stakeholders
that could exist in the three categories (Individuals, Business,
Systemic). In the future, it is planned to expand the stakeholder
analysis to include other sustainability actors (environment,
future generations etc.).</p>
        <p>Next, we assessed each of the different stakeholders from
the different ways in which they are categorized and derived
a list of goals specific to each stakeholder. Then we organized
the goals into a hierarchy of three categories, Business goals,
Usage goals and System goals, based on their overall objective.
Business goals are usually set by the Owners, Advisors,
higher level management etc. Usage goals are the standards
or expectations set by the direct users of the system. System
goals are goals about the system-characteristics which are set
by the development team to ensure the success of system.
Collectively, these goals work together to ensure the success
of the previous higher hierarchy of goals and ultimately the
Primary goal or the mission of the system. Finally, for each
goal, we noted which dimensions of sustainability satisfied
or improved by it. We noticed that these dimensions of
sustainability are common for related goals in the hierarchical
order, i.e., parent and child goals collectively improve common
dimensions of sustainability. Further, every goal higher up in
the hierarchical order (i.e., Business and Usage goals) must
have more than one subgoals. This ensured the cohesiveness
of the goals of the entire system.</p>
        <p>We followed this by creating a UML use case diagram.
Out of the list of stakeholders, we focused on the direct
users of the system. These are the primary, secondary and
tertiary users of the system. We mapped out all the possible
scenarios and actions they can perform in the system and
created a consolidated UML diagram. This diagram depicts
the relations between the direct users and their action flow
in the system. Next, we created the Rich picture diagram to
provide a big picture which is inclusive of all the stakeholders
in the system. It details all the processes occurring in the
system and interdependencies between the stakeholders of
the system. Every stakeholder can impact several processes.
Further, to enhance the big picture, the concerns of every
stakeholder are represented in their thought bubbles. This
shows us how different stakeholders have different objectives
from the system.</p>
        <p>Finally, we consolidate all the insights and information from
the above assessment of the system and produce the SusAD
diagram. We critically assessed the various stakeholders, their
goals, interdependencies and actions to achieve these goals in
the entire system to derive the possible immediate, enabling
and structural effects it creates. We classified the effects based
on the dimensions of sustainability they impact. This provided
us with the overall impacts created by the system and the
underlying process behind them. This helped in identifying the
ways in which we can optimize the processes of the system and
update the goals to make it more sustainable and impactful.</p>
      </sec>
      <sec id="sec-5-2">
        <title>B. Usefulness of the results for the start-up founders</title>
        <p>We elicited and structured information under the dimensions
of sustainability that the founder team had not previously
thought about in that manner. Their perspective was more
informed by an economics background and therefore applying
a software and systems engineering approach brought new
insights. In addition, the sustainability awareness diagram gave
more of a long-term view than the planning horizon a start-up
would usually analyze. While resources in terms of working
power and time are limited, just a discussion of 2 hours
brought a more than adequate amount of insights for the time
invested in the task. For example, the founders saw some good
points to highlight sustainable businesses on their platform.
All together they gave us the feedback that they gained some
additional insight from the analysis that can be beneficial to
their company going forward.</p>
        <p>
          The visual library used for the system vision had been
developed at ICT4S 2018 [
          <xref ref-type="bibr" rid="ref31">31</xref>
          ]. It was perceived as a useful
and adequate set of illustration icons by both the requirements
engineers and the start-up founders.
        </p>
      </sec>
      <sec id="sec-5-3">
        <title>C. Lessons Learned</title>
        <p>Looking back on the analysis of the research, there are a
couple of ways in which we could optimize the research to
improve the preciseness of details, results and impact of this case
study. An alternative way to initiate the sustainability analysis
part of the research from scratch would be by interviewing the
founders of Partneur about their perspectives of sustainability,
their sustainability analysis for the system thus far and their
future goals. In our case we had a general interview and
then some document analysis, which also led to a number
of insights but it would be interesting to compare the two
ways of approaching the creation of the sustainability analysis
and understand which way is potentially more effective and/or
efficient.</p>
        <p>After eliciting the requirements and concepts from the
information given to us, in a replication of this study we
could equally focus on drafting a clearer picture of the system
vision in direct iterative collaboration with the founders and
brainstorming the impacts of the system instead of creating
a draft and checking with them. This could be enhanced
with several in-depth conversations about the details of the
processes, the motivations of the stakeholders and creating
solutions for the concerns of every stakeholder.</p>
        <p>
          In this exploratory case study we have only one system
under development and therefore there was no ground to
perform any type of quantitative analysis, but once we can
replicate this study with several companies [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ], it would be
interesting to reuse rating scales for usability and usefulness
from previous work in the evaluation of artifact-based
requirements engineering [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ], [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ], [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ].
        </p>
      </sec>
      <sec id="sec-5-4">
        <title>D. Limitations and Threats to Validity</title>
        <p>
          The main limitation of the approach, i.e., what the approach
is suitable and intended for and what exceeds that, is that it
looks at a given scenario or situation in a development setting
and extrapolates the impacts that could potentially occur if the
system was going to be wildly successful. It does currently not
include the support for looking at alternative scenarios, which,
in the case of Partneur, could involve taking a closer look at
circular economy informed models [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ], [
          <xref ref-type="bibr" rid="ref30">30</xref>
          ] or regenerative
approaches [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ].
        </p>
        <p>The threats to validity include that of the three researchers
working on the analysis, two were only recently introduced to
the techniques that were applied. Furthermore, we could only
interview two of the four founders of Partneur, but the other
two were looped in by email to confirm preliminary results
and double-check we had not misunderstood anything in our
conversations.</p>
        <p>VI. CONCLUSIONS</p>
        <p>Most businesses and startups today depend on or are
facilitated by software. This paper showed a case study that employs
requirements engineering for sustainability and a sustainability
awareness diagram to help in the long-term estimation of
sustainability impacts. It is an artifact-based approach that
relies on several types of diagrams end our partner was a
startup company for online business model and team development.</p>
        <p>The presented diagrams and analysis are tools that can
support the critical assessment of the system or idea under
development. Stakeholder modeling and goal modeling can help
to resolve conflicts and find solutions for stakeholder concerns,
as well as explore the motivations of the stakeholders. The
sustainability awareness diagram helps to get better awareness
for the dimensions of sustainability impacted by the system.</p>
        <p>In order to further this research, we plan to observe Partneur
and follow them through their 5-year plan. Questions of
interest are: Are there differences in their long-term impacts
because they explicitly incorporated sustainability goals? What
are positive impacts? Are there negative side effect? How to
assess and judge that value difference?</p>
        <p>We are currently planning the next iteration and phase via
a facilitated team workshop with moderated discussions of
the sustainability dimensions with regard to Partneur’s latest
development status.</p>
        <p>Acknowledgement: We thank the Partneur co-founders
Dean Heiss and JR Jimenez for their input.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>Ian</given-names>
            <surname>Alexander</surname>
          </string-name>
          and
          <string-name>
            <given-names>Suzanne</given-names>
            <surname>Robertson</surname>
          </string-name>
          .
          <article-title>Understanding project sociology by modeling stakeholders</article-title>
          .
          <source>IEEE Software</source>
          ,
          <volume>21</volume>
          (
          <issue>1</issue>
          ):
          <fpage>23</fpage>
          -
          <lpage>27</lpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Victor</surname>
            <given-names>R Basili</given-names>
          </string-name>
          , Forrest Shull, and
          <string-name>
            <given-names>Filippo</given-names>
            <surname>Lanubile</surname>
          </string-name>
          .
          <article-title>Building knowledge through families of experiments</article-title>
          .
          <source>IEEE Transactions on Software Engineering</source>
          ,
          <volume>25</volume>
          (
          <issue>4</issue>
          ):
          <fpage>456</fpage>
          -
          <lpage>473</lpage>
          ,
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>Christoph</given-names>
            <surname>Becker</surname>
          </string-name>
          , Stefanie Betz, Ruzanna Chitchyan, Leticia Duboc, Steve Easterbrook, Birgit Penzenstadler, Norbert Seyff, and
          <string-name>
            <given-names>Colin</given-names>
            <surname>Venters</surname>
          </string-name>
          .
          <article-title>Requirements: The key to sustainability</article-title>
          .
          <source>IEEE Software</source>
          ,
          <volume>33</volume>
          (
          <issue>1</issue>
          ):
          <fpage>56</fpage>
          -
          <lpage>65</lpage>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>Christoph</given-names>
            <surname>Becker</surname>
          </string-name>
          , Ruzanna Chitchyan, Leticia Duboc, Steve Easterbrook, Birgit Penzenstadler, Norbert Seyff, and Colin C Venters.
          <article-title>Sustainability design and software: The karlskrona manifesto</article-title>
          .
          <source>In Proceedings of the 37th International Conference on Software Engineering-Volume</source>
          <volume>2</volume>
          , pages
          <fpage>467</fpage>
          -
          <lpage>476</lpage>
          . IEEE Press,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>Sheila</given-names>
            <surname>Bonini</surname>
          </string-name>
          .
          <article-title>Sustainability's strategic worth: Mckinsey global survey results</article-title>
          . https://www.mckinsey.
          <article-title>com/business-functions/sustainabilityand-resource-productivity/our-insights/sustainabilitys-strategic-worthmckinsey-global-survey-</article-title>
          <string-name>
            <surname>results</surname>
          </string-name>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Jeremy</surname>
            <given-names>L</given-names>
          </string-name>
          <string-name>
            <surname>Caradonna. Sustainability</surname>
          </string-name>
          :
          <article-title>A history</article-title>
          . Oxford University Press,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>Ruzanna</given-names>
            <surname>Chitchyan</surname>
          </string-name>
          , Stefanie Betz, Leticia Duboc, Birgit Penzenstadler, Steve Easterbrook, Christophe Ponsard, and
          <string-name>
            <given-names>Colin</given-names>
            <surname>Venters</surname>
          </string-name>
          .
          <article-title>Evidencing sustainability design through examples</article-title>
          .
          <source>In Intl. Workshop RE4SuSy</source>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>Germain</given-names>
            <surname>De</surname>
          </string-name>
          <article-title>´roche and Birgit Penzenstadler</article-title>
          .
          <article-title>An analysis of best practice patterns for corporate social responsibility in top it companies</article-title>
          .
          <source>Technologies</source>
          ,
          <volume>6</volume>
          (
          <issue>3</issue>
          ):
          <fpage>76</fpage>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Steve</surname>
          </string-name>
          et al. Easterbrook.
          <article-title>Selecting empirical methods for software engineering research. Guide to advanced empirical software engineering</article-title>
          , pages
          <fpage>285</fpage>
          -
          <lpage>311</lpage>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>Daniel</given-names>
            <surname>Mendez</surname>
          </string-name>
          Fernandez and
          <string-name>
            <given-names>Birgit</given-names>
            <surname>Penzenstadler</surname>
          </string-name>
          .
          <article-title>Artefact-based requirements engineering: the amdire approach</article-title>
          .
          <source>Requirements Engineering</source>
          ,
          <volume>20</volume>
          (
          <issue>4</issue>
          ):
          <fpage>405</fpage>
          -
          <lpage>434</lpage>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Martin</surname>
            <given-names>Geissdoerfer</given-names>
          </string-name>
          , Paulo Savaget,
          <article-title>Nancy MP Bocken, and Erik Jan Hultink. The circular economy-a new sustainability paradigm</article-title>
          ?
          <source>Journal of cleaner production</source>
          ,
          <volume>143</volume>
          :
          <fpage>757</fpage>
          -
          <lpage>768</lpage>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>Martin</given-names>
            <surname>Glinz</surname>
          </string-name>
          and
          <string-name>
            <given-names>Roel J.</given-names>
            <surname>Wieringa</surname>
          </string-name>
          . Guest editors'
          <article-title>introduction: Stakeholders in requirements engineering</article-title>
          .
          <source>IEEE Software</source>
          ,
          <volume>24</volume>
          (
          <issue>2</issue>
          ):
          <fpage>18</fpage>
          -
          <lpage>20</lpage>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>Lorenz</surname>
            <given-names>M Hilty</given-names>
          </string-name>
          and
          <string-name>
            <given-names>Bernard</given-names>
            <surname>Aebischer</surname>
          </string-name>
          .
          <article-title>Ict for sustainability: An emerging research field</article-title>
          .
          <source>In ICT Innovations for Sustainability</source>
          , pages
          <fpage>3</fpage>
          -
          <lpage>36</lpage>
          . Springer,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>Alexandre</given-names>
            <surname>Joyce and Raymond L Paquin</surname>
          </string-name>
          .
          <article-title>The triple layered business model canvas: A tool to design more sustainable business models</article-title>
          .
          <source>Journal of Cleaner Production</source>
          ,
          <volume>135</volume>
          :
          <fpage>1474</fpage>
          -
          <lpage>1486</lpage>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>DL</given-names>
            <surname>Lautenschutz</surname>
          </string-name>
          ,
          <article-title>Sergio Espan˜a, AC Hankel, SJ Overbeek, and</article-title>
          <string-name>
            <given-names>Patricia</given-names>
            <surname>Lago</surname>
          </string-name>
          .
          <article-title>A comparative analysis of green ict maturity models</article-title>
          .
          <source>In ICT4S2018</source>
          , volume
          <volume>52</volume>
          , pages
          <fpage>153</fpage>
          -
          <lpage>167</lpage>
          . EasyChair,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>D.</given-names>
            <surname>Mendez Fernandez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Lochmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Penzenstadler</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Wagner</surname>
          </string-name>
          .
          <article-title>A Case Study on the Application of an Artefact-Based Requirements Engineering Approach</article-title>
          .
          <source>In Proceedings of the 15th Annual Conference on Evaluation and Assessment in Software Engineering (EASE</source>
          <year>2011</year>
          ), pages
          <fpage>104</fpage>
          -
          <lpage>113</lpage>
          . Institution of Engineering and Technology (IET),
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>Andrew</given-names>
            <surname>Monk</surname>
          </string-name>
          and
          <string-name>
            <given-names>Steve</given-names>
            <surname>Howard</surname>
          </string-name>
          .
          <article-title>Methods &amp; tools: the rich picture: a tool for reasoning about work context</article-title>
          .
          <source>interactions</source>
          ,
          <volume>5</volume>
          (
          <issue>2</issue>
          ):
          <fpage>21</fpage>
          -
          <lpage>30</lpage>
          ,
          <year>1998</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>Alexander</given-names>
            <surname>Osterwalder</surname>
          </string-name>
          and
          <string-name>
            <given-names>Yves</given-names>
            <surname>Pigneur</surname>
          </string-name>
          .
          <article-title>Business model generation: a handbook for visionaries, game changers, and challengers</article-title>
          . John Wiley &amp; Sons,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>B.</given-names>
            <surname>Penzenstadler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. Mendez</given-names>
            <surname>Fernandez</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Eckhardt</surname>
          </string-name>
          .
          <article-title>Two Replication Studies for Evaluating Artefact Models in RE: Results and Lessons Learnt</article-title>
          . In International Workshop on Replication in
          <source>Empirical Software Engineering Research (RESER)</source>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>B.</given-names>
            <surname>Penzenstadler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. Mendez</given-names>
            <surname>Fernandez</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Eckhardt</surname>
          </string-name>
          .
          <article-title>Understanding the Impact of Artefact-based RE - Design of a Replication Study -</article-title>
          .
          <source>In International Symposium on Empirical Software Engineering and Measurement</source>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <given-names>Birgit</given-names>
            <surname>Penzenstadler</surname>
          </string-name>
          .
          <article-title>Infusing green: Requirements engineering for green in and through software systems</article-title>
          .
          <source>In RE4SuSy@ RE</source>
          , pages
          <fpage>44</fpage>
          -
          <lpage>53</lpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <given-names>Birgit</given-names>
            <surname>Penzenstadler</surname>
          </string-name>
          .
          <article-title>Sustainability analysis and ease of learning in artifact-based requirements engineering: The newest member of the family of studies (it'sa girl!)</article-title>
          .
          <source>Information and Software Technology</source>
          ,
          <volume>95</volume>
          :
          <fpage>130</fpage>
          -
          <lpage>146</lpage>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <surname>Birgit</surname>
            <given-names>Penzenstadler</given-names>
          </string-name>
          , Stefanie Betz, Colin C Venters, Ruzanna Chitchyan, Jari Porras, Norbert Seyff, Leticia Duboc, and
          <string-name>
            <given-names>Christoph</given-names>
            <surname>Becker</surname>
          </string-name>
          .
          <article-title>Everything is interrelated: teaching software engineering for sustainability</article-title>
          .
          <source>In Proceedings of the 40th International Conference on Software Engineering: Software Engineering Education and Training</source>
          , pages
          <fpage>153</fpage>
          -
          <lpage>162</lpage>
          . ACM,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <given-names>Birgit</given-names>
            <surname>Penzenstadler</surname>
          </string-name>
          and
          <string-name>
            <given-names>Henning</given-names>
            <surname>Femmer</surname>
          </string-name>
          .
          <article-title>A generic model for sustainability with process-and product-specific instances</article-title>
          .
          <source>In Proceedings of the 2013 workshop on Green in/by software engineering</source>
          , pages
          <fpage>3</fpage>
          -
          <lpage>8</lpage>
          . ACM,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <surname>Birgit</surname>
            <given-names>Penzenstadler</given-names>
          </string-name>
          , Henning Femmer, and
          <string-name>
            <given-names>Debra</given-names>
            <surname>Richardson</surname>
          </string-name>
          .
          <article-title>Who is the advocate?: stakeholders for sustainability</article-title>
          .
          <source>In Proceedings of the 2nd International Workshop on Green and Sustainable Software</source>
          , pages
          <fpage>70</fpage>
          -
          <lpage>77</lpage>
          . IEEE Press,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <surname>Birgit</surname>
            <given-names>Penzenstadler</given-names>
          </string-name>
          , Joseph Mehrabi, and
          <string-name>
            <surname>Debra</surname>
          </string-name>
          J Richardson.
          <article-title>Supporting physicians by re4s: Evaluating requirements engineering for sustainability in the medical domain</article-title>
          .
          <source>In Proceedings of the Fourth International Workshop on Green and Sustainable Software</source>
          , pages
          <fpage>36</fpage>
          -
          <lpage>42</lpage>
          . IEEE Press,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [27]
          <string-name>
            <given-names>Eric</given-names>
            <surname>Ries</surname>
          </string-name>
          .
          <article-title>Minimum viable product: a guide</article-title>
          .
          <source>Startup lessons learned</source>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          [28]
          <string-name>
            <surname>Michael</surname>
          </string-name>
          J Ryan.
          <volume>1</volume>
          .
          <article-title>2. 2 the role of stakeholders in requirements elicitation</article-title>
          .
          <source>In INCOSE International Symposium</source>
          , volume
          <volume>24</volume>
          , pages
          <fpage>16</fpage>
          -
          <lpage>26</lpage>
          . Wiley Online Library,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          [29]
          <string-name>
            <surname>Norbert</surname>
            <given-names>Seyff</given-names>
          </string-name>
          , Stefanie Betz, Leticia Duboc, Colin Venters, Christoph Becker, Ruzanna Chitchyan, Birgit Penzenstadler, and
          <article-title>Markus No¨bauer. Tailoring requirements negotiation to sustainability</article-title>
          .
          <source>In 2018 IEEE 26th International Requirements Engineering Conference (RE)</source>
          , pages
          <fpage>304</fpage>
          -
          <lpage>314</lpage>
          . IEEE,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          [30]
          <string-name>
            <surname>Walter</surname>
            <given-names>R</given-names>
          </string-name>
          <string-name>
            <surname>Stahel.</surname>
          </string-name>
          <article-title>The circular economy</article-title>
          .
          <source>Nature News</source>
          ,
          <volume>531</volume>
          (
          <issue>7595</issue>
          ):
          <fpage>435</fpage>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          [31]
          <string-name>
            <given-names>Miriam</given-names>
            <surname>Sturdee</surname>
          </string-name>
          .
          <article-title>Creating a visual library for a sustainability conference</article-title>
          .
          <source>In ACM Creativity and Cognition</source>
          ,
          <year>2019</year>
          . under review.
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          [32]
          <string-name>
            <surname>Gerald</surname>
            <given-names>M</given-names>
          </string-name>
          <string-name>
            <surname>Weinberg and Edward L Schulman</surname>
          </string-name>
          .
          <article-title>Goals and performance in computer programming</article-title>
          .
          <source>Human factors</source>
          ,
          <volume>16</volume>
          (
          <issue>1</issue>
          ):
          <fpage>70</fpage>
          -
          <lpage>77</lpage>
          ,
          <year>1974</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>