<!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>Towards Tool-support for Sustainability Profiling</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Ahmed D. Alharthi, Maria Spichkova and Margaret Hamilton School of Science, RMIT University</institution>
          ,
          <addr-line>Melbourne</addr-line>
          ,
          <country country="AU">Australia</country>
        </aff>
      </contrib-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>I. INTRODUCTION</p>
      <p>
        The impact of software systems on social and economic
activities increases each year, which makes the analysis of
sustainability requirements of the software systems more and
more important. Becker et al. [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] highlighted the point that
software systems are a major driver of social and economic
activity, which demands a paradigm shift in the software
engineering mind-set to take sustainability into account. The
key point for this is in requirements engineering activities,
which should consider sustainability design principles.
      </p>
      <p>Requirements engineers still have a narrow understanding of
sustainability; they focus on one or two dimensions of
sustainability such as environmental and economic sustainability, or on
the non-functional requirements for technical sustainability such
as maintainability and reusability requirements. Requirements
engineers should take into account sustainability requirements,
which implies additional analysis in the early stages of software
development to maximise the positive impact and to minimise
the negative impact of all sustainability dimensions. To support
these activities a tool is required. Contributions: In this paper, we analyse the core features of</p>
      <p>
        The tool has to be easy-to-use and allow involvement of SuSoftPro (abbreviated from Sustainable Software Profiling) in
