<!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>Semantic Consistency in Enterprise Models { Through Seamless Modelling and Execution Support</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Tomas Jonsson</string-name>
          <email>tomas@genicore.se</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Hakan Enquist</string-name>
          <email>hakan.enquist@gu.se</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Applied IT, University of Gothenburg</institution>
          ,
          <country country="SE">Sweden</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Genicore AB</institution>
          ,
          <addr-line>S-411 09 Goteborg</addr-line>
          ,
          <country country="SE">Sweden</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Semantic consistency, in context of a socio-technical view on Enterprise Information Systems (EIS), concern consistency between Enterprise Models, Conceptual Models expressed in professional language, Information Systems models and the factual data manipulation and functions implemented in runtime IT artefacts. CoreWeb, an environment for modelling and testing conceptual models, implemented as an easy to use web service, provide support for model editing and execution, semantic consistency exploration and checking as well as producing documentation for either requirement speci cations and/or for execution in model driven runtime environments such as CorePro. CoreWeb modelling views and features are presented in the paper and illustrated in the Demo comprising a walkthrough of a case supporting dialog and model veri cation between users, domain experts, modellers and system designers.</p>
      </abstract>
      <kwd-group>
        <kwd>Information Systems</kwd>
        <kwd>Phenomena Modelling</kwd>
        <kwd>Semantic Quality</kwd>
        <kwd>Natural Language</kwd>
        <kwd>Modelling Environment</kwd>
        <kwd>Model Execution</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Conceptual models can be used to re ect relevant concepts of an enterprise and
play an important role in communication between users, domain experts,
modellers and system designers, in the life cycle management of IT based Information
Systems (ITbIS).</p>
      <p>If the Enterprise Information System (EIS) is regarded as a socio-technical
system i.e. a system of people and information artefacts, the semantic consistency
of a conceptual model as a foundation for ITbIS development, can only be fully
evaluated with the resulting ITbIS put in context of the socio-technical EIS. This
evaluation will of course only be relevant if the ITbIS implementation accurately
correspond to the semantic model.</p>
      <p>Additionally, the socio-technical systems are comprised of various enterprise
actors with di erent semantic perspectives. If the semantic model is to be
consistent with these perspectives, the semantic modelling facility should include a
perspective-modelling component.</p>
      <p>The life cycle process, from conceptual model to target ITbIS, in traditional
approaches, involves several steps of manual transformations of what the
conceptual model expresses. Each step involves several degrees of freedom for design
and implementation compromises resulting in deviations from the statements
of the conceptual model. However, with a semantic model driven ITbIS, i.e.
semantic model execution, free from manual transformation processes, consistency
between model and implementation could be guaranteed.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Approaches to conceptual model execution</title>
      <p>
        Environments executing conceptual models in purpose of verifying conceptual
consistency exist, such as Merode [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] a modelling and model execution
environment aimed at practitioners and students. Merode however does not support
multi perspectives modelling, such as suggested in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>
        Core Enterprise Architecture Framework (CoreEAF) is a process agnostic,
rule based, reference architecture and modelling method for multi perspectives
information systems, proven to be viable for large scale information systems
development [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] in combination with CorePro model and runtime environment
(a C++, SQL and XSLT based information systems platform).
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>CoreWEB</title>
      <p>CoreWEB is an experimental (non commercial) modelling and execution WEB
service based on CoreEAF. CoreWEB is aimed at students and practitioners who
want to focus on enterprise phenomena modelling with multi-actor perspectives.</p>
      <p>The CoreWEB project was initiated in 2015 with the key target to simplify
the 'model to system' process as well as exploring various new modelling and
system quality aspects.</p>
      <p>CorePros web based modelling component was partly reused and extended.
A new (and compared with CorePro) simpli ed system execution strategy was
designed, including Javascript code generation for phenomena model execution,
a model driven user interface engine with user interface model editing capability
and a web service platform.</p>
      <p>CoreWEB, apart from being a WEB service, o ers new features focusing
on semantic quality for both conceptual model and system. Adding professional
language sentences feedback (currently in Swedish and English). A semantic user
interface model ensures semantic consistency between model and user interface,
an auto layout system enforce a syntactically consistent user interface.</p>
      <p>As an experiment and requirement elicitation driver, CoreWEB, with some
additions, has been used for a limited production system case (Lazarus, a live
action role play event association with 600 members).</p>
      <p>Environment and demonstration videos are available from Association for
Model Enabled Information Systems. https://ameis.se/cml/index.htm
4</p>
    </sec>
    <sec id="sec-4">
      <title>Demo of CoreWEB</title>
      <p>The CoreWEB phenomenon type-modelling component has some di erent views
Fig. 1. The phenomenon map, is a two dimensional map of types of phenomena
and their basic relationships, used for model navigation. The de nition of a
phenomenon type is comprised of attribute de nitions. Types of phenomena
and their attributes, except Boolean attributes, should be labelled with nouns
or noun phrases, in stating both singular and plural forms.</p>
      <p>In the phenomenon map, types of phenomena are displayed using the plural
noun form, since the model item represents a set of instances of a certain type.
Relation attribute labels are displayed according to their multiplicity, zero-one
or zero-many. From the model, a dictionary can be generated, de ning each
modelled enterprise concept with an auto generated statement. Also when executing
the ITbIS, singular and plural noun forms are displayed appropriately, in Fig. 1
for example the 2 possessions list and the owner eld.
The phenomena modelling component generates XML Fig. 2, which is
transformed by three XSLT processes into, natural language statements, executable
Javascript phenomena model equivalent and a user interface model, which is
kept consistent in respect to changes to the phenomena model. When system is
executed, the UI Engine will read the UI-model and interact with the executing
phenomena instance model according to the UI model.</p>
    </sec>
    <sec id="sec-5">
      <title>Notes and Comments</title>
      <p>CoreWEB approach to enterprise modelling facilitates dialog, user involvement,
conceptual con ict resolution and rich expressions of enterprise knowledge as a
direct design basis for information management and ITbIS artefacts.</p>
      <p>The resulting models, phenomenon and UI models, can be used as part of a
speci cation for ITbIS development regardless of implementation strategy or be
transferred to the CorePro production system development environment.</p>
      <p>Future research includes enrichment of model semantics and natural language
model feedback by adding semantic variants of relations and phenomena and
experiments with data content and explanatory text and speech generation.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Sedrakyan</surname>
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Snoeck</surname>
            <given-names>M.</given-names>
          </string-name>
          <year>2014</year>
          :
          <article-title>Lightweight Semantic Prototyper for Conceptual Modeling</article-title>
          ,
          <source>Advances in Conceptual Modeling: ER</source>
          <year>2014</year>
          , p298-
          <fpage>302</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Frank</surname>
            <given-names>U.</given-names>
          </string-name>
          <year>2014</year>
          :
          <article-title>Multi-perspective enterprise modeling: foundational concepts, prospects and future research challenges, Softw Syst Model (</article-title>
          <year>2014</year>
          )
          <volume>13</volume>
          :
          <fpage>941</fpage>
          -
          <lpage>962</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Jonsson</surname>
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Enquist</surname>
            <given-names>H.</given-names>
          </string-name>
          <year>2015</year>
          :
          <article-title>CoreEAF { a Model Driven Approach to Information Systems</article-title>
          .
          <source>Proceedings of CAISE Forum</source>
          <year>2015</year>
          ,
          <fpage>p137</fpage>
          -
          <lpage>144</lpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>