<!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 Automatically Identifying Potential Sustainability Effects of Requirements</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Iris Groher</string-name>
          <email>iris.groher@jku.at</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Norbert Seyff</string-name>
          <email>norbert.seyff@fhnw.ch</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Tahira Iqbal</string-name>
          <email>iqbal@fortiss.org</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>FHNW</institution>
          ,
          <addr-line>Windisch, Switzerland</addr-line>
          ,
          <institution>University of Zurich</institution>
          ,
          <addr-line>Zurich</addr-line>
          ,
          <country country="CH">Switzerland</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Johannes Kepler University</institution>
          ,
          <addr-line>Linz</addr-line>
          ,
          <country country="AT">Austria</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>fortiss GmbH</institution>
          ,
          <addr-line>Munich</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>-Software developers are gradually becoming aware that their systems have effects on sustainability. The identification of potential effects software-intensive systems can have on different sustainability dimensions over time is yet in its infancy. Researchers are currently exploring approaches which strongly make use of expert knowledge to identify potential effects. In this work in progress paper, we are looking at the problem from a different angle: we report on the exploration of a machine learning-based approach to identify potential effects. Such an approach allows to save time and costs but increases the risk that potential effects are overseen. First results of applying the machine learning-based approach in the domain of home automation systems are promising, but also indicate that further research is needed before our approach can be applied in practice. Furthermore, we have learned that even providing the ground truth for training the algorithms is a challenging task.</p>
      </abstract>
      <kwd-group>
        <kwd>Sustainability</kwd>
        <kwd>Analysis</kwd>
        <kwd>Requirements</kwd>
        <kwd>Machine Learning</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>I. INTRODUCTION</title>
      <p>
        Software-intensive systems do not operate in isolation but in
