<!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>What About Catalogs of Non-Functional Requirements?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Rainara M. Carvalho, Rossana M. C. Andrade, Valeria Lelli</string-name>
          <email>frainaracarvalho,rossana,valerialellig@great.ufc.br</email>
          <email>valerialellig@great.ufc.br</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Erika Gonzaga Silva</string-name>
          <email>erikagonzaga@alu.ufc.br</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kathia Marcal de Oliveira</string-name>
          <email>kathia@univ-valenciennes.fr</email>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>In: M. Sabetzadeh, A. Vogelsang, S. Abualhaija, M. Borg, F. Dalpiaz, M. Daneva, N. Fernandez, X. Franch, D. Fucci, V. Gervasi,</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>E. Groen</institution>
          ,
          <addr-line>R. Guizzardi, A. Herrmann, J. Horko , L. Mich</addr-line>
          ,
          <institution>A. Perini, A. Susi (eds.): Joint Proceedings of REFSQ-2020 Workshops, Doctoral Symposium, Live Studies Track, and Poster Track</institution>
          ,
          <addr-line>Pisa, Italy, 24-03-2020, published at http://ceur-ws.org</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Federal University of Ceara</institution>
          ,
          <addr-line>Quixada</addr-line>
          ,
          <country country="BR">Brazil</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Group of Computer Network, Software Engineering and Systems, Federal University of Ceara</institution>
          ,
          <addr-line>Fortaleza</addr-line>
          ,
          <country country="BR">Brazil</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Universite Polytechnique Hauts-de-France</institution>
          ,
          <addr-line>Valenciennes, LAMIH UMR CNRS 8201</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Researcher scholarship (DT Level 2) sponsored by CNPq (Brazil)</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>[Context and Motivation] Satisfying Non-Functional Requirements
(NFRs) in software development is challenging. There are many types
of NFRs and each one requires specialized knowledge. Moreover, they
can be correlated, which means that achieving one NFR can impact the
achievement of another, positively or negatively. A common solution in
the literature for helping developers to deal with these issues at the
beginning of the development is the usage of NFR catalogs. Then, there
is a need to know the current NFR catalogs to both support software
development and to identify their challenges. [Question/Problem]
However, the literature lacks a synthesized study of existing catalogs
to help developers and researchers. Then, this work aims to identify
what catalogs have been proposed in the literature and how they have
been represented, de ned and evaluated. [Principal ideas/results]
To achieve our goal, we performed a literature review through a
systematic mapping study. We then identi ed 102 catalogs supporting
86 NFRs. They are mostly represented by Softgoals Interdependency
Graphs and are built through literature review. [Contribution] Our
results provide not only an overview of the area to guide researchers
and practitioners who wish to build their catalogs, but also can help
developers to reuse the knowledge presented in these catalogs.
Copyright c 2020 for this paper by its authors. Use permitted under Creative Commons License Attribution 4.0 International (CC
BY 4.0).</p>
    </sec>
    <sec id="sec-2">
      <title>Introduction</title>
      <p>
        Dealing with NFRs that are quality characteristics (e.g. Usability, Security) during development brings several
issues to be overcome. One is that there are many types of them, and each requires specialized knowledge on
how to support it in software development. This knowledge is not always e ortlessly available for developers
especially for those who have no experience with NFRs [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Also, NFRs can interact with each other [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], which
means that achieving one NFR can impact the achievement of another. This impact can be either positive or
negative [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. When negative, this impact is called con ict or negative correlation.
      </p>
      <p>
        A common solution in the literature for helping developers to ful ll NFRs is the usage of NFR catalogs [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]
[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. A catalog is a body of knowledge that was accumulated from previous experience. They are known for
improving speci cations since it allows the reuse of requirements. However, several catalogs are scattered in
online libraries of scienti c studies [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], making their reuse more challenging. The requirements community
lacks a synthesized study about catalogs in order to help developers identifying strategies and con icts and to
de ne trends and future research. Thus, this work aims to give an overview about the existing NFR catalogs.
      </p>
      <p>
        To do this, we conducted a systematic mapping (SM) study [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], since it is a research method that
provides an overview of an area and allows to discover research gaps and possible trends. Based on the SM
study, this paper presents a set of NFRs catalogs that a developer can consult while dealing with NFRs at the
beginning of the development. Additionally, we provide a synthesis of research opportunities in this area.
2
      </p>
    </sec>
    <sec id="sec-3">
      <title>Background and Related Work</title>
      <p>
        According to the NFR Framework [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], there can be three types of NFR catalogs: (i) catalog of subcharacteristics;
(ii) catalog of methods (i.e., strategies to support the quality characteristic in a system) and (iii) catalog of
correlations.
      </p>
      <p>Subcharacteristics represent a more speci c knowledge about a NFR. For example, Security can be
decomposed into three subcharacteristics, Con dentiality, Integrity and Availability. Methods represent development
solutions intended to satisfy NFRs in a system. A method can be of any type, such as a function or some
component in architecture, a design constraint or a design guideline. These methods can even be re ned into
more speci c ones. Correlations represent the interactions in NFRs, which can be de ned in several levels: a)
correlation between top-level NFRs, e.g., Usability hurts Security; b) correlation between subcharacteristics; c)
correlation between method and top-level NFR; and d) correlation between method and subcharacteristic.</p>
      <p>
        The literature has several NFRs catalogs. For example, there is a catalog for Security, Performance and