stakeholders from diverse groups in the process of software comparison with two approaches which employ Multi-Criteria
development, as empowering more participants with a diversity Decision Analysis (MCDA) in requirements engineering. We
of perspectives leads to more sustainable systems [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. consider a case study of a Skin Cancer Information System
      </p>
      <p>There are many requirements engineering (RE) tools to elicit, (SCIS), which is a clinical software to store patient health
analyse, model, trace, document, manage, as well as verify records, to optimise SuSoftPro and to increase its usability.
and validate software requirements. Some of these tools are Outline: The rest of this paper is organised as follows.
web-based, which allows collaborative access to resources. In Section II, we analyse and evaluate the core features of
However, none of them has the ability to analyse sustainability SuSoftPro by comparing against two RE approaches which a
requirements by involving stakeholders. Thus, the goal of our different methodology using MCDA. Section III illustrates the
ongoing work is to evaluate Sustainability Profiling for Software work flow using a case study from the eHealth domain. Further
(SuSoftPro) for analysis of sustainability requirements. More discussion of the SuSoftPro features is presented in Section IV.
precisely, we are aiming to analyse the SuSoftPro method in- Section V covers related works. Finally, Section VI summarises
depth and evaluate the tool-support through comparison and the paper and outlines the directions of our future work.</p>
      <p>
        In our previous work, we introduced a methodology with
supported tool to analyse sustainability requirements for
longliving software systems [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. This methodology provides a
software sustainability profiling that involves a Fuzzy Rating
Scale (FRS, cf. [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]), and uses the Technique for Order
Preference by Similarity to Ideal Solution (TOPSIS, cf. [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]).
      </p>
      <p>
        Our new tool presents sustainability as a five-star rating label, a
visualisation for the degree of the five sustainability dimensions,
and a bar graph which illustrates the overall sustainability
level for each requirement. The tool enables requirements
engineers to defining stakeholder groups allotted to one or more
of the five sustainability dimensions, building a fuzzy rating
scale-questionnaire with regard to a sustainability dimension,
specifying the high-level requirements and assign them to
created groups, assigning stakeholders and allow them to rating
requirements, analysing sustainability, and generating software
sustainability profiling [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. We discussed the core steps of
the SuSoftPro process in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] to answer "What is SuSoftPro?".
      </p>
    </sec>
    <sec id="sec-2">
      <title>While this work is to answer: What are the differences between</title>
    </sec>
    <sec id="sec-3">
      <title>SuSoftPro and RE approaches using MCDA in sustainability context? and How can SuSoftPro be applied?</title>
      <p>To analyse and evaluate our methodology and the SuSoftPro
tool, we compared the SuSoftPro against two approaches
that developed a methodology using MCDA and used for
requirements engineering domain. Below, we address the
procedure, analysis, and result of the comparative evaluation.</p>
    </sec>
    <sec id="sec-4">
      <title>A. Procedure</title>
      <p>To perform comparative evaluation against SuSoftPro, we
defined three criteria for selecting frameworks from literature
studies as follow:</p>
      <p>Scope: Developed for requirements engineering context,
Process: Involved MCDA and stakeholders, and</p>
      <p>Objective: Analysed sustainability.</p>
      <p>Because there was no study meet the three criteria, we
removed the objective criteria (analysing sustainability) because
no MCDA technique has been used to analyse sustainability
within RE as well as sustainability is a new growing topic in
RE. Thus, only two frameworks were found: ReproTizer and
sureCM.</p>
      <p>Then, we specified 9 sub-criteria to analyse the three
frameworks (SuSoftPro, ReproTizer and sureCM) including
the purpose of the methodology, collection method, weight
scale, analysis method which is one type of the MCDA,
participant, rank updates that the methodology can instantly
re-compute results, supported tool, computational
complexity, error-proneness, prevent imprecision inherent in human
responses, number of criteria.</p>
    </sec>
    <sec id="sec-5">
      <title>B. Analysis of selected studies</title>
      <p>We analysed SuSoftPro’s core process and features with
regard to two other frameworks for requirement analysis:
ReproTizer and sureCM.</p>
      <p>
        1) SuSoftPro: SuSoftPro1 is a methodology and tool-support
to analyse sustainability requirements within sustainability
dimensions having individual, social, economic and
environmental dimensions. The general idea of the SuSoftPro process
is presented in Figure 1 and discussed in [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. There are 7
core steps allow requirements engineers to:
      </p>
      <p>Define stakeholder groups: through creating stakeholder
group based on stakeholders' role or expert, and then</p>
      <sec id="sec-5-1">
        <title>1Link of the tool-support: https://www.SuSoftPro.ahmedalharthi.net</title>
        <p>assign this group to one or more of the five sustainability
dimensions, so the group will be allotted to stakeholders
and requirements;
Define questions: that will be generated automatically as
five instructions with regard to a sustainability dimension
for FRS questionnaire;
Define requirements: via the specifications of the
highlevel requirements and allotting them to related groups
affected stakeholders and requirement ownership;
Assign stakeholders: to related groups based on
stakeholders' role in the system and their areas of expertise after
defining them;
Rate requirements: through enable stakeholders to use
ratio quantity approach as FRS responses;
Analyse sustainability: with MCDA using TOPSIS
approach to determine the level of sustainability dimensions
and sustainability requirements measurements; and</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Generate software sustainability profiling: including a</title>
      <p>five-star sustainability rating label, visualisation of
sustainability dimension levels, and bar-chart graph for each
sustainability requirements level.</p>
      <p>Sustainability profiling provides insight and identifies the
predictability of sustainability to enable requirements engineers
and stakeholders to analyse and break true
requirementsdependencies, and the interaction and overlapping of
sustainability dimensions by predicting the outcome value before
developing software systems.</p>
      <p>
        2) ReproTizer: ReproTizer was elaborated by Achimugu
et al. [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. It allows requirements prioritisation via capturing
stakeholders' requirement ranks through numeric weight scale
that are valued between 1 and 5, the prioritised requirements
are then analysed using a Weighted Average Decision Matrix
(WADM). ReproTizer framework has five steps as following:
Define requirements Requirements engineers specify
requirements list;
Add stakeholder: Requirements engineers add stakeholder
and assign them to requirements;
Score requirements: Stakeholders score each requirements
using a Likert scale from 1 to 5;
      </p>
    </sec>
    <sec id="sec-7">
      <title>Compute requirements prioritisation: Requirements priori</title>
      <p>tisation automatically are determined using WADM, after
scoring requirements by stakeholders; and
Artifact exports from
requirements projects</p>
    </sec>
    <sec id="sec-8">
      <title>Generate requirements prioritisation list: Weight of each</title>
      <p>
        requirement prioritisation is presented in ordered list.
3) sureCM: sureCM was introduced by Mairiza et al. [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ],
focusing on resolving non-functional requirements (NFR) such
as security-usability conflicts. Like SuSoftPro, it also applies
the TOPSIS method to analyse the collected data, but unlike
SuSoftPro the sureCM framework does not have any tool
support. sureCM framework has four steps including:
Identify NFRs conflict: via conflict relationship digram,
requirements engineers need to identify if NFRs have
conflict;
Rank characterize conflict: through recognising parameters
of alternative functionality, metrics, or measures;
Analysing solution: via TOPSIS the best alternative
solution and the worst solution are calculated; and
Present selected solution: Alternative solutions list is
presented from the highest to the lowest rank.
      </p>
    </sec>
    <sec id="sec-9">
      <title>C. Result</title>
      <p>
        As shown in Table I, both SuSoftPro and ReproTizer work
with more than two criteria for analysis, and are supported
by a tool, providing a fully systematic computation to prevent
errors. The sureCM framework is based on a semi-automatic
computation and data collection (requirements rating), which
are more error-proneness than a fully automated solution.
Another advantage of SuSoftPro is utilising the FRS, which
allows better precision of requirements' rating. Although the
FRS application provides more accurate scale than Likert scale
to capture real-valued responses, the FRS is not fully
friendlyto-use scale [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. With minor orientation and guidances will be
enough to use the FRS for responding.
      </p>
      <p>Neither ReproTizer nor sureCM support the sustainability
context whereas SuSoftPro supports and utilises a fully
systematic and comprehensive discovery methodology to analyse
sustainability requirements.</p>
      <p>The core results of the comparison are summarised in Table I.</p>
      <sec id="sec-9-1">
        <title>III. CASE STUDY</title>
        <p>
          To illustrate how SuSoftPro can be applied, we used a case
study from the eHealth domain, based on a real-life project,
a Skin Cancer Information System (SCIS), cf. [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. SCIS is a
web-based software system to register the diagnoses of skin
cancer along with the treatments. SCIS has five stakeholder
roles:
        </p>
      </sec>
      <sec id="sec-9-2">
        <title>1) Physicians,</title>
        <p>2) Nurses,
3) Receptionists,
4) Administrators and Managers, and
5) Developers and IT Support.</p>
      </sec>
    </sec>
    <sec id="sec-10">
      <title>A. Defining Stakeholder Groups</title>
      <p>Requirements engineers have selected 14 stakeholders (two
physicians, two nurses, four receptionists, three administrators
and managers, and three developers and IT supports). Five
groups (corresponding to the stakeholder roles) are created and
assigned to sustainability dimensions, cf. Table II. Groups are
used not only to group stakeholders with related sustainability
dimensions but also to associate requirements with related
stakeholder groups. For instance, nurse group is assigned to
individual and social sustainability dimensions as well as each
requirements affecting or related to nurses are assigned to nurse
group.</p>
    </sec>
    <sec id="sec-11">
      <title>B. Defining Questions</title>
      <p>SuSoftPro generates questions/instructions according to the