complex socio-technical contexts. Therefore, they have an
impact on this context, manifesting itself in different dimensions
such as the environmental, economic, social, individual, and
technical dimension [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. As effects can occur over time, we
can also identify three different orders of effects [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. The
cumulative positive and negative effects a software-intensive
system has on its context define its sustainability.
      </p>
      <p>
        In previous research [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], we have learned that practitioners
are not aware of the fact that software-intensive systems have
an impact on sustainability and that raising awareness is an
essential step towards the development of sustainable
softwareintensive systems. Furthermore, the complexity of this matter
and the lack of adequate methods and tools supporting the
identification of potential effects are hurdles for practitioners
who are already aware of their responsibility to build
sustainable systems.
      </p>
      <p>
        Requirements are the key to sustainability [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], which
indicates that the identification of potential sustainability effects
needs to start before systems are actually built or when
      </p>
      <p>Copyright 2019 for this paper by its authors. Use permitted under Creative
Commons License Attribution 4.0 International (CC BY 4.0).
certain aspects of a system are modified in the context of
system evolution. This, in part, also makes the identification
of potential effects a hypothetical endeavour, which often
needs to be based on expert opinions rather than facts. Only
after development, when the system is used in its application
context, one can eventually validate its effects on the different
sustainability dimensions over time.</p>
      <p>
        Researchers have started to build methods and tools to
support the identification of sustainability effects [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
Although such approaches can be successfully applied to
identify potential sustainability effects, it appears that they
require a significant time investment of companies, which
might prevent their adoption.
      </p>
      <p>In this work in progress paper, we follow a current trend in
software and requirements engineering and propose the use of
Machine Learning (ML) for the early identification of potential
sustainability effects. In this paper, we present this idea in
more detail and also report on a first application experiment in
the home automation domain. Based on requirements for home
automation systems, we have identified potential sustainability
effects and have used these results as ground truth for training
our algorithms. Early results indicate that using ML for the
identification of sustainability effects is promising, which
motivates us to continue with this research.</p>
      <p>In Section 2 we discuss existing approaches for identifying
sustainability effects in requirements. In Section 3 we present
our ML-based approach and report on a first experiment we
conducted in Section 4. In Section 5 we conclude the paper
and present an outlook on next steps we plan.</p>
      <p>II. EXISTING SUSTAINABILITY EFFECT IDENTIFICATION</p>
      <p>APPROACHES AND TOOLS</p>
      <p>The work presented in this paper is motivated by research in
the field of requirements engineering, where researchers aim
at identifying potential sustainability effects.</p>
      <p>
        In previous work on tailoring requirements negotiation to
sustainability [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], an extension of the WinWin negotiation
model was proposed. This approach incorporates sustainability
so that the negotiation is used to identify potential effects of
requirements on sustainability. For requirements which might
have negative effects, alternative requirements options are
discussed to minimize these negative effects. This method
was applied in an exploratory industrial case study, where
it allowed practitioners to reflect on requirements and their
effects on sustainability.
      </p>
      <p>
        Recent work presents a question-based framework for
raising awareness of the potential effects of software systems on
sustainability [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. The Sustainability Awareness Framework
(SusAF) was used by students to carry out interviews for a
software system of their choice to identify potential effects of
these systems on sustainability and in particular even identify
potential chain of effects. Results from this feasibility study
indicate that SusAF stimulates the discussion about potential
effects of software systems on sustainably.
      </p>
      <p>
        Alharthi et al. [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] present the SuSoftPro tool, which supports
the analysis of the impact of requirements on different
sustainability dimensions via a Fuzzy Rating Scale method. This
toolsupported approach allows for different visualization option of
the results (e.g., a bar graph that illustrates the sustainability
level).
      </p>
      <p>We conclude that researchers have identified the need
for identifying sustainability effects and that first promising
methods and even tool-supported approaches are appearing.
However, all presented methods strongly depend on human
involvement and might require time-intensive discussions, the
involvement of experts or a large number of people to derive
results. The quality of the produced results might further vary
a lot depending on different factors such as the complexity of
the domain and the level of expertise of the people involved.
Nevertheless, bespoke methods can raise awareness and can
help, at least in part, to improve the sustainability of
softwareintensive systems.</p>
      <p>III. MACHINE LEARNING-BASED EFFECT IDENTIFICATION</p>
      <p>The goal of our ongoing research is to automate the
identification of potential sustainability effects by analysing the
requirements of a software-intensive system. In contrast to
existing methods in place, we expect that such an approach
will result in the significant reduction of the effort needed
for the analysis. However, we also see the risks that such an
approach might result in overlooking potential effects.</p>
      <sec id="sec-1-1">
        <title>A. ML in Software and Requirements Engineering</title>
        <p>
          To achieve this goal, we follow a recent trend in software
and requirements engineering and explore the application of
ML [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. ML has already been successfully used to
classify software requirements into functional and non-functional
requirements [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. The analysis of a large number of
user feedback from multiple sources such as the app store
and Twitter has been automated by applying ML [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ] [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ].
This analysis helps to identify useful information such as bug
reports and feature requests to support software evolution. For
validating requirements, automated analysis of requirement
traceability with the help of natural language processing and
ML has been studied [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ] [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ]. ML has also been applied
in requirements management such as visualizing requirements
on different levels of granularity and prioritizing requirements
[
          <xref ref-type="bibr" rid="ref16">16</xref>
          ] [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ].
        </p>
      </sec>
      <sec id="sec-1-2">
        <title>B. ML Application Overview</title>
        <p>
          To automatically identify the impact of requirements on
sustainability we follow the ML workflow [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ], as shown in
Fig. 1.
        </p>
        <p>The first key step is data preprocessing that helps to avoid
data incompleteness and inconsistency issues. This data is
used as an input for the ML algorithm, which means that the
ML algorithm learns from existing data. On the basis of this
learning, a learning model is produced as output, which can
be used to make predictions on a different dataset than the one
used for training. The learning model can be evaluated based
on its performance. For measuring the performance, we use
well-known ML parameters such as precision, recall, accuracy,
and F-score.</p>
        <p>In the next section, we will describe how we have performed
the above discussed steps in our experiment.</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>IV. A FIRST EXPERIMENT</title>
      <p>We performed a first experiment in the domain of home
automation systems to evaluate our ML-based approach. In
the next subsection, we describe the setup of our experiment
and in the subsequent subsection we present our preliminary
results.</p>
      <sec id="sec-2-1">
        <title>A. Setup</title>
        <p>
          Data: The dataset used for training and evaluating our
MLbased approach is comprised of publicly available smart home
requirements1. The requirements were collected as part of
research on crowd-RE [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ].
        </p>
        <p>In a first step, three annotators manually classified 200
randomly selected requirements from the total set of
available requirements (around 2900). All three annotators had
proficient knowledge and expertise for sustainable systems in
software engineering. For each requirement, each annotator
independently marked which sustainability dimension(s) it had
an effect on. To support this classification, a literature review
has been performed on sustainability dimensions and created
a classification guideline based on the results of this analysis.
The guideline contained for each dimension a set of influence
factors and for each factor a description, rational, example
requirements, and literature references for further reading.
Table I shows an example influence factor in the environmental
dimension.</p>
        <p>The annotators used the guideline as a reference during the
manual classification of the 200 smart home requirements.
Each requirement was independently classified according to
its influence on the five dimensions of software sustainability
as positive, negative, or neutral. The plus sign (+) was assigned
for positive influence, a minus sign (-) for negative influence,
and no sign for indicating no influence as shown in Table II.
The ratings were merged and cases in which the researchers
did not agree were discussed until consensus was reached.</p>
        <p>1Smarthome Crowd Requirements Dataset,
https://crowdre.github.io/murukannaiah-smarthome-requirements-dataset/
Dimension
Factor
Description
Influence/Rational
Example</p>
        <p>Pre-processing: We applied natural language processing
techniques on our data before applying the different ML
algorithms. First, we applied text tokenization on each requirement.
Then we eliminated all stop words and converted the text into
small characters. We applied stemming as our next step. As
the last step, we converted pre-processed text as a vector space
model using Term Frequency-Inverse Document Frequency
(TF-ID or TF-IDF) as a weighting scheme:
tf idf (t; d) = tf (t; d) idf
(1)</p>
        <p>
          Here t is a term in a vector and d is a requirement in a
collection of requirements [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ].
        </p>
        <p>
          Classification: For the automated classification of
sustainability requirements and their dimensions, we trained our
model using the annotated requirements dataset. We
implemented Nave Bayes (NB), k-Nearest Neighbor (KNN),
Decision trees (DT), Support Vector Machine (SVM), Logistic
regression (LR), and Neural Network (NN) algorithms and
also trained our classifier with and without stemming the data,
as discussed in [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]. The results were quite similar with a minor
difference and we used stemmed data for final analysis. We
used tenfold cross-validation for evaluating our results.
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>C. Results</title>
        <p>The results for six different classifiers from our experiments
are shown in Table III. For choosing the best classifier, we
evaluated the performance of all these classifiers on the
basis of commonly used ML metrics i.e., accuracy, precision,
recall, and F1-score. These metrics can be calculated using
the following formulae:</p>
        <p>Accuracy = T P + T N=T P + F P + F N + T N
P recision = T P=(T P + F P )
(2)
(3)</p>
        <p>Recall = T P=(T P + F N )
F 1
score = P recision=Recall
(4)
(5)</p>
        <p>Here, TP (True Positive) is the number of requirements
correctly classified as belonging to a category. TN (True
Negative) is the number of requirements that are correctly
classified as not belonging to a category. FP (False Positive) is
the number of requirements incorrectly classified as belonging
to a category, and FN (False Negative) is the number of
requirements that are incorrectly classified as not belonging
to a category.</p>
        <p>In simple words, accuracy is the ratio of correctly classified
data over total data. This helps to predict the model
performance whereas high accuracy results in a better performance
of the model. However, data can be asymmetric and thus
parameters other than accuracy need to be evaluated. The
precision metric refers to the ratio of correctly predicted
positive values to the total number of predicted positive values.
On the other hand, recall is the ratio of total predicted positive
values to the actual number of positive values. It is not possible
to maximize both recall and precision metrics at the same time,
as one comes at the cost of another. To consider both, F1-score
is used which is the harmonic mean of precision and recall.</p>
        <p>The highest accuracy and F1-score decide which algorithm
is the best among others. We achieved the highest accuracy
with DT classifier (70% precision) followed by SVM (69%
precision). Our dataset was not balanced, meaning that the
five different sustainability dimensions were not equally
represented in the dataset (see Fig. 2). The economic,
environmental, and social dimensions were almost equally
represented. The individual dimension had high occurrences and
the technical dimension was almost inexistent. To overcome
this problem, we used the weighting technique by assigning
more weight to fewer data. After applying this setting, we
achieved the highest accuracy for SVM (75%), as shown in
column SVM (b) of Table III. Recall and precision are 63%
and 57% respectively, which is acceptable according to our
accuracy. We also calculated the F1-scores, and the highest
value was achieved with SVM (60%).</p>
        <p>The results from this initial experiment can be improved
further as we observed some issues that are impacting our
results. The structure of our dataset varied with respect to
the length of the textual requirements. For example, one
requirement consisted of 20 words, and another one consisted
of 200 words. Due to the significant difference regarding their
length, our ML classifier features were sparse, which might
have lead to an underfitted model.</p>
        <p>Moreover, our negative and positive influence values on the
sustainability dimensions were also not equally distributed.
Our data only contained 12 requirements with negative
influence, the rest were positive influences.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>V. CONCLUSION AND NEXT STEPS</title>
      <p>The goal of our ongoing research is the automation of the
identification of requirements, which potentially have effects
on the sustainability of a software-intensive system.</p>
      <p>In this paper, we present the application of a state-of-the-art
ML approach to support effect identification. Our first results
indicate that ML can be successfully used for the identification
of potential sustainability effects. However, we have learned
that the results from our first experiment can be improved
further. This starts with the dataset. The current dataset can
be improved to generate a more suitable learning model for
the classifiers.</p>
      <p>As a next step, we plan to increase the size of our dataset.
We have already designed a web-based solution where experts
can update the categorized requirements and add additional
requirements. This web-based tool will help us to improve
our labeling and support us in getting more data. It will also
allow us to provide a more balanced dataset.</p>
      <p>Our current results indicate that there is the risk of
overlooking requirements which have potential effects. As a next step,
we plan to focus on optimizing recall to minimize this risk. We
envision that our approach could be used to complement
existing methods. Instead of discussing each requirement manually,
our approach could provide a list of relevant requirements,
which should be discussed further by human stakeholders.
High recall might result in lower precision, which means that
human stakeholders are confronted with a larger number of
false positives. However, we expect that providing a reduced
set of requirements for discussion will enable practitioners to
save time compared to a full manual analysis.</p>
      <p>Similar to other work in this field, we have also experienced
that manually identifying potential effects can lead to different
opinions amongst the annotators. Although, the three
annotators were able to agree on a ground truth used for training our
classifier, we would like to highlight that our results might
reflect a rather subjective viewpoint of the annotators.</p>
      <p>
        Overall, we would like to explore how we can integrate our
work into existing studies for requirements classification. In
particular, we envision to use our approach within planned
work on crowd-focused semi-automated requirements
engineering for evolution towards sustainability [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ]. This would
also allow us to use our approach for other domains than
smart homes, which might also result in datasets with different
characteristics allowing us to further improve the classification
results.
      </p>
    </sec>
    <sec id="sec-4">
      <title>ACKNOWLEDGEMENT</title>
      <p>The authors would like to thank Robert O¨rdo¨ g for
implementing the tool support for our ML-based approach and
for conducting the experiment presented in this paper. This
research was partially funded by the European Unions
Horizon 2020 research and innovation program under the Marie
Skodowska-Curie grant agreement No. 674875.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <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>
            <surname>Colin</surname>
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Venters</surname>
          </string-name>
          . Requirements:
          <article-title>The key to sustainability</article-title>
          .
          <source>IEEE Software</source>
          ,
          <volume>33</volume>
          (
          <issue>1</issue>
          ):
          <fpage>56</fpage>
          -
          <lpage>65</lpage>
          ,
          <year>Jan 2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Christoph</given-names>
            <surname>Becker</surname>
          </string-name>
          , Ruzanna Chitchyan, Leticia Duboc, Steve Easterbrook, Birgit Penzenstadler, Norbert Seyff, and
          <string-name>
            <surname>Colin</surname>
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Venters</surname>
          </string-name>
          .
          <article-title>Sustainability design and software: The karlskrona manifesto</article-title>
          .
          <source>In Proceedings of the 37th International Conference on Software Engineering - Volume 2, ICSE '15</source>
          , pages
          <fpage>467</fpage>
          -
          <lpage>476</lpage>
          , Piscataway, NJ, USA,
          <year>2015</year>
          . IEEE Press.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <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="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>Ruzanna</given-names>
            <surname>Chitchyan</surname>
          </string-name>
          , Christoph Becker, Stefanie Betz, Leticia Duboc, Birgit Penzenstadler, Norbert Seyff, and
          <string-name>
            <surname>Colin</surname>
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <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, ICSE '16</source>
          , pages
          <fpage>533</fpage>
          -
          <lpage>542</lpage>
          , New York, NY, USA,
          <year>2016</year>
          . ACM.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>Norbert</given-names>
            <surname>Seyff</surname>
          </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="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>Leticia</given-names>
            <surname>Duboc</surname>
          </string-name>
          , Stefanie Betz, Birgit Penzenstadler, Sedef Akinli Kocak, Ruzanna Chitchyan, Ola Leifler, Jari Porras, Norbert Seyff, and Colin C Venters.
          <article-title>Do we really know what we are building? raising awareness of potential sustainability effects of software systems in requirements engineering</article-title>
          .
          <source>In 27th IEEE International Requirements Engineering Conference</source>
          ,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Ahmed</surname>
            <given-names>D</given-names>
          </string-name>
          <string-name>
            <surname>Alharthi</surname>
            ,
            <given-names>Maria</given-names>
          </string-name>
          <string-name>
            <surname>Spichkova</surname>
            , and
            <given-names>Margaret</given-names>
          </string-name>
          <string-name>
            <surname>Hamilton</surname>
          </string-name>
          . Susoftpro:
          <article-title>Sustainability profiling for software</article-title>
          .
          <source>In 2018 IEEE 26th International Requirements Engineering Conference (RE)</source>
          , pages
          <fpage>500</fpage>
          -
          <lpage>501</lpage>
          . IEEE,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>T.</given-names>
            <surname>Iqbal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Elahidoost</surname>
          </string-name>
          , and
          <string-name>
            <given-names>L.</given-names>
            <surname>Lcio</surname>
          </string-name>
          .
          <article-title>A bird's eye view on requirements engineering and machine learning</article-title>
          .
          <source>In 2018 25th Asia-Pacific Software Engineering Conference (APSEC)</source>
          , pages
          <fpage>11</fpage>
          -
          <lpage>20</lpage>
          ,
          <year>Dec 2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>William</given-names>
            <surname>Martin</surname>
          </string-name>
          ,
          <string-name>
            <surname>Federica Sarro</surname>
          </string-name>
          , Yue Jia, Yuanyuan Zhang, and
          <string-name>
            <given-names>Mark</given-names>
            <surname>Harman</surname>
          </string-name>
          .
          <article-title>A survey of app store analysis for software engineering</article-title>
          .
          <source>IEEE transactions on software engineering</source>
          ,
          <volume>43</volume>
          (
          <issue>9</issue>
          ):
          <fpage>817</fpage>
          -
          <lpage>847</lpage>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Zijad</surname>
            <given-names>Kurtanovic´</given-names>
          </string-name>
          and
          <string-name>
            <given-names>Walid</given-names>
            <surname>Maalej</surname>
          </string-name>
          .
          <article-title>Automatically classifying functional and non-functional requirements using supervised machine learning</article-title>
          .
          <source>In 2017 IEEE 25th International Requirements Engineering Conference (RE)</source>
          , pages
          <fpage>490</fpage>
          -
          <lpage>495</lpage>
          . IEEE,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Douglas</surname>
            <given-names>S Lange.</given-names>
          </string-name>
          <article-title>Text classification and machine learning support for requirements analysis using blogs</article-title>
          .
          <source>In Monterey Workshop</source>
          , pages
          <fpage>182</fpage>
          -
          <lpage>195</lpage>
          . Springer,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>Grant</given-names>
            <surname>Williams</surname>
          </string-name>
          and
          <string-name>
            <given-names>Anas</given-names>
            <surname>Mahmoud</surname>
          </string-name>
          .
          <article-title>Mining twitter feeds for software user requirements</article-title>
          .
          <source>In 2017 IEEE 25th International Requirements Engineering Conference (RE)</source>
          , pages
          <fpage>1</fpage>
          -
          <lpage>10</lpage>
          . IEEE,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>Walid</given-names>
            <surname>Maalej</surname>
          </string-name>
          and
          <string-name>
            <given-names>Hadeer</given-names>
            <surname>Nabil</surname>
          </string-name>
          .
          <article-title>Bug report, feature request, or simply praise? on automatically classifying app reviews</article-title>
          .
          <source>In 2015 IEEE 23rd international requirements engineering conference (RE)</source>
          , pages
          <fpage>116</fpage>
          -
          <lpage>125</lpage>
          . IEEE,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>Sandeep</surname>
            <given-names>Reddivari</given-names>
          </string-name>
          , Zhangji Chen, and
          <string-name>
            <given-names>Nan</given-names>
            <surname>Niu</surname>
          </string-name>
          .
          <article-title>Recvisu: A tool for clustering-based visual exploration of requirements</article-title>
          .
          <source>In 2012 20th IEEE International Requirements Engineering Conference (RE)</source>
          , pages
          <fpage>327</fpage>
          -
          <lpage>328</lpage>
          . IEEE,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>Hakim</given-names>
            <surname>Sultanov</surname>
          </string-name>
          and
          <article-title>Jane Huffman Hayes</article-title>
          .
          <article-title>Application of reinforcement learning to requirements engineering: requirements tracing</article-title>
          .
          <source>In 2013 21st IEEE International Requirements Engineering Conference (RE)</source>
          , pages
          <fpage>52</fpage>
          -
          <lpage>61</lpage>
          . IEEE,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>Vincenzo</given-names>
            <surname>Gervasi</surname>
          </string-name>
          and
          <string-name>
            <given-names>Didar</given-names>
            <surname>Zowghi</surname>
          </string-name>
          .
          <article-title>Mining requirements links</article-title>
          .
          <source>In International Working Conference on Requirements Engineering: Foundation for Software Quality</source>
          , pages
          <fpage>196</fpage>
          -
          <lpage>201</lpage>
          . Springer,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <surname>Paolo</surname>
            <given-names>Avesani</given-names>
          </string-name>
          , Anna Perini, Alberto Siena, and
          <string-name>
            <given-names>Angelo</given-names>
            <surname>Susi</surname>
          </string-name>
          .
          <article-title>Goals at risk? machine learning at support of early assessment</article-title>
          .
          <source>In 2015 IEEE 23rd International Requirements Engineering Conference (RE)</source>
          , pages
          <fpage>252</fpage>
          -
          <lpage>255</lpage>
          . IEEE,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <surname>Moussa</surname>
            <given-names>Amrani</given-names>
          </string-name>
          , Levi Lu´cio, and
          <article-title>Adrien Bibal</article-title>
          .
          <article-title>Ml+ fv=? a survey on the application of machine learning to formal verification</article-title>
          .
          <source>arxiv: 1806.03600</source>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <surname>Pradeep</surname>
            <given-names>K Murukannaiah</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nirav Ajmeri</surname>
          </string-name>
          , and Munindar P Singh.
          <article-title>Acquiring creative requirements from the crowd: Understanding the influences of personality and creative potential in crowd re</article-title>
          .
          <source>In 2016 IEEE 24th International Requirements Engineering Conference (RE)</source>
          , pages
          <fpage>176</fpage>
          -
          <lpage>185</lpage>
          . IEEE,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>Juan</given-names>
            <surname>Ramos</surname>
          </string-name>
          et al.
          <article-title>Using tf-idf to determine word relevance in document queries</article-title>
          .
          <source>In Proceedings of the first instructional conference on machine learning</source>
          , volume
          <volume>242</volume>
          , pages
          <fpage>133</fpage>
          -
          <lpage>142</lpage>
          . Piscataway, NJ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <surname>Norbert</surname>
            <given-names>Seyff</given-names>
          </string-name>
          , Stefanie Betz, Iris Groher, Melanie Stade, Ruzanna Chitchyan, Let´ıcia Duboc, Birgit Penzenstadler, Colin Venters, and
          <string-name>
            <given-names>Christoph</given-names>
            <surname>Becker</surname>
          </string-name>
          .
          <article-title>Crowd-focused semi-automated requirements engineering for evolution towards sustainability</article-title>
          .
          <source>In 2018 IEEE 26th International Requirements Engineering Conference (RE)</source>
          , pages
          <fpage>370</fpage>
          -
          <lpage>375</lpage>
          . IEEE,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>