<!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>Enterprise Architecture modelling with ArchiMate</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Kaïs Chaabouni</string-name>
          <email>kais.chaabouni@softeam.fr</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Alessandra Bagnato</string-name>
          <email>alessandra.bagnato@softeam.fr</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ståle Walderhaug</string-name>
          <email>stale.walderhaug@sintef.no</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Arne J. Berre</string-name>
          <email>arne.j.berre@sintef.no</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Caj Södergård</string-name>
          <email>caj.sodergard@vtt.fi</email>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andrey Sadovykh</string-name>
          <email>a.sadovykh@innopolis.ru</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Innopolis University</institution>
          ,
          <country country="RU">Russia</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>SINTEF</institution>
          ,
          <country country="NO">Norway</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Softeam R&amp;D Department</institution>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>VTT</institution>
          ,
          <country country="FI">Finland</country>
        </aff>
      </contrib-group>
      <fpage>79</fpage>
      <lpage>84</lpage>
      <abstract>
        <p>The Data-Driven Bio-economy project (DataBio) focuses on developing new technologies and services for agriculture, fishery and forestry by exploiting the huge potential of Big Data technologies. This Lighthouse project includes 27 pilots and 91 technological components provided by 27 of the 48 project partners. It applies a standard Enterprise Architecture modelling language: “ArchiMate 3.0”. ArchiMate models are created with the tool “Modelio” which allows contributors to create ArchiMate diagrams and collaborate on a synchronized version of the models. The DataBio models cover different aspects of the project from the specification phase including requirements, goals and strategies, to the implementation phase by describing the different processes of the tasks included in the work packages and representing the technological components. This paper describes the use of ArchiMate modelling applied in the context of the DataBio research project.</p>
      </abstract>
      <kwd-group>
        <kwd>Enterprise Architecture</kwd>
        <kwd>Modelling</kwd>
        <kwd>ArchiMate</kwd>
        <kwd>Modelio</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Project data</title>
      <p>- The agriculture pilots which aim to improve precision farming based on
observational data and predictive analysis.
- The forestry pilots which aim to improve forest monitoring, predict risks and
optimize tree resources.
- The fishery pilots which aim to improve vessel energy economy, logistic
efficiency and predictive analysis of the fishery market as well as decreasing the
environmental impact.</p>
      <p>
        Taking into consideration the complexity of these tasks and the big number of
heterogeneous technological components involved, we chose ArchiMate 3.0 [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] as an
enterprise architecture modelling language in order to represent the components and
the processes of the different pilots. These models can be useful for requirements
elicitation, technical solutions design, interactions between stakeholders, facilitating
communications between partners and for reporting results. This paper is structured as
follows: section 2 presents the ArchiMate modelling approach in the context of
DataBio project, section 3 illustrates the modelling of the pilots and Section 4
contains the modelling of the technological components used in DataBio project.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2 DataBio modelling approach with “ArchiMate 3.0”</title>
      <p>
        The enterprise architecture methods are used for providing organizational structure,