following format:
“Rate the influence of the requirement on the X sustainability”,
where X is replaced in a concrete case by the corresponding
sustainability dimension: individual, social, technical, economic,
and environmental. There is an option to adjust each question,
but we decided to continue with the generated questions for
our case.</p>
    </sec>
    <sec id="sec-12">
      <title>C. Defining Requirements</title>
      <p>
        A 23 high-level requirements specification of the system
in [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] are imported from a Comma Separated Values (CSV) file
and assigned to related groups, cf. Table III. Each requirement
is assigned to one or more groups only when the requirement
will impact or belong to the associated stakeholders in the
group. For example, Req. 2 "Create a new record" is allocated
to the physician, nurse, and developer and IT support groups
because they will utilise this requirement and it may affect
them.
      </p>
    </sec>
    <sec id="sec-13">
      <title>D. Assigning Stakeholders</title>
      <p>The user profiles for the stakeholders are created and then
assigned to the groups, as shown in Figure 2. Therefore,
each group is assigned to related sustainability dimensions,
requirements and stakeholders. In other word, stakeholders are
grouped and designated to related sustainability dimensions and
requirements. Adjusting stakeholder details are automatically
prevented when stakeholders start responding to the
questionnaire. For example, a nurse begins answering the questionnaire,
the change of the group and other related details are frozen.</p>
      <p>After building the questionnaire, generating and sending
