<!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 Assistance for Data Modelers combining Natural Language Processing and Data Modeling Heuristics: A Prototype Demonstration?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Benjamin Ternes</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kristina Rosenthal</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Stefan Strecker</string-name>
          <email>stefan.streckerg@fernuni-hagen.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Enterprise Modelling Research Group, University of Hagen</institution>
          ,
          <addr-line>Hagen</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <fpage>25</fpage>
      <lpage>30</lpage>
      <abstract>
        <p>Identi ers of model elements convey semantics of conceptual models essential to interpretation by human viewers. Prior research shows that devising meaningful identi ers for model elements challenges data modelers from early learning stages to advanced levels of modeling expertise, constituting one of the most common di culties data modelers face. We demonstrate the Automated Assistant, an integrated modeling tool support component combining natural language processing techniques and data modeling heuristics to provide data modelers with modeling-time feedback on identifying and signifying entity types, relationship types, and attributes with meaningful identi ers. Di erent from other approaches to automating assistance for data modelers, the Automated Assistant implementation does not rely on xed reference solutions for modeling tasks as it processes (m)any natural language descriptions of modeling tasks. We report on the current state of prototype development, discuss the Automated Assistant implementation and outline future work.</p>
      </abstract>
      <kwd-group>
        <kwd>Conceptual Modeling</kwd>
        <kwd>Data Modeling</kwd>
        <kwd>Modeling Tool</kwd>
        <kwd>Natural Language Processing</kwd>
        <kwd>Process-oriented Feedback</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Model element identi ers (labels), e. g., for entity types, relationship types and