Accuracy in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], Usability in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], Transparency in [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], Privacy in [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. However, we did not nd a work that
synthesizes the existing catalogs through a systematic study and organizes them to help researchers and developers.
Therefore, we believe that a study summarizing and classifying the knowledge about catalogs of NFRs could be
useful for researchers and developers to both understand the current state-of-the-art of this area and improve
their practices.
3
      </p>
    </sec>
    <sec id="sec-4">
      <title>Research Method</title>
      <p>3.1</p>
      <sec id="sec-4-1">
        <title>Planning</title>
        <p>
          To perform our SM study, we followed a process with three main phases proposed by [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] for systematic studies:
(i) Planning; (ii) Conducting, and (iii) Reporting, described as follows.
        </p>
        <p>The aim of the planning phase is the de nition of a protocol. This document is usually composed of the following
data: research goal, questions, databases, selection criteria, screening process and extraction strategy, explained
as follows1.
3.1.1</p>
      </sec>
      <sec id="sec-4-2">
        <title>Research Goal and Questions.</title>
        <p>The goal of this SM is to provide an overview of the literature regarding NFRs catalogs. To achieve this goal, we
investigate the following research questions (RQs):</p>
      </sec>
      <sec id="sec-4-3">
        <title>RQ1. What NFR catalogs have been proposed in the literature?</title>
      </sec>
      <sec id="sec-4-4">
        <title>RQ2. How is the information represented in the NFR catalogs?</title>
        <p>1Detailed information is available in https://github.com/great-ufc/SM-NFRsCatalogs/blob/master/ProtocolandResults.pdf</p>
        <p>
          The strategy PICO (Population, Intervention, Comparison, and Outcomes) suggested by [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ] was considered to
identify keywords and thus formulate the search string from research questions. To evaluate its quality, we
selected three control papers that we knew before the execution of the database search [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ] [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ] [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ], then we
de ned the nal string only if it brought these papers. Table 1 presents it.
        </p>
        <p>As databases, Web of Science and Scopus were chosen, since they have good coverage and stability. Also,
Scopus cover other bases, such as IEEE. We also added one speci c database from the requirements area:
Workshop on Requirements Engineering (WER). We have chosen it for three reasons: it represents an important
event in the area where researchers usually publish NFRs catalogs, publications from there are not all indexed
in the databases we previously choose, and it provides a search engine of its own, making the search for catalogs
easier.
3.1.3</p>
      </sec>
      <sec id="sec-4-5">
        <title>Selection Criteria.</title>
        <p>We have de ned the following inclusion (IC) and exclusion (EC) criteria to select the most suitable studies: IC1
- the study presents a NFR catalog; EC1 - the study is not written in English; EC2 - the study is not from
Computer Science or Engineering related areas; and EC3 - the paper does not present a NFR catalog.
3.1.4</p>
      </sec>
      <sec id="sec-4-6">
        <title>Data Extraction. 3.1.5</title>
      </sec>
      <sec id="sec-4-7">
        <title>Data Analysis.</title>
        <p>An extraction form was elaborated to be used for each selected paper in this phase. This form is organized into
four parts. The rst one is related to data from the accepted papers and the other parts are related to data to
answer the each RQ (RQ1, RQ2, RQ3, RQ4).</p>
        <p>
          The extracted data was analyzed according to the type of data extracted. For RQ1 and RQ2, a quantitative
analysis was performed due to the nature of the data collected, which were numerical in a nominal scale. A
measure of central tendency (mode) and a measure of dispersion (frequency) were used to present the results.
Regarding RQ3 and RQ4, the data extracted from the literature provided a signi cant amount of textual
information. Therefore, we decided to use a qualitative method called Content Analysis (CA) to analyze the data
and, consequently, answer more appropriately the questions [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ].
3.2
        </p>
      </sec>
      <sec id="sec-4-8">
        <title>Conducting</title>
        <p>This phase was performed in ve steps, described as follows.
3.2.1</p>
      </sec>
      <sec id="sec-4-9">
        <title>Database Search.</title>
        <p>This step is about applying the search string (see Table 1) into the search machines of the libraries (Scopus and
Web of Science). To select the most suitable set of papers after applying the search string, a screening step
was performed using the following ve lters: (1) Applying EC1 and EC 2 in the found studies; (2) Excluding
duplicate studies; (3) Applying the exclusion criteria in the abstract and title reading; (4) Applying the exclusion
criteria in the introduction and conclusion reading, also apply the exclusion criteria by checking if there is an
image of a catalog in the study (e.g., graph, table); and (5) Applying the exclusion criteria in the entire paper
reading.</p>
        <p>The lter 1 was performed in the own search machines (Web of Science and Scopus) whereas the other lters
(2, 3, 4 and 5) were performed with supporting of Parsif.al tool2. Filters 3, 4 and 5 were executed by peers
2Free online collaborative tool for systematic reviews: https://parsif.
one student and one expert in NFRs catalog. First, a student performed the lter alone. Then, an expert who
has been working with NFRs catalogs reviewed only excluded papers. For example, if a student had excluded a
paper by reading the abstract and title, the expert should review them to check whether he-she agrees with the
exclusion. If not, the paper would be included in the study again.
3.2.2</p>
      </sec>
      <sec id="sec-4-10">
        <title>Snowballing.</title>
        <p>We have used the backward snowballing procedures to complement the set of papers found by the database
search. The backward procedure consists of checking the references list of a set of papers. In our case, the set
of papers were the ones selected in the databases searches. We adapted the procedure from [?] and [?], which
consisted of four lters. These lters are not totally similar to the lters we used earlier since the selection
through backward snowballing is slightly di erent. First, we started by manually reviewing all references from
each accepted paper from databases searches. Then, for each reference we applied the following lters: (1)
Applying all exclusion criteria in the reference. In this case, we had to be more speci c since we were reading
only titles, authors, venue and year. Thus, we accepted papers who presented any keyword from our search
string; (2) Applying all exclusion criteria in the abstract reading; (3) Applying the exclusion criteria in the most
relevant part of the papers (introduction, conclusion, and images of catalogs); and (4) Applying the exclusion
criteria in the entire paper reading.
3.2.3</p>
      </sec>
      <sec id="sec-4-11">
        <title>WER Search.</title>
        <p>WER exists since 1998 and has been an advance for the Ibero-American community. This workshop provides a
Google search engine3 that explores papers in all WER editions. Therefore, we applied the same search string
from Table 1 on it and the same lters for the databases searches.
3.2.4</p>
      </sec>
      <sec id="sec-4-12">
        <title>Data Extraction</title>
        <p>After performed all searches, the data extraction took place. In this way, rst, the extraction of data was done
in the papers found in the electronic databases. Then the extraction was done in the papers of snowballing and,
nally, the extraction was carried out in the papers from the workshop.</p>
        <p>Regarding to the papers obtained by the databases, the same student who performed the lters during the
ltering phase also performed the data extraction. Each extraction was reviewed by the expert. The extractions
of the papers obtained by the snowballing and the workshop were made by the expert and reviewed by the
student.</p>
        <p>During extraction, the form was updated to include a data not considered during planning: \type of
correlation". Through one of the obtained papers, it was possible to note that the correlations can appear between
NFRs (e.g., Usability and Performance), which is called INTER-NFRs, or within a same requirement (e.g.,
Performance subcharacteristics con ict with one another), called INTRA-NFR. Thus, all papers that had already
been extracted were reviewed again to extract this speci c data.
3.2.5</p>
      </sec>
      <sec id="sec-4-13">
        <title>Data Analysis</title>
        <p>
          This phase was about analyzing the extracted data. RQ1 and RQ2 were indeed analyzed with the measures
Mode and Frequency. RQ3 and RQ4 were also analyzed using quantitative measures, but they were also analyzed
through a qualitative method, Content Analysis [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. The main procedure is this method is the data coding,
which means extracting and relating codes from raw data through inspection. Codes are conceptual names that
represent the understanding of the researcher about a text. A set of codes can be grouped to form a category,
which is a higher-level concept. Then, each extracted data from RQ3 and RQ4 were carefully read and coded.
The, these codes were grouped to the similar ones into categories4.
4
        </p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Results</title>
      <p>This systematic study obtained 53 papers (38 from databases and 15 from snowballing). The key results from
the extraction and analysis of these papers can be viewed in Figure 1, which presents an overview for each RQ.</p>
      <p>
        Answering RQ1, 102 catalogs were obtained. We realized that they cannot be classi ed as mutually exclusive
in three types of catalogs, as previously proposed by [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Then, we extended the classi cation of [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] to: T1 {
3http://wer.inf.puc-rio.br/index.html
4The MAXQDA12 tool was used to support CA method - https://www.maxqda.com/
      </p>
      <p>Subcharacteristics, T2 - Subcharacteristics and strategies, T3 - Subcharacteristics, Strategies and Correlations,
T4 { Strategies, T5 - Strategies and Correlations, T6 { Correlations and T7 - Subcharacteristics and correlations.</p>
      <p>Initially it was expected that the catalogs could be for a speci c area, but with this study, we realized that
they can be proposed to particular areas, domains or artifacts. These di erent views are named as the \focus"
of the catalog.</p>
      <p>We also analyzed the NFRs supported by these catalogs. In total, 86 di erent NFRs were extracted.
Performance was the most cited (34), followed by Security (29), Usability (23) and Reliability (14). Regarding
subcharacteristics and methods, we found out 1269 and 1113, respectively.</p>
      <p>Regarding correlations, this SM study found 473 positive and 395 negative correlations in total. They can
occur not only between NFRs but also within the same NFR because their subcharacteristics or strategies may
con ict with one another. In this way, a classi cation of correlation types was found out: INTER-NFRs and
INTRA-NFR.</p>
      <p>This last nding allowed us to establish a research opportunity related to the investigation of con icting
(positive or negative) correlations. For example, when a catalog states two NFRs is con icting, and another
catalog states they are cooperating.</p>
      <p>Besides, this SM study found out that there are six levels of correlation. This level varies from the most
generic, which are correlations directly between NFRs, to more speci c levels, which are correlations between
strategies and strategies and characteristics.</p>
      <p>The identi ed catalogs are represented in eight di erent ways (answering RQ2 ): SIG (including SIG
adaptations), matrices, i* notation, tables, hierarchical structures, list, template, and pattern. With this information,
we established a second research opportunity related to the catalog's representation. Future research could
investigate these representations in a way that could indicate which would be the most appropriate to deal with
each knowledge of a catalog of NFRs: subcharacteristics, strategies and correlations.</p>
      <p>Although there are catalogs de ned by the authors themselves based on their experience, this study realized
that the de nition of a catalog can be done in two steps (answering RQ3 ). First, it is necessary to collect
the information, and then it is necessary to analyze this information to arrive at a more organized knowledge.
Concerning the collection, there are six external sources by which the catalog creator can search for
information: literature, existing catalogs, existing systems, experts, stakeholders and architects/developers. Also, there
are seven techniques to extract the information from these sources: bibliographic review, systematic review,
interview, questionnaire, questions patterns, goal-question-operationalization and measurement. Finally, there
are ve techniques to analyze data: Collaboration Process with researchers, Consensus Meeting, Clustering
Techniques, Content Analysis and a Technique based on Personal Construct Theory.</p>
      <p>Therefore, a third opportunity is related to the de nition of a complete catalog. Although some papers
explain their ways of constructing the proposed catalogs, a generic framework or process that provides a detailed
guideline to create NFRs catalog was not found.</p>
      <p>The last ndings were regarding the evaluation of a catalog (answering RQ4 ). Six evaluation approaches
were found out: proof of concept, case study, survey, questionnaire, relative validity and controlled experiment.
Seven evaluation purposes: designing a speci c system considering a NFR; redesigning an existing system to
show improvement with the use of the catalog; building a new model, often reusing knowledge from the existing
catalog; remodeling an existing catalog; arguing about the e ectiveness of the catalog; and support a system's
implementation. Also, many catalogs are not evaluate themselves but used to support another proposal. Five
supporting purposes were found out: to support evaluations, to be used in a model, to be used for comparison
study, to be used in a tool, to be used in proposed approaches.</p>
      <p>Then, a fourth and last opportunity is related to the evaluation of a proposed catalog. Few catalogs presented
detailed evaluation procedures. Thus, there is a need to create a guideline to guide NFRs catalog evaluations.
This paper has presented a study about NFRs' catalogs5. Through the SM method, together with quantitative
and qualitative analysis (content analysis), it was possible to derive important information about the catalogs
that are useful not only for researchers but also for developers who are concerned with satisfying NFRs in their
systems. Thus, the contributions of this work have implications regarding both industry and academy.</p>
      <p>For industry, this work generated a dataset containing more than 1000 subcharacteristics, 1113 implementation
and design methods, 473 positive correlations, 395 negative correlations for 86 NFRs. We believe this base can
be useful for developers to search several ways of implementing NFRs and thus reuse the knowledge gained from
this research. For academy, this work generated a list of four high-level research opportunities that can improve
the NFRs catalogs area. As a next step, we are using the results of this study to propose a process to de ne
NFRs catalogs.</p>
      <p>As future work, we plan to conduct a study in the industry to understand the usage of NFRs catalog in real
scenarios. Then, the current challenges and issues the practitioners have faced in their work could be investigated.
Furthermore, we encourage additional searches to possibly expand our database of NFRs catalogs.
5All materials and results from this SM study are available at https://github.com/great-ufc/SM-NFRsCatalogs</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Wiegers</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Beatty</surname>
          </string-name>
          , J.:
          <article-title>Software requirements</article-title>
          .
          <source>Pearson Education</source>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Chung</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nixon</surname>
            ,
            <given-names>B. A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yu</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Mylopoulos</surname>
          </string-name>
          , J.:
          <article-title>Non-functional requirements in software engineering</article-title>
          . Springer Science Business Media (
          <year>2000</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Mairiza</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Zowghi</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Constructing a Catalogue of Con icts among Non-functional Requirements</article-title>
          . In: Communications in Computer and Information Science, (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Cysneiros</surname>
            ,
            <given-names>L. M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Werneck</surname>
            ,
            <given-names>V. M.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Kushniruk</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Reusable knowledge for satis cing usability requirements</article-title>
          .
          <source>In: IEEE International Conference on Requirements Engineering</source>
          , (
          <year>2005</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Gramatica</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Labunets</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Massacci</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Paci</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Tedeschi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>The role of catalogues of threats and security controls in security risk assessment: an empirical study with ATM professionals</article-title>
          . In International Working Conference on Requirements Engineering:
          <article-title>Foundation for Software Quality (</article-title>
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Petersen</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vakkalanka</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuzniarz</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>Guidelines for conducting systematic mapping studies in software engineering: An update</article-title>
          .
          <source>Information and Software Technology</source>
          ,
          <volume>64</volume>
          ,
          <fpage>1</fpage>
          -
          <lpage>18</lpage>
          .(
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Kuhrmann</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fernandez</surname>
            ,
            <given-names>D. M.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Daneva</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>On the pragmatic design of literature studies in software engineering: an experience-based guideline</article-title>
          .
          <source>Empirical software engineering</source>
          ,
          <volume>22</volume>
          (
          <issue>6</issue>
          ),
          <fpage>2852</fpage>
          -
          <lpage>2891</lpage>
          . (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Leite</surname>
            ,
            <given-names>J. C.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Cappelli</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Software transparency</article-title>
          .
          <source>Business and Information Systems Engineering</source>
          , Springer (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Zinovatna</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Cysneiros</surname>
            ,
            <given-names>L. M.</given-names>
          </string-name>
          :
          <article-title>Reusing knowledge on delivering privacy and transparency together</article-title>
          .
          <source>In: IEEE Fifth International Workshop on Requirements Patterns (RePa)</source>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Kitchenham</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Brereton</surname>
            ,
            <given-names>P.:</given-names>
          </string-name>
          <article-title>A systematic review of systematic review process research in software engineering</article-title>
          .
          <source>Information and software technology</source>
          ,
          <volume>55</volume>
          (
          <issue>12</issue>
          ),
          <fpage>2049</fpage>
          -
          <lpage>2075</lpage>
          . (
          <year>2013</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Cho</surname>
            ,
            <given-names>J. Y.</given-names>
          </string-name>
          and
          <string-name>
            <surname>LEE</surname>
          </string-name>
          , E.-H.:
          <article-title>Reducing confusion about grounded theory and qualitative content analysis: Similarities and di erences</article-title>
          .
          <source>In The qualitative report</source>
          , v.
          <volume>19</volume>
          , n.
          <volume>32</volume>
          , p.
          <volume>1</volume>
          {
          <fpage>20</fpage>
          , (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Nixon</surname>
            ,
            <given-names>B. A.</given-names>
          </string-name>
          :
          <article-title>Management of Performance Requirements for Information Systems</article-title>
          .
          <source>IEEE Transactions on Software Engineering</source>
          (
          <year>2000</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>Cysneiros</surname>
            ,
            <given-names>L. M.</given-names>
          </string-name>
          :
          <article-title>Evaluating the E ectiveness of Using Catalogues to Elicit Non-Functional Requirements</article-title>
          . In Workshop in Requirements Engineering, (
          <year>2007</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>