autosign-in link to the stakeholders to access the questionnaire, the
status of all the stakeholders in the project becomes waiting,
until they begin to respond to the questionnaire. For each
high-level requirement to be rated, the stakeholder can rate
its influence on the sustainability dimensions using interface
presented on Figure 3. In SCIS case to illustrate the flexibility
of the tool, nurses have 30 questions to answer, where
15 questions are on the individual sustainability
perspective for the 15 allotted requirements to physician and nurse
group in the SCIS, and
15 questions for the social perspective of the same
requirements.</p>
      <p>Physicians have 45 questions:
30 questions are the same as for the nurse group,
additional 10 questions on the economic perspective of
the same requirements.</p>
      <p>SCIS REQUIREMENTS WITH SUSTAINABILITY RATING WHERE 1 IS THE HIGHEST AND 0 THE LOWEST POSSIBLE RATING
16
There are 24 questions covering the individual, social, and
economic perspective for requirements related to receptionists.</p>
      <p>Administrators and managers are assigned 52 questions to
answer for administration and managements requirements
covering the following perspectives (13 questions each): economic,
technical, social, and environmental perspectives. Developers
and IT people have 92 questions for all the requirements
covering 23 questions on each individual, technical, economic,
and environmental sustainability perspective, see Table III.</p>
      <p>Guidance on how to use the FRS is provided for stakeholders,
so stakeholders such as nurses or physicians, who have not seen
or used the FRS before, will be easily guided. They also had</p>
      <p>Assigned Group
the ability to save their responses and return back to continue.</p>
      <p>An option for skipping any question for certain requirements
within particular sustainability dimension is implemented. For
example, a physician was asked to rate the influence of
Req. 6 "Insert procedure" on economic sustainability; the
physician was able to skip this question. However, the question
has a probability to be answered by other stakeholders such
as other physicians and developers who are assigned to rate
Req. 6, for the economic dimension.</p>
    </sec>
    <sec id="sec-14">
      <title>F. Analysing Sustainability</title>
      <p>Only the individual dimension is in a satisfactory range
which is more than 0.60 (the corresponding bar in the
chart is light green).</p>
      <p>The technical, social and economic dimensions are
between 0.54 and 0.58 (the corresponding bars in the chart
are yellow).</p>
      <p>The environmental dimensions is in an unsatisfactory
range which is around 0.35 (the corresponding bars in
the chart are orange).</p>
      <p>
        The sustainability value of each requirement is indicated in