business processes and the IT infrastructure of an enterprise. These methods can be
applied to DataBio context, where we are interested in modelling the case studies
business objectives, processes, requirements, data pipelines and IT components.
ArchiMate language has been proven to be particularly helpful for modelling
organizations having complex IT infrastructures [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Moreover, the ArchiMate
framework provides a wide range of modelling concepts which represent different
layers of the enterprise such as: strategy, application, motivation, technology,
business, etc [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. The modelling environment used for this task is the Modelio
ArchiMate modelling tool [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] which allows developers to collaborate on a
synchronized remote version of the models. At the first stage of the project, first six
months, the modelling process was focusing on the specification phase which meant
to provide diagrams to specify the objectives, the requirements and the desired
outcomes of the pilots. This helps to understand the big picture of the pilot, the
guidelines and the interactions between the stakeholders. In the second stage of the
modelling process, the technological design of the pilots became more mature and the
partners started working on diagrams that illustrate the software components, their
interactions and their deployment environment. The models are structured in five
ArchiMate projects described as follows: three projects (agriculture, forestry and
fishery) for pilot description, one project for modelling software and IoT system
components and finally one project for modelling Earth Observation data services.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3 DataBio pilot models</title>
      <p>
        DataBio pilots allow to experiment with different technologies on real case studies
with the objective of analyzing the feasibility, the efficiency and the economic
impact. The project’s goal is to have a big data platform that integrates these
technologies at the end of the project. We define this platform as an environment in
which a combination of software components are developed to be deployed in
hardware, virtualized infrastructure, operating system, middleware or a cloud. This
environment provides through the DataBio Hub (http://databiohub.eu) [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], a big data
toolset which offers functionalities primarily for services in agriculture, forestry and
fishery. The functionalities enable new software components to be easily and
effectively combined with open source, standards-based big data, and proprietary
components and infrastructures based on generic and domain specific components.
The DataBio toolset supports the forming of reusable and deployable pipelines of
interoperable and replaceable components, that can integrate the technologies adopted
in the pilots. Each pilot has been modelled in the specification phase with diagrams
that emphasize the motivation and strategy point of view. The motivation views
provide elements that motivate the choices of the pilot such as objectives and
requirements. The strategy views complete the motivation views by planning long
term actions to meet the specified objectives. Some of the pilots went further in their
design into providing additional models such as application views, data views and
business processes.
      </p>
      <sec id="sec-3-1">
        <title>3.1 Pilot motivation views</title>
        <p>The pilot motivation views present the reasons and factors that justify and guide the
pilot choices. This step is important for introducing the pilot and for explaining the
relevance of the pilot concept. The motivation diagrams contain goals which specify
the main objectives of the pilots. In relation to goals, these diagrams contain certain
outcomes that realize the specified goals. Moreover, these views contain the
stakeholders which are the individuals, teams and organizations involved in the pilot.
There are also internal and external factors represented by “driver” elements which
motivate an organization to define its goals and implement the changes necessary to
achieve them. In addition to these concepts, we use “requirement” elements which are
functionalities that need to be implemented and “constraint” elements which are
factors that limit the realization of the defined goals.</p>
        <p>
          An example of the motivation view can be found in the published presentation of
the “tuna fisheries planning” pilot [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. The purpose of this pilot is to improve
profitability of tuna fisheries by saving fuel based on fish observation and vessels
route optimization. Observe, that the catch volume cannot normally be increased as it
is limited by quota. Therefore, the main goal of this pilot is “improving catch
revenue”. More specifically we want to “reduce energy consumption” and “improving
catch efficiency” (see Fig. 1). In this pilot there are two major stakeholders: the
“Vessel Owner” and “Vessel master” who both want to improve catch revenue. The
vessel master is motivated by logistics on the ship and reducing the time spent on
operations. Similarly, the vessel owner is concerned with reducing energy
consumption and improving catch efficiency. These objectives are realized by
optimizing route cost efficiency and species distribution forecasting.
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2 Pilot strategy views</title>
        <p>The pilot strategy views allow decision makers to elaborate a global roadmap to
implement the announced objectives by defining course of actions for implementing
the tasks at hand considering the capabilities of the organization and the available
resources. For example, the strategy view of the fishery pilot mentioned in the
previous section demonstrate how strategy elements provide leads for implementing
the objective of “Improving the revenue of fish catching” (see Fig. 2). This objective
can be realized by providing a decision support system on vessel operations. Given
our capabilities in data collection and data analytics, we can develop the specified
decision support system by collecting sensor data and extract useful information for
decision makers.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4 Technological components models</title>
      <p>
        DataBio pilots include various technological components with different interfaces,
different data formats (sensors data, satellite imagery, etc) and different deployment
environments. For each component, ArchiMate diagrams were created for modelling
the interface view, the deployment view and the data view. The interface view shows
the external interfaces of the component which are designed for interactions with
users or with other components through various communication protocols. For
example, the component “C07.04: Data Manager” is used for downloading and
preprocessing earth observation data in forestry and fishery pilots. Its identification
code “C07.04” is formed from component (=C), DataBio partner number (=07) and
component number of that partner (=4). This component offers three interfaces for
downloading data via Java API, REST API and command line interface (CLI). It also
offers three interfaces for consuming data from other components (see Fig. 3) [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. The
deployment view describes the application executables and the software and physical
environment required for running the application. The data view describes the format,
the source and the content of the data processed by the component.
      </p>
      <p>
        In addition to components models, more ArchiMate diagrams were created in
order to represent the data pipelines adopted by each pilot. As mentioned before, the
different pilots are working on integrating several components into their workflow
processes. These processes are referred to as “pipelines”, as they integrate different
tasks along the data value chain from data collecting to analysing and visualizing. The
pipelines models represent the pilot lifecycle, the integrated components and the data
flow between components. For example, the component “C07.04: Data Manager”
mentioned previously is integrated in the pipeline of the fishery pilot “Oceanic tuna
fisheries planning” (see Fig. 4) [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. “Data Manager” acquires data from different
components such as the component “C07.01: FedEO Gateway” which is a unique
endpoint that retrieves geographical data from several backend providers such as
“Copernicus Open Access Hub”. Moreover, “Data Manager” stores data in network
file systems or HDFS distributed file systems. Finally, the component “C07.06
      </p>
      <p>Ingestion Engine” consumes the collected data by “Data Manager” via REST API
interface.</p>
    </sec>
    <sec id="sec-5">
      <title>Acknowledgments</title>
      <p>This work is partially funded by the DataBio project (No. 732064) under European
Commission’s Horizon 2020 research and innovative programme.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>DataBio</given-names>
            <surname>Consortium</surname>
          </string-name>
          , https://www.databio.eu/en/consortium. Accessed 18 Apr.
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>DataBio</given-names>
            <surname>Summary</surname>
          </string-name>
          ,https://www.databio.eu/en/summary Accessed 18 Apr.
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Josey</surname>
          </string-name>
          , Andrew.
          <source>ArchiMate® 3.0</source>
          . 1
          <article-title>-A pocket guide</article-title>
          .
          <source>Van Haren</source>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4. FRITSCHER,
          <string-name>
            <surname>Boris et</surname>
            <given-names>PIGNEUR</given-names>
          </string-name>
          ,
          <article-title>Yves. Business IT alignment from business model to enterprise architecture</article-title>
          .
          <source>In : International Conference on Advanced Information Systems Engineering</source>
          . Springer, Berlin, Heidelberg,
          <year>2011</year>
          . p.
          <fpage>4</fpage>
          -
          <lpage>15</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Desfray</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Raymond</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          (
          <year>2018</year>
          ).
          <article-title>TOGAF, Archimate, UML et BPMN-3e éd</article-title>
          . Dunod.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6. Modelio products, https://www.modeliosoft.com/en/.
          <source>Last accessed 18 Apr</source>
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>DataBio</given-names>
            <surname>Hub</surname>
          </string-name>
          , https://www.databiohub.eu.
          <source>Last accessed 18 Apr</source>
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <source>DataBio public deliverable D3</source>
          .1:
          <string-name>
            <given-names>Fishery</given-names>
            <surname>Pilot Definition</surname>
          </string-name>
          ,
          <year>v1</year>
          .0,
          <year>2017</year>
          /10/20.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <source>DataBio public deliverable D5</source>
          .
          <article-title>1: EO Components Specifications</article-title>
          ,
          <year>v1</year>
          .0,
          <year>2017</year>
          /12/29.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <article-title>DataBio public deliverable D5.2: EO Components and Interfaces</article-title>
          ,
          <source>v1.0</source>
          ,
          <year>2018</year>
          /05/30.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <source>Internet of Food &amp; Farm Project</source>
          <year>2020</year>
          (
          <issue>IoF2020</issue>
          ) ,https://www.iof2020.
          <source>eu . 18 Apr</source>
          .
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <article-title>Big Data Benchmarking project (DataBench)</article-title>
          , https://www.databench.
          <source>eu . 18 Apr</source>
          .
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Mohagheghi</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          , et al. (
          <year>2009</year>
          ).
          <article-title>"Definitions and approaches to model quality in modelbased software development-A review of literature."</article-title>
          <source>Information and Software Technology</source>
          <volume>51</volume>
          (
          <issue>12</issue>
          ):
          <fpage>1646</fpage>
          -
          <lpage>1669</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>