attributes in an Entity-Relationship (ER) diagram, carry and convey semantics
important to sensible interpretation of conceptual data models by human
viewers, semantics transcending the formal semantics of model elements [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. Devising
meaningful, appropriate, and expedient identi ers is a prerequisite for
comprehensible and usable conceptual models [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Empirical research shows that data
modelers oftentimes face di culties devising meaningful identi ers for model
elements from early learning stages to advanced levels of modeling expertise,
described as one of the most common di culties beginning learners face [
        <xref ref-type="bibr" rid="ref1 ref11">1,11</xref>
        ]. To
? Copyright © 2021 for this paper by its authors. Use permitted under Creative
      </p>
      <p>
        Commons License Attribution 4.0 International (CC BY 4.0).
support learners of data modeling in devising meaningful identi ers for model
elements, we design and implement the Automated Assistant, a research
prototype that provides modeling-time feedback to data modelers on their choice
of model element identi ers based on the natural language description of the
respective modeling universe of discourse (cf. [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]).
      </p>
      <p>
        The primary use case of the Automated Assistant is a learning context in
which learners of data modeling are asked to create an ER diagram based on
a textual description of a modeling task|a common learning scenario in many
settings. Research, design and prototype implementation of the Automated
Assistant combine and build on research on data modeling heuristics for identi er
formulation from natural language descriptions [
        <xref ref-type="bibr" rid="ref15 ref2">2,15</xref>
        ] and on research on
Natural Language Processing (NLP) [
        <xref ref-type="bibr" rid="ref3 ref4">3,4</xref>
        ]. Di erent from prior work (e. g.[
        <xref ref-type="bibr" rid="ref15 ref5 ref8 ref9">9,15,5,8</xref>
        ]),
the Automated Assistant does not require the time-consuming ex ante
construction of (multiple) reference solutions to a speci c modeling task description but
works on (m)any natural language descriptions of a modeling task (as long as
they comply with English grammar).
      </p>
      <p>
        The Automated Assistant prototype described in the present work
substantially extends an earlier prototype implementation (cf. [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]). Speci cally, we
substantially extend the number of implemented data modeling heuristics for
better detection of compound nouns signifying entity types as well as for
detecting associated attributes, and we enhance the earlier prototype implementation
by an identi cation component for data types of attributes. Moreover, the
prototype implementation now presents generated candidates for element identi ers
color highlighted to the modeler.
2
      </p>
      <p>
        The Automated Assistant Prototype Overview
The Automated Assistant prototype implementation builds on TOOL, a
modeling tool web application [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. TOOL provides a graphical data modeling editor
which implements a variant of the Entity-Relationship Model [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] to create ER
diagrams. The Automated Assistant hooks into the graphical editor to assist
data modelers at modeling-time with suggestions on signifying element
identiers. The Automated Assistant implementation utilizes the Stanford CoreNLP
toolkit [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] which provides a pipeline framework for deriving linguistic
annotations from natural language text input, in combination with heuristics rules for
data modeling that we adapt and re ne to the in-browser ER modeling
variant. Moreover, the Automated Assistant implements widely accepted naming
conventions for ER modeling (e. g., [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]).
      </p>
      <p>In a nutshell, the prototype implementation of the Automated Assistant
essentially applies a two-step procedure: First, starting from a (1) (natural
language) modeling task description, a list of potential candidates for meaningful
identi ers for entity types, associated attributes, and relationship types is
generated. Then, based on the results of step (1), feedback (2) is provided to modelers
at modeling-time in the graphical modeling editor on their choice of model
element identi ers and data types|potential candidates for meaningful entity</p>
    </sec>
    <sec id="sec-2">
      <title>Natural language description of a modeling task</title>
      <p>Execution flow
g
n
liittpS lit)
tceen (ssp
n
e
S</p>
      <p>itfr--caopeheagggnTPS ()spo illlircyssohpogonaaAM l()eamm iiitttycaedneognnoENRm ()rne</p>
      <p>Stanford CoreNLP pipeline
(adapted for our application context)
g
n
iittrccaaP )r(saep
s
n
y
S</p>
    </sec>
    <sec id="sec-3">
      <title>Executing heuristic rules &amp;</title>
      <p>naming conventions
rs fr)e
ttoano ,rcedo
rnA dne
the ,.g
O .ge
(</p>
    </sec>
    <sec id="sec-4">
      <title>Annotated text</title>
      <p>(e.g., amod, NN)</p>
    </sec>
    <sec id="sec-5">
      <title>Linguistic annotations</title>
    </sec>
    <sec id="sec-6">
      <title>Heuristics rules</title>
      <p>&amp; naming conventions
37 Heuristics</p>
    </sec>
    <sec id="sec-7">
      <title>3 Conventions</title>
    </sec>
    <sec id="sec-8">
      <title>Rule head (if)</title>
    </sec>
    <sec id="sec-9">
      <title>Rule tail (then) generates</title>
    </sec>
    <sec id="sec-10">
      <title>Lists of candidates</title>
      <p>
        type identi ers as well as corresponding attributes, and data types are color
highlighted in the textual description displayed to the modelers. To generate a
list of potential candidates based on natural language description (cf. step 1),
the pipeline of the CoreNLP toolkit is adapted to the primary use case of the
Automated Assistant (see Fig. 2), and enhanced in several design iterations by
conscientiously revising the applied heuristic rules for classifying certain
patterns of statements of the English language for identifying identi ers of model
elements (e. g., [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]). The identi cation of potential candidates mainly relies on
part-of-speech tagging and statistical dependency parsing (e. g., words which
modify nominal phrases|adjectival modi ers) and to establish (grammatical)
relations between words (e. g., by typed dependencies). The Automated
Assistant utilizes multiple NLP techniques (built into the CoreNLP implementation)
for the analysis of modeling task descriptions in a speci c order: tokenization,
sentence splitting, part-of-speech tagging, morphological analysis, and syntactic
parsing (see Fig. 2). The subsequent identi cation of candidates for identi ers
for entity types, associated attributes, and relationship types builds on
linguistic annotations returned from CoreNLP as a semantic graph consisting of lists
of tuples. Starting from these linguistic annotations, the revised prototype
implementation applies 37 heuristic rules (13 on relationship types, 13 on entity
types, and 11 on associated attributes) and 3 naming conventions for
formulating model element identi ers to match them with the syntactical functions of
the annotation pipeline. The heuristic rules and naming conventions are
reconstructed, adapted and re ned from a comprehensive review of prior work (the
adapted annotation pipeline is described in further detail in [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]).
      </p>
      <p>
        From a modeler's perspective, the Automated Assistant suggests feedback
(cf. step 2), i. e., whenever a modeler devises identi ers of a model elements on
the modeling canvas of the graphical modeling editor (see Fig. 2). The provided
feedback aims at supporting modelers in developing an understanding of how to
identify and signify model elements meaningfully, and, in particular, to encourage
modelers to rethink their choices for model element identi ers based on sensible
auto-generated suggestions of the Automated Assistant. Hence, the Automated
Assistant provides feedback in three categories: (a) `Great' for positive feedback,
e. g., if a label matches an entity type of the generated candidate list (in green);
(b) `Reconsider' for a label that is not mentioned in the modeling task description
or that is not identi ed as a possible candidate for an entity type, attribute, or
relationship type (problem-oriented feedback; in orange); (c) `Convention' if the
input does not follow the implemented naming conventions, e. g., if an entity
type label begins with a lowercase letter, or a spelling error is examined (neutral
feedback; in yellow). As a major usability enhancement to an earlier version of the
Automatic Assistant (cf. [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]), we have further extended the integrated modeling
tool support to color highlight possible entity types and associated attributes in
the textual description, e. g., when there is uncertainty or when the modeler
wants to compare them to the chosen model element identi ers on the modeling
canvas (see Fig. 2, right side). Compared to earlier prototype implementations,
the Automated Assistant now provides more accurate feedback on data types of
attributes based on named entity recognition. A short video demonstrator of the
Automated Assistant is available at: https://video.fernuni-hagen.de/Play/896
      </p>
      <p>
        Discussion and Outlook
The Automated Assistant provides modeling-time feedback to modelers on their
choice of model element identi ers based on natural language processing of
modeling task descriptions to assist in overcoming one of the most common (learning)
di culties data modelers face, i. e., devising meaningful and expedient
identiers for model elements [
        <xref ref-type="bibr" rid="ref1 ref10">1,10</xref>
        ]. Evaluation of the feedback generated by the
Automated Assistant from three modeling task descriptions of increasing length
and complexity suggests that the generated feedback is similar to human (e. g.,
instructor's) advice, and helpful to learner of data modeling.
      </p>
      <p>
        Compared to earlier prototype implementations (see [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]), precision and
recall for ve demonstration cases, i. e., modeling tasks used in teaching
conceptual data modeling, improved in recognizing entity type and relationship type
identi ers from the text descriptions by an average of 0.045 with the largest
increase in attribute identi cation (entity types: precision 0.88 (from 0.84), recall
0.97 (from 0.94); attributes: precision 0.86 (from 0.79) 0.86, recall 0.79 (from
0.71); relationship types: precision 0.84 (from 0.84), recall 0.74 (from 0.69)).
The newly added identi cation of data types achieves a precision of 1.00 and a
recall of 0.66. In terms of precision and recall, the current prototype
implementation performs on par or better than related approaches (e. g., [
        <xref ref-type="bibr" rid="ref5 ref9">5,9</xref>
        ]), especially
with respect to nding candidates for entity type identi ers, with prior research
demonstrating values for recall from 0.92 [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] to 0.95 [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. Closer inspection of
precision and recall results show, as expected, the heuristic nature of the rules
applied to recognize relationship types, entity types, attributes, and
corresponding data types|and of the NLP techniques we use. Still, compound nouns with
three (and more) words such as 'social security number' are, for example, not
always properly recognized|a limitation we have already addressed by revising
the implemented data modeling heuristics for entity types and attributes but
which needs further work. For example, further prototype evaluation exempli es
that the identi cation of inherent relationships of compound nouns should be
improved posing a particular challenge as there are many ways to combine them
(see [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]). Moreover, we are currently implementing heuristic rules for identifying
generalization hierarchies in textual descriptions to provide data modelers with
automated assistance in modeling generalization relationships. Future work on
the Automated Assistant will also address the identi cation and recognition of
synonyms in the textual description by utilizing word embedding approaches
such as WordNet.
      </p>
      <p>
        We are currently planning for further systematic evaluation by empirical
studies investigating how well the feedback provided by the Automated
Assistant supports learners of data modeling in devising meaningful and appropriate
identi ers for model elements. Building on prior mixed-methods research into
data modeling processes [
        <xref ref-type="bibr" rid="ref10 ref11 ref13">10,11,13</xref>
        ], modelers will be observed from
complementary perspectives, e. g., based on the think-aloud method and surveying modelers
on their perception of the feedback as provided by the Automated Assistant.
Subsequently, we are planning to apply the Automated Assistant in an introductory
course on data modeling with 200+ students per semester to collect feedback on
the support provided by the Automated Assistant.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Batra</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ho</surname>
            <given-names>er</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>J.A.</given-names>
            ,
            <surname>Bostrom</surname>
          </string-name>
          ,
          <string-name>
            <surname>R.P.</surname>
          </string-name>
          :
          <article-title>Comparing representations with relational and EER models</article-title>
          .
          <source>Communications of the ACM</source>
          <volume>33</volume>
          (
          <issue>2</issue>
          ),
          <volume>126</volume>
          {
          <fpage>139</fpage>
          (
          <year>1990</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Chen</surname>
            ,
            <given-names>P.P.</given-names>
          </string-name>
          : English Sentence Structure and
          <string-name>
            <surname>Entity-Relationship Diagrams</surname>
          </string-name>
          .
          <source>Information Sciences</source>
          <volume>29</volume>
          ,
          <volume>127</volume>
          {
          <fpage>149</fpage>
          (
          <year>1983</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Chowdhury</surname>
          </string-name>
          , G.:
          <article-title>Natural language processing</article-title>
          .
          <source>Annual review of Information science and technology 37</source>
          ,
          <volume>51</volume>
          {
          <fpage>89</fpage>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Liddy</surname>
          </string-name>
          , E.D.:
          <article-title>Enhanced Text Retrieval Using Natural Language Processing</article-title>
          .
          <source>Bulletin of the American Society for Information Science and Technology</source>
          <volume>24</volume>
          (
          <issue>4</issue>
          ),
          <volume>14</volume>
          {
          <fpage>16</fpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Lucassen</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Robeer</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dalpiaz</surname>
          </string-name>
          , F.,
          <string-name>
            <surname>van der Werf</surname>
            ,
            <given-names>J.M.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brinkkemper</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Extracting conceptual models from user stories with Visual Narrator</article-title>
          .
          <source>Requirements Engineering</source>
          <volume>22</volume>
          (
          <issue>3</issue>
          ),
          <volume>339</volume>
          {
          <fpage>358</fpage>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Manning</surname>
            ,
            <given-names>C.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Surdeanu</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bauer</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Finkel</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bethard</surname>
            ,
            <given-names>S.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McClosky</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>The Stanford CoreNLP Natural Language Processing Toolkit</article-title>
          . In:
          <article-title>52nd Annual Meeting of the Association for Computational Linguistics: System Demonstrations</article-title>
          . pp.
          <volume>55</volume>
          {
          <fpage>60</fpage>
          .
          <string-name>
            <surname>Baltimore</surname>
          </string-name>
          ,
          <string-name>
            <surname>Maryland</surname>
          </string-name>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Mendling</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reijers</surname>
            ,
            <given-names>H.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Recker</surname>
          </string-name>
          , J.:
          <article-title>Activity labeling in process modeling: Empirical insights and recommendations</article-title>
          .
          <source>Information Systems</source>
          <volume>35</volume>
          (
          <issue>4</issue>
          ),
          <volume>467</volume>
          {
          <fpage>482</fpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Omar</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hanna</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mc</surname>
            <given-names>Kevitt</given-names>
          </string-name>
          ,
          <string-name>
            <surname>P.</surname>
          </string-name>
          :
          <article-title>Heuristics-based entity-relationship modelling through natural language processing</article-title>
          .
          <source>In: 15th Arti cial Intelligence and Cognitive Science Conference</source>
          . pp.
          <volume>302</volume>
          {
          <fpage>313</fpage>
          . Dublin, Ireland (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Omer</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , Wilson, D.:
          <article-title>Implementing a Database from a Requirement Speci cation</article-title>
          .
          <source>International Journal of Computer and Information Engineering</source>
          <volume>9</volume>
          (
          <issue>1</issue>
          ),
          <volume>33</volume>
          {
          <fpage>41</fpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Rosenthal</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Strecker</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Toward a taxonomy of modeling di culties: A multimodal study on individual modeling processes</article-title>
          .
          <source>In: 40th International Conference on Information Systems, ICIS</source>
          <year>2019</year>
          , Munich, Germany,
          <source>December</source>
          <volume>15</volume>
          {
          <fpage>18</fpage>
          ,
          <year>2019</year>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Rosenthal</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Strecker</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pastor</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          :
          <article-title>Modeling di culties in data modeling: Similarities and di erences between experienced and non-experienced modelers</article-title>
          .
          <source>In: 39th International Conference on Conceptual Modeling, ER</source>
          <year>2020</year>
          , Vienna, Austria,
          <source>November</source>
          <volume>3</volume>
          {
          <fpage>6</fpage>
          ,
          <year>2020</year>
          . LNCS, vol
          <volume>12400</volume>
          . pp.
          <volume>501</volume>
          {
          <issue>511</issue>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Speaks</surname>
          </string-name>
          , J.:
          <article-title>Theories of Meaning</article-title>
          . In: Zalta,
          <string-name>
            <surname>E.N.</surname>
          </string-name>
          <article-title>(ed.) The Stanford Encyclopedia of Philosophy</article-title>
          . Metaphysics Research Lab, Stanford University, winter
          <year>2019</year>
          edn. (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Strecker</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosenthal</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ternes</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Studying Conceptual Modeling Processes: A Modeling Tool</article-title>
          , Research Observatory, and
          <article-title>Multimodal Observation Setup</article-title>
          . In: Gimpel,
          <string-name>
            <given-names>H.</given-names>
            , Kramer, J.,
            <surname>Neumann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Pfei</surname>
          </string-name>
          <string-name>
            <given-names>er</given-names>
            , J.,
            <surname>Seifert</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Teubner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            ,
            <surname>Veit</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Weidlich</surname>
          </string-name>
          ,
          <string-name>
            <surname>A</surname>
          </string-name>
          . (eds.) Market Engineering { Insights from Two Decades of Research, pp.
          <volume>99</volume>
          {
          <fpage>111</fpage>
          . Springer, Cham (
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Ternes</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosenthal</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Strecker</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>Automated Assistance for Data Modelers: A Heuristics-based Natural Language Processing Approach</article-title>
          .
          <source>In: 29th European Conference on Information Systems, ECIS</source>
          <year>2021</year>
          , Marrakech, Morocco,
          <source>June</source>
          <volume>15</volume>
          {
          <fpage>17</fpage>
          ,
          <year>2021</year>
          (
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Tjoa</surname>
            ,
            <given-names>A.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berger</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>Transformation of requirement speci cations expressed in natural language into an EER model</article-title>
          . In: Elmasri,
          <string-name>
            <given-names>R.</given-names>
            ,
            <surname>Kouramajian</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            ,
            <surname>Thalheim</surname>
          </string-name>
          ,
          <string-name>
            <surname>B</surname>
          </string-name>
          . (eds.)
          <source>Proceedings of the 12th International Conference on the EntityRelationship Approach</source>
          , ER 1993, Arlington, Texas, USA, December
          <volume>15</volume>
          {
          <fpage>17</fpage>
          ,
          <year>1993</year>
          . LNCS, vol
          <volume>823</volume>
          . pp.
          <volume>206</volume>
          {
          <issue>217</issue>
          (
          <year>1994</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>