Table III. The value in the result is between 0-1 where in the
TOPSIS method 0 represents the worst ideal solution and 1 is
the best ideal solution [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>As the next step, SuSoftPro applies the TOPSIS method and
creates the sustainability profiling of the system. A systematic
computation of TOPSIS is performed and recalculated when IV. DISCUSSION
each stakeholder submits their response. Also, rated require- SuSoftPro is an automated solution in the sustainability
ments with its questions are automatically locked when any context to analyse sustainability requirements based on
quesstakeholder begins to rate it, so engineers can not amend them. tionnaire, in which quantity data gathers via FRS questionnaire
and analyses using TOPSIS. The result presents as
sustainG. Generating Software Sustainability Profiling ability profiling for software having a five-star rating label,</p>
      <p>
        The created profiling presents in the dashboard in Figure 4. visualisation of the degree of sustainability dimensions, and
Based on the simulated responses we used to illustrate the bar graph of overall sustainability level for each requirement.
example (where only 13 out of 14 stakeholders submitted their From the comparative evaluation result, both SuSoftPro and
ReproTizer approaches are based on individuals perspective.
responses), the overall sustainability of the SCIS has FFF
three-star rating (3 out of 5). The five sustainability dimensions The perspective is important to change sustainability of software
are presented by a bar chart: when users’ opinions are addressed and taken into account.
Scholars of social practice theory believed that practices and
perspectives of individuals in the performance of daily tasks
stimulate social, economic and environmental changes [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
      </p>
      <p>The SuSoftPro tool aggregated all stakeholders' requirements.</p>
      <p>This enables the recognition of diverse visions and voices
into decisions that are needed to develop sustainable software.</p>
      <p>Thus, the point of sustainability perspective while analysing
requirements could be the main force in providing sustainable
software in the early stages.</p>
      <p>
        Besides, providing FRS in SuSoftPro to capture
individuals views was necessary to prevent imprecision. However,
there is the need for reconciling plurality through supporting
stakeholders with the diversity of points of view that ensure
sustainability [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>
        As the case study demonstrated, practitioners were supplied
with information related to sustainability aspects. The
sustainability profiling presented sustainability scores for each
requirements and sustainability dimensions. These scores will
improve the sustainability attention and allow practitioners
to provide sustainable software. For example, the lowest
sustainability scores in SCIS was Req. 9 "Allocate pathology
report to procedure", so practitioners could give more attention
to improve this requirements and acceptance as well as increase
users satisfaction which lead to sustainability [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
      </p>
      <p>Additionally, the tool allows requirements engineers to
create groups with regard to stakeholders diversity or role.</p>
      <p>For example, groups in SCIS profiling were divided into user
role. Grouping stakeholders and requirements are not only to
reduce the number of questions but also to express their opinion</p>
      <p>Fig. 4. The SuSoftPro Dashboard for the SCIS profile about what is related to them. Also, there are two ways to
invite stakeholders either with a public link to accommodate
more stakeholders with self-registration or being registered by
the engineers.</p>
      <p>
        Two different colours are provided for practitioners with
colour-deficient vision in the tool. The red colour is replaced
with blue when the colour-deficient vision is opted. This option
ensures better accessibility and equally user experience to read
sustainability profile because one in every 12 people has colour
vision deficiency [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
      </p>
      <p>Intuitive design is taken into account during designing the
tool. For practitioners, the tool divided into logic sections
including a dashboard, questionnaire, requirements,
stakeholders, and profiling. A systematic computation of stakeholders
responses after submitting is implemented to prevent error.</p>
      <p>
        Icons and colours also are provided for an effortless
understanding of the tool. However, stakeholders may face difficulty
to understand the FRS when they start to respond [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]). A
guidance with example is developed to accomplish rating and
increase the usability.
      </p>
      <p>The tool also allow integration with commonly used
requirements engineering tools such as ReqMan and Rational
DOORS: Its export and import features allows the exchange
of requirement specifications using the CSV format.</p>
      <p>SuSoftPro has emerged to:</p>
      <p>Capture more individuals perspective with the diversity
and accurate impression,
Analyse software requirements in sustainability context,
and</p>
      <p>Present the result as a sustainability profiling.</p>
      <p>However, a few limitations need to be taken into account.</p>
      <p>There is need to provide a standards for sustainability
fivestar rating label to specify the minimum level of sustainability
performance that software should meet before they can be
developed. Also, when the number of requirements is increased and
a group has assigned more than two sustainability dimensions,
the number of question will be large either double or treble
requirements. This large number could lead to take a long time
for responding to a questionnaire, so stakeholders might feel
more annoying. An initial optimised solution, requirements
engineers can divide a group that allotted to more than two
sustainability dimensions into two groups and then assign them
to one or two different sustainability dimensions. Another
solution is to leverage machine learning to assign stakeholders
and divide questions between one group. We did optimise the
number of questions in the tool through establishing a group
and assign stakeholders and requirements to it. This solution
assists to reduce the number of questions about 20-50% in
some cases.</p>
      <p>V. RELATED WORK</p>
      <p>
        Some works on embedding sustainability in the software
development process, e.g. [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], are focusing on environmental
aspects. In SuSoftPro, contrary to them, we cover individual,
social, economic, technical and environmental dimensions.
      </p>
      <p>
        Porras et al. [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] proposed a manually model-based analysis
to evaluate the ICT projects wrt. sustainability effect. Although
the model covers sustainability dimension and impacts, the
model is not simple and systematic approach to measure
sustainability during software developments and usages. There
is limited of stakeholders involving to provide sustainability
perceptions, so this limitation will lead to a lack of sustainability
perceptions.
      </p>
      <p>
        Mahaux [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] suggested that additional analysis activities
need to have support from participants who are involved
as stakeholders in the process of software developments.
      </p>
      <p>Hence, involving supported participants will ensure sustainable
software. This argument emerges the need of a tool involving
supported participants easily, and the SuSoftPro is developed
to involve supported participants vis providing their perspective
as support.</p>
      <p>
        Al Hinai [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] introduced a number of metrics and an
accompanying method for analysing social sustainability requirements
of software systems. The method is not systematic and easy
to elicit the values because of the variety of translating value,
and the potential of conflicting value types.
      </p>
      <p>
        Chitchyan et al. [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] presented the results of a qualitative
study, which goal was to explore perceptions and attitudes
towards sustainability, of requirements engineering practitioners.
      </p>
      <p>The lack of methodological support was one of the identified
barriers to the engagement with sustainability design in RE
practice. The SuSoftPro is a solution to overcome this barrier
through engaging practitioners and stakeholders to analyse
sustainability.</p>
      <p>
        Becker et al. [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] compared two projects to illustrate the
software development within and without sustainability design,
so they stated that requirements engineering is the key to
sustainability through following interdisciplinary,
stakeholderfocused approach, and systems-oriented as well as supporting
by higher management and executives. Their analysis approach
is to visualise the systems’ potential impacts as immediate,
enabling, and structural impacts within the five sustainability
dimensions. While SuSoftPro visualises the sustainability level
of software and requirements within the five sustainability
dimensions. Both practices could assist to understand the
sustainability of software systems and their impact on sustainability
aspects.
      </p>
      <p>
        A number of requirements engineering tools with general
or specific features for eliciting, analysing, modelling,
tracing, documenting, managing, and verifying and validating
requirements [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]. Some of these tools are begin to facilitate
web-based solution in order to allow collaborative access
to resources, while others particularly dominated tools are
becoming more complex and difficult to use. However, none
of them has the ability to analyse sustainability requirements
by involving stakeholders with regard to the sustainability
dimensions. Hence SuSoftPro was developed to enable the
analysis of sustainability through extensive questionnaires on
requirements which cover the sustainability context of the
software and can include a wide range of stakeholders.
      </p>
      <p>VI. CONCLUSIONS</p>
      <p>We evaluated SuSoftPro with two approaches that developed
a methodology using Multi-Criteria Decision Analysis (MCDA)
and used for requirements engineering domain. The evaluation
demonstrated a number of advantages of SuSoftPro for the
sustainability analysis: such as tool support, FRS to allow
better impression of requirements' rating, and last but not least
a systematic methodology to analyse the sustainability of the
system under development.</p>
      <p>Also, we explored the viability and demonstrated the usability
and feasibility of SuSoftPro by conducting a case study from
the eHealth domain, based on a real-life project: a Skin Cancer
Information System to store patient health records.</p>
      <p>
        Future work: We are conducting an empirical assessment of
SuSoftPro. The evaluation methodology is designed to capture
the views of professional practice experts in sustainability
requirements through qualitative approach, using qualitative
methods [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. The data is collected via online questionnaire.
      </p>
      <p>Then, these data will be analysed using predefined themes such
as the usefulness of the framework and developed tool, and the
potential of adapting the framework and tool. Furthermore, we
are currently conducting two other case SuSoftPro studies from
education domain, having two different eLearning systems and
large number of participants in higher education institution
from two countries.</p>
      <p>ACKNOWLEDGEMENTS</p>
      <p>The first author is supported by a scholarship from Umm
Al-Qura University, Saudi Arabia.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>C.</given-names>
            <surname>Becker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Betz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Chitchyan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Duboc</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. M.</given-names>
            <surname>Easterbrook</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Penzenstadler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Seyff</surname>
          </string-name>
          , and
          <string-name>
            <given-names>C. C.</given-names>
            <surname>Venters</surname>
          </string-name>
          , “Requirements: The key to sustainability,
          <source>” IEEE Software</source>
          , vol.
          <volume>33</volume>
          , no.
          <issue>1</issue>
          , pp.
          <fpage>56</fpage>
          -
          <lpage>65</lpage>
          , Jan.
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>M.</given-names>
            <surname>Mahaux</surname>
          </string-name>
          , “
          <article-title>Could participation support sustainability in requirements engineering?</article-title>
          ”
          <source>in Proceedings of the 2nd International Workshop on Requirements Engineering for Sustainable Systems</source>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>A. D.</given-names>
            <surname>Alharthi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Spichkova</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Hamilton</surname>
          </string-name>
          , “
          <article-title>Sustainability profiling of long-living software systems</article-title>
          ,
          <source>” in Proceedings of 4th International Workshop on Quantitative Approaches to Software Quality</source>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4] S. de la Rosa de Sáa,
          <string-name>
            <given-names>M. A.</given-names>
            <surname>Gil</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>González-Rodríguez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. T.</given-names>
            <surname>López</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M. A.</given-names>
            <surname>Lubiano</surname>
          </string-name>
          , “
          <article-title>Fuzzy rating scale-based questionnaires and their statistical analysis</article-title>
          ,
          <source>” IEEE Transactions on Fuzzy Systems</source>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>D.</given-names>
            <surname>Mairiza</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Zowghi</surname>
          </string-name>
          , and
          <string-name>
            <given-names>V.</given-names>
            <surname>Gervasi</surname>
          </string-name>
          , “
          <string-name>
            <surname>Utilizing</surname>
            <given-names>TOPSIS</given-names>
          </string-name>
          :
          <article-title>A multi criteria decision analysis technique for non-functional requirements conflicts</article-title>
          ,” in Requirements Engineering - First
          <source>Asia Pacific Requirements Engineering Symposium</source>
          . Springer,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>A. D.</given-names>
            <surname>Alharthi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Spichkova</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Hamilton</surname>
          </string-name>
          , “
          <article-title>SuSoftPro: Sustainability profiling for software,” in 26th International Requirements Engineering Conference (RE)</article-title>
          . IEEE,
          <year>2018</year>
          , (in press).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>P.</given-names>
            <surname>Achimugu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Selamat</surname>
          </string-name>
          , and
          <string-name>
            <given-names>R.</given-names>
            <surname>Ibrahim</surname>
          </string-name>
          , “
          <article-title>Reprotizer: A fully implemented software requirements prioritization tool,”</article-title>
          <source>Trans. Computational Collective Intelligence</source>
          , vol.
          <volume>22</volume>
          , pp.
          <fpage>80</fpage>
          -
          <lpage>105</lpage>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>A.</given-names>
            <surname>Alharthi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Busch</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Smith</surname>
          </string-name>
          , “
          <article-title>A prototypical skin cancer information system</article-title>
          ,
          <source>” in 24th Australasian Conference on Information Systems (ACIS)</source>
          . RMIT University,
          <year>2013</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>11</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>M.</given-names>
            <surname>Behzadian</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. K.</given-names>
            <surname>Otaghsara</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Yazdani</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Ignatius</surname>
          </string-name>
          , “
          <article-title>A state-of the-art survey of TOPSIS applications,” Expert Systems with Applications</article-title>
          , vol.
          <volume>39</volume>
          , no.
          <issue>17</issue>
          , pp.
          <fpage>51</fpage>
          -
          <lpage>69</lpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>R. H.</given-names>
            <surname>Boyer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N. D.</given-names>
            <surname>Peterson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Arora</surname>
          </string-name>
          , and
          <string-name>
            <given-names>K.</given-names>
            <surname>Caldwell</surname>
          </string-name>
          , “
          <article-title>Five approaches to social sustainability and an integrated way forward</article-title>
          ,
          <source>” Sustainability</source>
          , vol.
          <volume>8</volume>
          , no.
          <issue>9</issue>
          , p.
          <fpage>878</fpage>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>M. Al</given-names>
            <surname>Hinai</surname>
          </string-name>
          and
          <string-name>
            <given-names>R.</given-names>
            <surname>Chitchyan</surname>
          </string-name>
          , “
          <article-title>Engineering requirements for social sustainability</article-title>
          ,”
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>A.</given-names>
            <surname>Chaparro</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Chaparro</surname>
          </string-name>
          , “
          <article-title>Applications of color in design for color-deficient users,” Ergonomics in Design</article-title>
          , vol.
          <volume>25</volume>
          , no.
          <issue>1</issue>
          , pp.
          <fpage>23</fpage>
          -
          <lpage>30</lpage>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>M.</given-names>
            <surname>Bovea</surname>
          </string-name>
          and
          <string-name>
            <given-names>V.</given-names>
            <surname>Pérez-Belis</surname>
          </string-name>
          ,
          <article-title>“A taxonomy of ecodesign tools for integrating environmental requirements into the product design process</article-title>
          ,
          <source>” Journal of Cleaner Production</source>
          , vol.
          <volume>20</volume>
          , no.
          <issue>1</issue>
          , pp.
          <fpage>61</fpage>
          -
          <lpage>71</lpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>J.</given-names>
            <surname>Porras</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Palacin-Silva</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Drögehorn</surname>
          </string-name>
          , and
          <string-name>
            <given-names>B.</given-names>
            <surname>Penzenstadler</surname>
          </string-name>
          , “
          <article-title>Developing a model for evaluation of sustainability perspectives and effects in ict projects</article-title>
          ,” in International conference on Sustainable, Ecological Engineering Design for Society (SEEDS),
          <year>September 2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>M.</given-names>
            <surname>Al Hinai</surname>
          </string-name>
          ,
          <article-title>“Quantification of social sustainability in software</article-title>
          ,” in 22nd International Requirements Engineering Conference (RE). IEEE,
          <year>2014</year>
          , pp.
          <fpage>456</fpage>
          -
          <lpage>460</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>R.</given-names>
            <surname>Chitchyan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Becker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Betz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Duboc</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Penzenstadler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Seyff</surname>
          </string-name>
          , and
          <string-name>
            <given-names>C. C.</given-names>
            <surname>Venters</surname>
          </string-name>
          , “
          <article-title>Sustainability design in requirements engineering: state of practice,”</article-title>
          <source>in Proceedings of the 38th International Conference on Software Engineering Companion. ACM</source>
          ,
          <year>2016</year>
          , pp.
          <fpage>533</fpage>
          -
          <lpage>542</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>J. M.</given-names>
            <surname>Carrillo-de-Gea</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Nicolás</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. L. F.</given-names>
            <surname>Alemán</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Toval</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Ebert</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Vizcaíno</surname>
          </string-name>
          , “
          <article-title>Requirements engineering tools: Capabilities, survey</article-title>
          and assessment,
          <source>” Information &amp; Software Technology</source>
          , vol.
          <volume>54</volume>
          , no.
          <issue>10</issue>
          , pp.
          <fpage>1142</fpage>
          -
          <lpage>1157</lpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>M. Q.</given-names>
            <surname>Patton</surname>
          </string-name>
          ,
          <article-title>Qualitative evaluation and research methods</article-title>
          .
          <source>SAGE</source>
          ,
          <year>2002</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>