<!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>Automated GDPR-Compliance in Requirements Engineering</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Business Informatics and Operations Management, Faculty of Economics and Business Administration, Ghent University</institution>
          ,
          <addr-line>Ghent</addr-line>
          ,
          <country country="BE">Belgium</country>
        </aff>
      </contrib-group>
      <fpage>21</fpage>
      <lpage>29</lpage>
      <abstract>
        <p>In the last lustrum, the EU General Data Protection Regulation (GDPR) profoundly impacted data processing organizations as compliance with this Regulation became obligatory. Due to resource poverty, complying with the GDPR can be a challenge for small and mediumsized enterprises. In this research, we consider GDPR-compliance as a high-level goal in software development that should be addressed at the outset of software development, that is, during requirements engineering (RE). Moreover, we argue that natural language processing (NLP) can be utilized to automate this process. Therefore, this Ph.D. research aims to address the challenge organizations face by developing an NLP-based automated approach towards GDPR-compliance in RE. In particular, we aim to develop an approach to assess whether a set of system requirements complies with the GDPR to achieve data protection by design and by default, thus providing organizations with an e cient and e ective solution to ensure GDPR-compliance. This paper presents our research questions and their relevance, the adopted research method, preliminary results, and the current state of our research.</p>
      </abstract>
      <kwd-group>
        <kwd>General Data Protection Regulation</kwd>
        <kwd>Machine Learning</kwd>
        <kwd>Natural Language Processing</kwd>
        <kwd>Requirements Engineering</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Provisionally agreed upon in 2015, the General Data Protection Regulation
(GDPR) came into e ect in May 2018 to ensure and safeguard data subjects'
rights. The GDPR applies to any personal data processing of European data
subjects|regardless of whether the data processing itself takes place in the
European Union|and ensures that individuals are not deprived of their data
protection rights. Furthermore, the GDPR's transnational application results in
far-reaching implications on the digital market of the world [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>
        To achieve GDPR compliance, organizations should take technical and
organizational measures necessary to ensure data protection by design and by default
to achieve GDPR-compliance [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. Since the conditions for data processing are
Copyright © 2021 for this paper by its authors. Use permitted under Creative
Commons License Attribution 4.0 International (CC BY 4.0).
fundamentally being set by the soft- and hardware used for the task [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ], we
consider GDPR-compliance to be a high-level goal in software development. In this
Ph.D. research, we aim to address GDPR-compliance at the outset of software
development, meaning requirements engineering, to achieve data protection by
design and by default. Requirements engineering consists of the elicitation,
evaluation, speci cation, analysis, and evolution of the objectives, functionalities,
qualities, and constraints to be achieved by a software-intensive system [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. In
this research, these constraints are set by the GDPR.
      </p>
      <p>
        Complying with the GDPR demands signi cant e orts, which can be
especially troublesome for small and medium-sized enterprises (SMEs) due to lack
of resources to take the necessary technical, and organizational measures [
        <xref ref-type="bibr" rid="ref17 ref8">8, 17</xref>
        ].
Moreover, the need to nd e cient and e ective solutions to ensure
GDPRcompliance [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] is emphasized by the fact that the vast majority of businesses
(99%) in the European Union are SMEs [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
      </p>
      <p>
        Therefore, we propose using natural language processing (NLP) techniques|
a popular approach amongst requirements engineers [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]|as a means of
automating GDPR-compliance in organizations. Requirements engineering is especially
conducive for the use of NLP since requirements are often expressed in natural
language [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
      </p>
      <p>The main focus of this Ph.D. research is to prevent organizations from
compromising the privacy of data subjects and ensuring data protection by design
and by default, by addressing GDPR-compliance at the intersection of RE and
NLP. The remainder of this paper is structured as follows. Section 2 presents
our research questions. Section 3 describes the adopted research method. The
preliminary results are presented in Section 4. Section 5 presents the current
stage of our research. Related work is presented in Section 6. Finally, Section 7
concludes this paper and elaborates on our plans for future work.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Research Questions</title>
      <p>The goal of this Ph.D. research is to achieve NLP-based automated
GDPRcompliance in RE. In doing so, we aim to build a bridge between GDPR, NLP,
and RE to provide organizations with insights towards GDPR-compliance.
Furthermore, we intend to develop a machine learning approach based on NLP to
facilitate GDPR-compliance and prevent organizations from compromising EU
citizens' privacy, thus ensuring data protection. To achieve this, we adopt an
incremental approach which is re ected in our research questions (RQs) and the
corresponding sub-research questions (SRQs):
RQ1 \What is the current state of research as to NLP-based automated
GDPRcompliance in RE? " This RQ aims to map the existing literature on the
intersection of GDPR, NLP and RE relevant to achieving automated GDPR-compliance.
However, since preliminary research yielded no relevant studies, it was decided
to formulate SRQs to search all possible combinations of the three domains (i.e.,
GDPR, NLP, and RE):
SRQ1 \What NLP approaches are useful for RE and for which RE
activity? " Literature shows that several NLP approaches are available for the
di erent activities in RE. However, no systematic literature mapping exists
where these di erent approaches are mapped with the tasks they can be used
for while upholding the higher goal of automating GDPR-compliance in RE.
SRQ2 \Which NLP approaches are available for achieving GDPR-compliance
in organizations? " In addition to mapping the NLP approaches explicitly
developed for the RE domain, it is also interesting to explore NLP approaches
outside the RE paradigm that focus on achieving GDPR-compliance in
organizations. This insight will allow us to investigate the possibility of learning
from these approaches and transfer this learning to the RE phase in software
development.</p>
      <p>SRQ3 \Which state-of-the-art RE solutions are available for achieving
GDPR-compliance? " This question endeavors to identify state-of-the-art RE
solution types that maintain and possibly facilitate the GDPR. The answer
to this question will provide us with a topical mapping of the RE
developments in achieving GDPR-compliance.</p>
      <p>RQ2 \How to automatically assess organizations' GDPR-compliance based
on their privacy policy? " This research question aims to assess organizations'
GDPR-compliance through an NLP-based machine learning approach.
Organizations use privacy policies to convey the taken GDPR-measures to data
subjects. We will particularly focus on SMEs and provide them with an e cient and
e ective approach to identify possible GDPR non-compliance.</p>
      <p>RQ3 \How do organizations di er in their approach to GDPR-compliance? "
Building on the previous RQ, this question aims to identify the in uence of
organizational factors such as size and industry on GDPR-compliance. The
construed machine learning approach of RQ2 will be used to classify a data set
comprising organizations and their respective privacy policies on their GDPR
compliance. The resulting classi cation will be combined with organizational
meta-data of the corresponding organizations, after which possible relationships
between GDPR-compliance and organizational factors will be identi ed through
machine learning. The outcome may validate the need for a tailored approach
towards GDPR-compliance for organizations, addressed in RQ4.
RQ4 \How to automatically identify the GDPR-compliance of a set system
requirements? " This question is built on the outcomes of RQ2 and RQ3 and
aims to devise an automated approach based on NLP and machine learning,
tailored to the outcome of RQ3, that can be used to assess, by using NLP-based
machine learning, the GDPR-compliance of a set system requirements at the
outset of software development and thus achieving data protection by design
and by default.</p>
      <p>Summarized, we adopt an incremental approach towards our goal of
NLPbased automated GDPR-compliance in RE. First, we intend to explore the
literature on the intersection of GDPR, NLP, and RE. Next, we aim to develop
an NLP-based machine learning approach to assess the GDPR-compliance of
organizations' privacy policies. Furthermore, we aim to identify the
organizational factors that in uence this GDPR-compliance. Based on the identi ed
factors, we intend to devise an automated approach based on machine
learning that focuses on achieving GDPR-compliance by design and by default, by
automatically assessing system requirements at the beginning of the software
development process on their GDPR-compliance. This approach will enable
requirements engineering professionals to identify requirements automatically that
may lead to non-compliance, consequently instilling a proactive stance towards
GDPR-compliance. The envisaged outcomes and solutions are intended to
facilitate GDPR-compliance in organizations by providing the corresponding
professionals with the means to achieve this compliance.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Research Method</title>
      <p>
        This research adopts the design science research methodology. Design science
research is a research paradigm that focuses on answering questions related to
human problems by creating new and innovating artifacts [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. This research
paradigm is built upon the fundamental principle that knowledge and
understanding of a design problem and its solutions are acquired in the building and
application of an artifact. In examining how artifacts can be developed, design
science research can be seen as an embodiment of three closely related cycles of
activities: the relevance cycle, the rigor cycle, and the design cycle [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. The
relevance cycle links the contextual environment with the research and introduces
the research artifacts into environmental eld testing. The rigor cycle bridges
the knowledge base with the research and adds incrementally the new knowledge
created by the research to the knowledge base. Lastly, the design cycle iterates
between the core activities of building and evaluating the design artifacts and
processes of the research.
      </p>
      <p>In this Ph.D. research, the need to nd e cient and e ective solutions to
ensure GDPR-compliance in organizations forms the problem space of interest.
We intend to address this by developing an NLP-based machine learning
approach to assist organizations in meeting GDPR-compliance in RE. However,
rst, we aim to validate this need and understand the problem space by
developing an artifact that assesses GDPR-compliance of organizations based on the
measures adopted as communicated through their privacy policies, followed by
identifying the organizational factors that contribute to non-compliance|thus
iterating between the relevance cycle and the design cycle while contributing
to the knowledge base. Based on the outcome, we intend to develop a machine
learning approach|in the design cycle|to achieve GDPR-compliance by design
and by default, by automatically assessing system requirements in the RE phase
of software development on their GDPR-compliance. Finally, we aim to evaluate
the performance of this machine learning approach using expert-labeled data.</p>
    </sec>
    <sec id="sec-4">
      <title>Preliminary Results</title>
      <p>
        This Ph.D. research started with conducting a systematic mapping study [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ],
following the guidelines in [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], to address RQ1 and its sub-research questions and
identify the current research state of NLP-based automated GDPR-compliance
in RE. The mapping study resulted in 448 relevant studies. The majority of
these studies|420 studies|were identi ed as relevant to SRQ1, which centers
around NLP and RE. SRQ2, focusing on GDPR and NLP, yielded nine studies.
SRQ3, which centers around GDPR and RE, resulted in 20 studies. One of the
retrieved studies fell within all pairwise research eld combinations (i.e., NLP &amp;
RE, NLP &amp; GDPR, and GDPR &amp; RE) [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. The referenced study presents a
recommender-based privacy requirements elicitation approach (EPICUREAN)
which uses NLP and machine learning techniques in the RE activity of domain
understanding &amp; elicitation to determine and recommend appropriate privacy
settings to the user and, as a result of this, simplifying privacy settings according
to the GDPR.
      </p>
      <p>Regarding SRQ1, 420 studies were identi ed, mentioning 199 di erent NLP
approaches useful for RE. The most common NLP approaches were
part-ofspeech tagging, pre-processing, and text-classi cation with 165, 117, and 104
occurrences, respectively. SRQ2, aimed to identify studies that discuss NLP
approaches used to achieve GDPR-compliance in organizations, yielded nine studies
in which text-classi cation and pre-processing were the most frequently
occurring NLP approaches with 4 and 2 occurrences, respectively. Furthermore, the
retrieved studies related to SRQ2 addressed the GDPR concept of
anonymization four times, privacy was addressed twice, consent and lawfulness, fairness
and transparency occurred each once. Lastly, regarding SRQ3, 20 studies were
identi ed that discussed RE solutions for achieving GDPR-compliance in
organizations. The most frequent occurring solutions types were Approach and Method,
proposed as a solution by four studies each.</p>
      <p>Next to the key ndings that addressed our research questions, we discovered
several interesting phenomena. First, the mapping revealed a tendency among
researchers from the RE community to concentrate mainly on the RE
activities of domain understanding &amp; elicitation and speci cation &amp; documentation.
Concurrently, the activities of evaluation &amp; negotiation, and quality assurance
receive less attention. This development was true for research related to both
SRQ1 and SRQ2. For studies related to SRQ1, this may imply that researchers
overlooked the possibility of using NLP for the activities of evaluation &amp;
negotiation, and quality assurance. Another possibility is that RE tasks in the latter
are less suitable for automating with NLP. Second, it could be foreseen from
the line of questioning in our research questions that the resulting studies will
gravitate towards design science research. Therefore, it is not unexpected that
the vast majority of studies focused on proposing a solution and acted within
this research paradigm. However, this is done at the expense of other research
types, to the detriment of the diversity of RE as a research domain.</p>
      <p>Despite identifying only one study on the intersection of GDPR, NLP, and
RE, we have|during the mapping process|identi ed possibilities for bridging
these research elds to achieve GDPR-compliance through data protection by
design and by default in RE. In particular, we focus on literature related to
SRQ2 and SRQ3 because they address the GDPR explicitly. Scrutinizing the
solutions proposed by literature related to NLP and GDPR (SRQ2) gives rise
to the opportunity of introducing these approaches to classi cation problems in
the RE domain, for instance, using NLP-based machine learning solutions that
identify GDPR-compliance on requirement documents. Moreover, examining the
studies related to SRQ3 presents possibilities of using NLP techniques to assist
with manual and potentially repetitive tasks on the junction of GDPR and RE.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Current Stage</title>
      <p>At this stage, we are working towards an approach to automatically assess
organizations' GDPR-compliance based on their privacy policy (RQ2). As mentioned
in Section 2, this question aims to assess organizations' GDPR-compliance by
developing an NLP-based machine learning approach that can be used to
assess privacy policies' GDPR-coverage based on a set of prede ned assessment
criteria. The results of such a classi cation may imply that a particular
organization fails to comply with the GDPR-measures. Speci cally, we will focus on
SMEs|due to the threat of resource poverty|and provide them with an e cient
and e ective approach to identify possible GDPR non-compliance. Currently, we
are concerned with collecting and labeling data that can be used to train our
machine learning model. After this process, we aim to build the classi cation
model and evaluate its usefulness. Consequently, we will extend this research
to RQ3, which focuses on identifying how organizations di er in their approach
to GDPR-compliance. In detail, we aim to use machine learning techniques to
identify factors (e.g., organization size) that in uence GDPR non-compliance.
6</p>
    </sec>
    <sec id="sec-6">
      <title>Related Work</title>
      <p>
        As manifested through our mapping study, research related to automating
GDPRcompliance is still in its infancy. Due to the relative novelty of the GDPR (i.e., it
is enforced since 2018), not much research was conducted on the intersection of
GDPR, NLP, and RE. In fact, our mapping study (See Section 4) identi ed only
one study on the convergence of GDPR, NLP, and RE [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. The authors present
a recommender-based privacy requirements elicitation approach that uses
natural language processing techniques to determine and provide|in line with the
GDPR|users with privacy setting suggestions tailored to their needs. Our
research does not focus on eliciting requirements; instead, we aim to
automatically assess system requirements on their GDPR-compliance using NLP-based
machine learning. The following paragraph will shed light on some contiguous
research that centers on using NLP towards GDPR-compliance.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], a new model auditing technique is presented to help enforce data
protection regulations (e.g., GDPR) by aiding users in detecting whether their
data was used to train a machine learning model. In the same stream, [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] proposes
an automated privacy policy extraction system that considers users' privacy
concerns while providing the user with GDPR items to assist in privacy-aware
decision making. Reference [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] proposes a supervised machine learning system
that identi es personal information in large data sets to ease processing such data
in an organization according to the GDPR. Along the same lines, [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] presents
a system based on NLP and machine learning capable of correctly identifying
sensitive data, assisting companies in complying with standards such as the
GDPR. Moreover, [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] presents an approach that implements NLP to detect
personally identi able information in contracts.
      </p>
      <p>However, the studies above are located on the crossing of GDPR and NLP,
whereas our research aims to use NLP to automate GDPR-compliance in RE
to achieve data protection by design and default, thus combining the elds of
GDPR, NLP, and RE.
7</p>
    </sec>
    <sec id="sec-7">
      <title>Conclusion and Future Work</title>
      <p>This paper presents our research approach to achieve data protection by design
and by default through developing an NLP-based machine learning approach to
assess system requirements on their GDPR-compliance. In preparation for
developing this approach, we have conducted a systematic mapping study to outline
the current research state on the junction of GDPR, NLP, and RE. The mapping
study shows potential for our intersectional research. Currently, we are devising
a machine learning approach to assess organizations' privacy policies on
GDPRcompliance to validate the need for data protection by design and by default as
intended by our primary objective. Thereafter, we aim to identify organizational
factors that in uence GDPR-compliance. Finally, we plan to develop an
NLPbased machine learning approach that focuses on achieving GDPR-compliance
by automatically assessing the compliance of system requirements at the
beginning of the software development process. In summary, this Ph.D. research
contributes to a novel research stream on the intersection of GDPR, NLP, and RE
by developing an NLP-based automated approach towards GDPR-compliance
in RE and towards ensuring data protection by design and by default.</p>
    </sec>
    <sec id="sec-8">
      <title>Acknowledgments References</title>
      <p>This Ph.D. research is supervised by Prof. Dr. Geert Poels and Dr. Seppe vanden
Broucke.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Aberkane</surname>
            ,
            <given-names>A.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Poels</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Broucke</surname>
            ,
            <given-names>S.V.</given-names>
          </string-name>
          :
          <article-title>Exploring automated gdpr-compliance in requirements engineering: A systematic mapping study</article-title>
          .
          <source>IEEE Access 9</source>
          ,
          <issue>66542</issue>
          {
          <fpage>66559</fpage>
          (
          <year>2021</year>
          ). https://doi.org/10.1109/ACCESS.
          <year>2021</year>
          .3076921
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Albrecht</surname>
            ,
            <given-names>J.P.</given-names>
          </string-name>
          :
          <article-title>How the gdpr will change the world</article-title>
          .
          <source>Eur. Data Protection Law Rev</source>
          .
          <volume>2</volume>
          (
          <issue>3</issue>
          ),
          <volume>287</volume>
          {
          <fpage>289</fpage>
          (
          <year>2016</year>
          ). https://doi.org/10.21552/edpl/2016/3/4
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <issue>3</issue>
          .
          <string-name>
            <surname>Chang</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Li</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          , Zhang,
          <string-name>
            <given-names>Y.</given-names>
            ,
            <surname>Du</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Cao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            ,
            <surname>Zhu</surname>
          </string-name>
          , H.:
          <article-title>Automated and personalized privacy policy extraction under gdpr consideration</article-title>
          .
          <source>In: International Conference on Wireless Algorithms, Systems, and Applications</source>
          . pp.
          <volume>43</volume>
          {
          <fpage>54</fpage>
          . Springer, Cham (Jun
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Dalpiaz</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ferrari</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Franch</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Palomares</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Natural language processing for requirements engineering: the best is yet to come</article-title>
          .
          <source>IEEE Softw</source>
          .
          <volume>35</volume>
          (
          <issue>5</issue>
          ),
          <volume>115</volume>
          {119 (Sep
          <year>2018</year>
          ). https://doi.org/10.1109/MS.
          <year>2018</year>
          .3571242
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>Di</given-names>
            <surname>Cerbo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            ,
            <surname>Trabelsi</surname>
          </string-name>
          ,
          <string-name>
            <surname>S.</surname>
          </string-name>
          :
          <article-title>Towards personal data identi cation and anonymization using machine learning techniques</article-title>
          .
          <source>In: European Conference on Advances in Databases and Information Systems</source>
          , vol.
          <volume>909</volume>
          , pp.
          <volume>118</volume>
          {
          <fpage>126</fpage>
          . Springer, Cham (Aug
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Dias</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ferreira</surname>
            ,
            <given-names>J.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maia</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Santos</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ribeiro</surname>
          </string-name>
          , R.:
          <article-title>Privacy in text documents</article-title>
          .
          <source>In: Proceedings of the 33rd International Business Information Management Association Conference</source>
          . pp.
          <volume>2551</volume>
          {
          <issue>2560</issue>
          (Apr
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>European</given-names>
            <surname>Commission</surname>
          </string-name>
          :
          <article-title>Internal market, industry, entrepreneurship and smes</article-title>
          , https://ec.europa.eu/growth/smes/sme-de nition en,
          <source>accessed Apr. 9</source>
          , 2021
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Freitas</surname>
          </string-name>
          , M.d.C.,
          <string-name>
            <surname>Mira</surname>
          </string-name>
          da Silva, M.:
          <article-title>Gdpr compliance in smes: There is much to be done</article-title>
          .
          <source>J. Inf. Syst. Eng. &amp; Manage</source>
          .
          <volume>3</volume>
          (
          <issue>4</issue>
          ),
          <volume>30</volume>
          (
          <year>2018</year>
          ). https://doi.org/10.20897/jisem/3941
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Hevner</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chatterjee</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Design science research in information systems</article-title>
          .
          <source>In: Design research in information systems</source>
          , pp.
          <volume>16</volume>
          {
          <fpage>19</fpage>
          . Integrated Series in Information Systems, Springer, Boston, MA, USA (
          <year>2010</year>
          ). https://doi.org/10.1007/978-1-
          <fpage>4419</fpage>
          - 5653-8
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Hevner</surname>
            ,
            <given-names>A.R.:</given-names>
          </string-name>
          <article-title>A three cycle view of design science research</article-title>
          .
          <source>Scandinavian J. Inf. Syst</source>
          .
          <volume>19</volume>
          (
          <issue>2</issue>
          ),
          <volume>4</volume>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Kassab</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Neill</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Laplante</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>State of practice in requirements engineering: contemporary data</article-title>
          .
          <source>Innov. Syst. Softw. Eng</source>
          .
          <volume>10</volume>
          (
          <issue>4</issue>
          ),
          <volume>235</volume>
          {241 (Apr
          <year>2014</year>
          ). https://doi.org/10.1007/s11334-014-0232-4
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Keele</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Guidelines for performing systematic literature reviews in software engineering</article-title>
          .
          <source>Tech. Report 2.3</source>
          , Dept. Comput. Sci., Univ. Durham, Durham,
          <string-name>
            <surname>U.K.</surname>
          </string-name>
          (
          <year>Jul 2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Silva</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goncalves</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Godinho</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Antunes</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Curado</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>Using natural language processing to detect privacy violations in online contracts</article-title>
          .
          <source>In: Proceedings of the 35th Annual ACM Symposium on Applied Computing</source>
          . pp.
          <volume>1305</volume>
          {
          <fpage>1307</fpage>
          .
          <string-name>
            <surname>ACM</surname>
          </string-name>
          , New York, NY, United
          <string-name>
            <surname>States</surname>
          </string-name>
          (
          <year>Mar 2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Song</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shmatikov</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          :
          <article-title>Auditing data provenance in text-generation models</article-title>
          .
          <source>In: Proceedings of the ACM SIGKDD International Conference on Knowledge Discovery and Data Mining</source>
          . pp.
          <volume>196</volume>
          {
          <fpage>206</fpage>
          .
          <string-name>
            <surname>ACM</surname>
          </string-name>
          , New York, NY, USA (Jul
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Stach</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Steimle</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Recommender-based privacy requirements elicitation - EPICUREAN</article-title>
          .
          <source>In: Proceedings of the 34th ACM/SIGAPP Symposium on Applied Computing</source>
          . pp.
          <volume>1500</volume>
          {
          <fpage>1507</fpage>
          .
          <string-name>
            <surname>ACM</surname>
          </string-name>
          , New York, NY, USA (Apr
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <article-title>The European Parliament and the Council of European Union: REGULATION (EU)</article-title>
          <year>2016</year>
          /679.
          <article-title>O cial Journal of the European Union (</article-title>
          <year>2016</year>
          ). https://doi.org/http://data.europa.eu/eli/reg/2016/679/2016-05-04
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Tikkinen-Piri</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rohunen</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Markkula</surname>
          </string-name>
          , J.:
          <article-title>Eu general data protection regulation: Changes and implications for personal data collecting companies</article-title>
          .
          <source>Comput. Law &amp; Sec. Review</source>
          <volume>34</volume>
          (
          <issue>1</issue>
          ),
          <volume>134</volume>
          {
          <fpage>153</fpage>
          (
          <year>2018</year>
          ). https://doi.org/10.1016/j.clsr.
          <year>2017</year>
          .
          <volume>05</volume>
          .015
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Van Lamsweerde</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Requirements engineering: From system goals to UML models to software</article-title>
          , vol.
          <volume>10</volume>
          , pp.
          <volume>30</volume>
          {
          <fpage>34</fpage>
          . John Wiley &amp; Sons, Chichester, UK (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Voigt</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          , von dem Bussche,
          <string-name>
            <surname>A.</surname>
          </string-name>
          :
          <source>The EU General Data Protection Regulation (GDPR)</source>
          , vol.
          <volume>1</volume>
          , p.
          <fpage>62</fpage>
          . Springer, Cham (
          <year>2017</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>319</fpage>
          - 57959-7
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>